how to automate tasks in DevRev
ART-2037_KNOWLEDGE_NODE-40
Identities** and **Link GitHub Account**.\n\nYou can configure these automations from [GitHub for DevRev snap-in](/marketplace/github).\n\nTask creation\n-------------\n\nDevRev can help you keep track of your issues while they\'re in the PR process. With PR Task Creation, a task is created for each PR reviewer in the DevRev issue associated with the PR. These tasks are automatically marked as completed when the reviewer approves or denies the PR or when the PR is closed for any reason.\n\nTo
GitHub | Integrate | Snap-ins | DevRev
ART-8441_KNOWLEDGE_NODE-25
your code to the center of your decision-making with GitLab and DevRev. The GitLab integration allows users to onboard to DevRev and automate day-to-day activities, eliminating tedious manual tasks.\n\n* [Work automation](#work-automation): Connect GitLab events to your DevRev issues.\n* [Magic Commands](#magic-commands): Update DevRev issues without leaving your IDE.\n* [Autotrack work](#automatic-work-detection): Automatically track your work in DevRev even without creating an issue ahead of
GitLab | Integrate | Snap-ins | DevRev
ART-1945_KNOWLEDGE_NODE-29
such as Slack and Jira. Automations perform tasks within DevRev based on events, like responding to customer conversations and linking tickets and issues. [AirSync](./import) helps you bring data from external sources to DevRev and keep them in sync.\n\nWhile numerous snap-ins are available and more are in development, you can create your own using [DevRev APIs](https://developer.devrev.ai/about/for-developers).\n\n[PreviousIntroduction](/docs)[NextCore concepts](/docs/product/core)\n\n#### On
Computer by DevRev | DevRev
ART-2037_KNOWLEDGE_NODE-25
integration allows GitHub users to onboard to DevRev and automate day-to-day activities, removing the need for tedious manual tasks.\n\n* [Work automation](#work-automation): Connect GitHub events to your DevRev issues.\n* [Magic Commands](#magic-commands): Update DevRev issues without leaving your IDE.\n* [Autotrack work](#automatic-work-detection): Automatically track your work in DevRev even without creating an issue ahead of time.\n* [PR Task Creation](#task-creation): Create DevRev tasks
GitHub | Integrate | Snap-ins | DevRev
ART-2030_KNOWLEDGE_NODE-26
IDE.\n* **Autotrack work**: Automatically track your work in DevRev even without creating an issue ahead of time.\n* **PR task creation**: Create DevRev tasks for PR reviewers.\n* **PR reminders**: Automatically remind PR reviewers when a PR goes stale.\n\n![]()\n\nFor more information, refer to the\n[Bitbucket for DevRev snap-in](https://marketplace.devrev.ai/bitbucket) on the DevRev marketplace.\n\nInstallation\n------------\n\n1. In DevRev, go to **Settings** > **Snap-ins** and click
Bitbucket | Integrate | Snap-ins | DevRev
ART-4179_KNOWLEDGE_NODE-3
the DevRev ecosystem.](https://devrevu.reach360.com/share/course/676d4cd1-0520-45bd-813d-8289d0fc8772)[![]()\n\nDevRev: Customizations and snap-ins\n\nExtend DevRev by building custom experiences for your workflow](https://devrevu.reach360.com/share/course/6dea13c5-5e05-46bd-bf2b-e29f4fca130c)[![]()\n\nDevRev: Workflows and automations\n\nDesign workflows and automations that drive productivity at
DevRev University
ART-1985_KNOWLEDGE_NODE-9
[Automate](/docs/automate)\n\n    - [Account deduplication](/docs/automations/account-deduplication)\n    - [Airtable](/docs/automations/airtable)\n    - [Auto-link DevRev GitHub accounts](/docs/automations/auto-link-github-devrev)\n    - [Automatic customer reply](/docs/automations/auto-reply)\n    - [Auto parts to conversation](/docs/automations/auto-parts)\n    - [Automated part update](/docs/automations/automated-part-update)\n    - [Automate opportunities](/docs/automations/opportunity)\n
Articles | Knowledge Base | Computer for Support Teams | DevRev
ART-6176_KNOWLEDGE_NODE-9
[Automate](/docs/automate)\n\n    - [Account deduplication](/docs/automations/account-deduplication)\n    - [Airtable](/docs/automations/airtable)\n    - [Auto-link DevRev GitHub accounts](/docs/automations/auto-link-github-devrev)\n    - [Automatic customer reply](/docs/automations/auto-reply)\n    - [Auto parts to conversation](/docs/automations/auto-parts)\n    - [Automated part update](/docs/automations/automated-part-update)\n    - [Automate opportunities](/docs/automations/opportunity)\n
Real-time sentiment evaluator | Automate | Snap-ins | DevRev
ART-2017_KNOWLEDGE_NODE-9
[Automate](/docs/automate)\n\n    - [Account deduplication](/docs/automations/account-deduplication)\n    - [Airtable](/docs/automations/airtable)\n    - [Auto-link DevRev GitHub accounts](/docs/automations/auto-link-github-devrev)\n    - [Automatic customer reply](/docs/automations/auto-reply)\n    - [Auto parts to conversation](/docs/automations/auto-parts)\n    - [Automated part update](/docs/automations/automated-part-update)\n    - [Automate opportunities](/docs/automations/opportunity)\n
SLA status change Slack notifier | Automate | Snap-ins | DevRev
ART-4186_KNOWLEDGE_NODE-9
[Automate](/docs/automate)\n\n    - [Account deduplication](/docs/automations/account-deduplication)\n    - [Airtable](/docs/automations/airtable)\n    - [Auto-link DevRev GitHub accounts](/docs/automations/auto-link-github-devrev)\n    - [Automatic customer reply](/docs/automations/auto-reply)\n    - [Auto parts to conversation](/docs/automations/auto-parts)\n    - [Automated part update](/docs/automations/automated-part-update)\n    - [Automate opportunities](/docs/automations/opportunity)\n
Computer for User Insights | Session analytics | Computer for Your Customers | DevRev
ART-2037_KNOWLEDGE_NODE-26
for PR reviewers.\n* [PR Reminders](#pr-reminders): Automatically remind PR reviewers when a PR goes stale.\n\nWork automation\n---------------\n\nYou can enable GitHub work automation through the [GitHub for DevRev snap-in](/marketplace/github) by establishing a GitHub connection and setting up a webhook.\n\nTo set up the GitHub for DevRev snap-in, go to [Marketplace](/marketplace) and install the [GitHub for DevRev snap-in](/marketplace/github).\n\nWebhook
GitHub | Integrate | Snap-ins | DevRev
ART-2019_KNOWLEDGE_NODE-7
software development. Through this automation, issues are automatically assigned to the relevant sprints based on their stage and other relevant factors. This leads to a decrease in manual workload and an improvement in overall efficiency.\n\nInstalling the smart sprint snap-in.\n\nIn DevRev, go to Settings. > Snap-ins. and click Explore Marketplace. in the top-right corner.\nIn the DevRev marketplace, find Smart sprint. and click Install..\nIn DevRev, confirm installation.\nClick
Smart sprint | Automate | Snap-ins | DevRev
ART-1970_KNOWLEDGE_NODE-9
[Automate](/docs/automate)\n\n    - [Account deduplication](/docs/automations/account-deduplication)\n    - [Airtable](/docs/automations/airtable)\n    - [Auto-link DevRev GitHub accounts](/docs/automations/auto-link-github-devrev)\n    - [Automatic customer reply](/docs/automations/auto-reply)\n    - [Auto parts to conversation](/docs/automations/auto-parts)\n    - [Automated part update](/docs/automations/automated-part-update)\n    - [Automate opportunities](/docs/automations/opportunity)\n
Conversation-Team Performance | Support analytics | Computer for Support Teams | DevRev
ART-2076_KNOWLEDGE_NODE-3
the DevRev ecosystem.](https://devrevu.reach360.com/share/course/676d4cd1-0520-45bd-813d-8289d0fc8772)[![]()\n\nDevRev: Customizations and snap-ins\n\nExtend DevRev by building custom experiences for your workflow](https://devrevu.reach360.com/share/course/6dea13c5-5e05-46bd-bf2b-e29f4fca130c)[![]()\n\nDevRev: Workflows and automations\n\nDesign workflows and automations that drive productivity at
DevRev University
ART-15716_KNOWLEDGE_NODE-0
b'Support QueryIntegration and API Questions\n\nAPI Support in DevRev\n\nYes, DevRev provides robust APIs for automation, integration, and custom workflows. You can use REST APIs to interact with tickets, issues, users, and more.\n\n[Learn more about DevRev APIs](https://devrev.ai/docs/api)\n\n2. Slack User Permissions Needed for Slack Integration\n\nTo integrate DevRev with Slack, you need to be a Slack workspace admin or have permission to install apps. The integration requires permission to
Support queries related playbook
ART-8441_KNOWLEDGE_NODE-37
lifecycle\n\nThe lifecycle of autonomous work is also automatically updated based on the stage of GitLab event mapping. Closing of autonomous work items based on PR close event is a user-level setting that each individual developer can opt-in for based on their preferences under **My Settings** and toggle on **Enable for Me**.\n\nTask creation\n-------------\n\nDevRev can help you keep track of your issues while they're in the PR process. With PR Task Creation, a task is created for each PR
GitLab | Integrate | Snap-ins | DevRev
ART-8441_KNOWLEDGE_NODE-38
reviewer in the DevRev issue associated with the PR. These tasks are automatically marked as completed when the reviewer approves or denies the PR or when the PR is closed for any reason.\n\nTo make use of this feature, the following conditions must be met:\n\n1. Create task for PR reviewers is enabled under **My Settings** and toggle on **Enable for me**.\n2. Each developer that wants to use this feature links their GitLab account by going to **Settings** > **Account** > **External
GitLab | Integrate | Snap-ins | DevRev
ART-1991_KNOWLEDGE_NODE-25
helps you bring data from external sources to DevRev and keep them in sync.\n\nWhile numerous snap-ins are available and more are in development, you can create your own using [DevRev APIs](https://developer.devrev.ai/).\n\nSupport\n-------\n\n| Automate | Integrate | AirSync |\n| --- | --- | --- |\n| [Auto parts to conversation](/docs/automations/auto-parts) | [Calendly](/docs/integrations/calendly) | [Salesforce](/docs/integrations/salesforce) |\n| [Auto-reply](/docs/automations/auto-reply) |
Support snap-ins | Computer for Support Teams | DevRev
ART-1277_KNOWLEDGE_NODE-4
[Using a snap-in to perform a DevRev action](/snapin-development/tutorials/timer-ticket-creator) tutorial.\n\n[1](/snapin-development/tutorials/triggered-event#installation-guide)\n\n### Installation guide\n\n* Install [DevRev CLI](/snapin-development/references/cli-install)\n* Install [jq](https://stedolan.github.io/jq)\n* Install [DevRev SDK](https://www.npmjs.com/package/@devrev/typescript-sdk?activeTab=readme)\n\n##### \n\nIf you did not follow the [getting
Snap-in triggered by a DevRev event | DevRev | Docs
ART-1353_KNOWLEDGE_NODE-3
upper-left corner of this site to switch between versions.\n\nTo take action based on events from the DevRev platform, [webhooks](/guides/webhooks) are also supported.\n\n[Public](/public)[Beta](/beta)\n\n\xf0\x9f\xa7\xa9 Snap-ins\n----------\n\nNumerous snap-ins are available on the DevRev [Marketplace](https://devrev.ai/marketplace). The [snap-in framework](/snapin-development/concepts) is available for you to create your own snap-ins for automation of DevRev workflows or integration with
For Developers | DevRev | Docs
ART-2016_KNOWLEDGE_NODE-25
more information, refer to the\n[StageFlow Automator snap-in](https://marketplace.devrev.ai/custom-covergence) on the DevRev marketplace.\n\nInstallation\n------------\n\n1. In DevRev, go to **Settings** > **Snap-ins** and click **Explore Marketplace** in the top-right corner.\n2. In the DevRev marketplace, find **StageFlow Automator** and click **Install**.\n\nConfiguration\n-------------\n\nYou need to create a mapping between the tickets and issues/enhancement stages so that when the stage
StageFlow automator | Automate | Snap-ins | DevRev
ART-1276_KNOWLEDGE_NODE-1
development](/snapin-development/concepts)[Tutorials](/snapin-development/tutorials/overview)\n\nUsing a snap-in to perform an external action\n=============================================\n\nCopy page\n\nIntroduction\n------------\n\nIn this tutorial, you learn how to develop a snap-in that mirrors an issue from DevRev to GitHub. This requires addition of a command that can be run from the **Discussions** tab of an issue in DevRev, which creates an issue in GitHub.\n\nBackground
Using a snap-in to perform an external action | DevRev | Docs
ART-1709_KNOWLEDGE_NODE-7
Rewards wanted a system that worked out of the box and had easy integration options. _\xe2\x80\x9c**We did not have the bandwidth amongst all our customer engagements to do in-house development to integrate into a platform.** \xe2\x80\x9d _says Pradeep.\n\nDevRev\xe2\x80\x99s wide range of add-on modules, also known as [Snap-ins](https://docs.devrev.ai/snapins), allows businesses to easily automate manual tasks and integrate the platform with the existing systems.\n\n**2\\. Easy migration:** As
ACC-qjz7ErXz - Mad Rewards: MadRewards uses DevRev’s AI to modernize customer su
ART-8441_KNOWLEDGE_NODE-26
time.\n* [PR Task Creation](#task-creation): Create DevRev tasks for PR reviewers.\n* [PR Reminders](#pr-reminders): Automatically remind PR reviewers when a PR goes stale.\n\n![]()\n\nFor more information, refer to the\n[GitLab snap-in](https://marketplace.devrev.ai/gitlab) on the DevRev marketplace.\n\nInstallation\n------------\n\n1. In DevRev, go to **Settings** > **Snap-ins** and click **Explore Marketplace** in the top-right corner.\n2. In the DevRev marketplace, find **GitLab for
GitLab | Integrate | Snap-ins | DevRev
ART-1485_KNOWLEDGE_NODE-7
the intricacies of responding to a DevRev webhook event, specifically focused on work creation.\n\n  2. **Command-based activation** : Explore how the snap-in can be triggered by a dedicated command within the DevRev environment.\n\n  3. **Payload exploration** : Delve into the payload structure, gaining insights into how to efficiently extract essential fields from within the functions.\n\n  4. **Action execution** : Become proficient in executing a specified action - adding a customizable
Snap-in triggered by a DevRev event — DevRev | Docs
ART-1485_KNOWLEDGE_NODE-19
comment on a DevRev work item created.  \n    5|   - name: function_2  \n    6|     description:  \n    7|       Function to create a timeline entry comment on a DevRev work item on which  \n    8|       comment is added.\n[/code]  \n  \n[6](/public/snapin-development/tutorials/triggered-event#automations)\n\n### Automations\n\nWith the building blocks in place, the final piece of the puzzle involves defining automations. These automations encapsulate a trigger and a corresponding function that
Snap-in triggered by a DevRev event — DevRev | Docs
ART-1483_KNOWLEDGE_NODE-3
development](/public/snapin-development/concepts)[Tutorials](/public/snapin-development/tutorials/overview)\n\n#\n\nUsing a snap-in to perform a DevRev action\n\n## Introduction\n\nThe objective is to build a snap-in that creates a new ticket every 10 minutes.\n\n## Background context\n\nThe [Getting Started](/public/snapin-development/tutorials/getting-started) tutorial creates a hello-world snap-in which prints a log message when a work item is created. This tutorial makes the following
Using a snap-in to perform a DevRev action — DevRev | Docs
ART-1961_KNOWLEDGE_NODE-28
workflow engine.\n* **Automations on one schema**: Our AirSync feature automatically transforms data from different sources. It enables you to create workflows natively in DevRev without the need to create fetch nodes or manually transform data.\n\nComponents\n----------\n\n* Workflow canvas: The field where you connect and visualize different steps in your workflow.\n* Steps: The building blocks of your workflow, shown on the canvas.\n* Variable selector: Used to insert variables into your
Workflows | Computer by DevRev | DevRev