query_id
stringlengths 36
36
| query
stringlengths 20
119
| retrievals
listlengths 1
126
|
|---|---|---|
59091cde-69a2-4096-a7bc-590007eca18c
|
session not logged for latest android releases
|
[
{
"id": "ART-12449_KNOWLEDGE_NODE-22",
"text": "session recording to capture user interactions with your app.\\n\\n#####\\n\\nThe session recording feature is opt-out and is enabled by default.\\n\\nHere are the available methods to help you control the session recording feature:\\n\\nAction| Kotlin (`DevRev`)| Java (`DevRevObservabilityExtKt`) \\n---|---|--- \\nStarts the session recording.| startRecording()| startRecording(DevRev.INSTANCE, context); \\nEnds the session recording and uploads it to the portal.| stopRecording()|",
"title": "Features — DevRev | Docs"
},
{
"id": "ART-2898_KNOWLEDGE_NODE-19",
"text": "app.\\n\\n#####\\n\\nThe session recording feature is opt-out and is enabled by default.\\n\\nHere are the available methods to help you control the session recording feature:\\n\\nAction| Kotlin (`DevRev`)| Java (`DevRevObservabilityExtKt`) \\n---|---|--- \\nStarts the session recording.| startRecording()| startRecording(DevRev.INSTANCE, context); \\nEnds the session recording and uploads it to the portal.| stopRecording()| stopRecording(DevRev.INSTANCE); \\nPauses the ongoing session recording.|",
"title": "Android integration — DevRev | Docs"
},
{
"id": "ART-12449_KNOWLEDGE_NODE-20",
"text": "enabling them from the start. However, you can opt-out using the following method:\\n\\n###### Kotlin\\n\\n###### Java\\n\\n[code]\\n\\n 1| DevRev.stopAllMonitoring() \\n ---|---\\n[/code] \\n \\nTo opt back in, use the following method:\\n\\n###### Kotlin\\n\\n###### Java\\n\\n[code]\\n\\n 1| DevRev.resumeAllMonitoring() \\n ---|---\\n[/code] \\n \\nYou can check whether session monitoring has been enabled by using this property:\\n\\nIf session recording was disabled for the user using the",
"title": "Features — DevRev | Docs"
},
{
"id": "ART-15513_KNOWLEDGE_NODE-31",
"text": "default, enabling them from the start. However, you can opt-out using the following method:\\n\\n###### Kotlin\\n\\n###### Java\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | DevRev.stopAllMonitoring() |\\n```\\n\\nTo opt back in, use the following method:\\n\\n###### Kotlin\\n\\n###### Java\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | DevRev.resumeAllMonitoring() |\\n```\\n\\nYou can check whether session monitoring has been enabled by using this property:\\n\\n###### Kotlin\\n\\n###### Java\\n\\n```\\n| | |\\n| --- | --- |\\n| 1",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-2898_KNOWLEDGE_NODE-18",
"text": "this user.\\n\\n###### Kotlin\\n\\n###### Java\\n\\n[code]\\n\\n 1| DevRev.resumeAllMonitoring() \\n ---|---\\n[/code] \\n \\nIf session recording was disabled for the user using the `stopAllMonitoring()` method, you can enable recording at runtime with this method.\\n\\n#####\\n\\nThis feature only stores a monitoring permission flag and does not provide any user interface or dialog.\\n\\n### Session recording\\n\\nYou can enable session recording to capture user interactions with your",
"title": "Android integration — DevRev | Docs"
},
{
"id": "ART-2982_KNOWLEDGE_NODE-15",
"text": "\\nTo opt back in, use the following method:\\n\\n[code]\\n\\n 1| DevRev.resumeAllMonitoring() \\n ---|---\\n[/code] \\n \\n### Session recording\\n\\nYou can enable session recording to capture user interactions with your app.\\n\\n#####\\n\\nThe session recording feature is opt-out and is enabled by default.\\n\\nThe session recording feature includes the following methods to control the recording:\\n\\nMethod| Action \\n---|--- \\n`DevRev.startRecording()`| Starts the session recording.",
"title": "React Native integration — DevRev | Docs"
},
{
"id": "ART-12453_KNOWLEDGE_NODE-20",
"text": "Opting-in or out\\n\\nSession analytics features are opted-in by default, enabling them from the start. However, you can opt-out using the following method:\\n\\n[code]\\n\\n 1| DevRev.stopAllMonitoring() \\n ---|---\\n[/code] \\n \\nTo opt back in, use the following method:\\n\\n[code]\\n\\n 1| DevRev.resumeAllMonitoring() \\n ---|---\\n[/code] \\n \\n### Session recording\\n\\nYou can enable session recording to capture user interactions with your app.\\n\\n#####\\n\\nThe session recording feature",
"title": "Features — DevRev | Docs"
},
{
"id": "ART-16579_KNOWLEDGE_NODE-28",
"text": "|\\n```\\n\\nTo opt back in, use the following method:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | DevRev.resumeAllMonitoring(); |\\n```\\n\\n### Session recording\\n\\nYou can enable session recording to record user interactions with your app.\\n\\n##### \\n\\nThe session recording feature is opt-out and is enabled by default.\\n\\nThe session recording feature includes the following methods to control the recording:\\n\\n| Method | Action |\\n| --- | --- |\\n| `DevRev.startRecording()` | Starts the session",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-4255_KNOWLEDGE_NODE-17",
"text": "analytics.\\n\\n###### Kotlin\\n\\n###### Java\\n\\n[code]\\n\\n 1| DevRev.stopAllMonitoring() \\n ---|---\\n[/code] \\n \\nThis method terminates and deletes the current session recording and also disables future session recording by our SDK for this user.\\n\\n###### Kotlin\\n\\n###### Java\\n\\n[code]\\n\\n 1| DevRev.resumeAllMonitoring() \\n ---|---\\n[/code] \\n \\nIf session recording was disabled for the user using the `stopAllMonitoring()` method, you can enable recording at runtime with this",
"title": "DevRev SDK for Android — DevRev | Docs"
},
{
"id": "ART-15507_KNOWLEDGE_NODE-26",
"text": "|\\n```\\n\\nSession analytics\\n-----------------\\n\\nThe DevRev SDK offers session analytics features to help you understand how users interact with your app.\\n\\n### Opt in or out\\n\\nSession analytics features are opted-in by default, enabling them from the start. However, you can opt-out using the following method:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | DevRev.stopAllMonitoring() |\\n```\\n\\nTo opt back in, use the following method:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | DevRev.resumeAllMonitoring()",
"title": "Features | DevRev | Docs"
}
] |
81bdf016-38e1-4abb-a766-92ecd6cb2bc2
|
enable conversations chat for some users only via widget
|
[
{
"id": "ART-15504_KNOWLEDGE_NODE-4",
"text": "[identify your customers](/sdks/web/user-identity) and update their information.\\n\\n##### \\n\\nOnce the SDK is installed, the chat widget appears by default. If you are not using the Plug SDK for support or chat-related flows, you can disable the chat widget by setting the `disable_plug_chat_window` input to `true`.\\n\\n```\\n| |\\n| --- |\\n| <script> |\\n| window.plugSDK.init({ |\\n| app_id: \\'<your_unique_app_id>\\', |\\n| disable_plug_chat_window: true, |\\n| }); |\\n| </script> |\\n```\\n\\nTo ensure",
"title": "Install the Web SDK | DevRev | Docs"
},
{
"id": "ART-2893_KNOWLEDGE_NODE-4",
"text": "update their information.\\n\\n#####\\n\\nOnce the SDK is installed, the chat widget appears by default. If you are not using the PLuG SDK for support or chat-related flows, you can disable the chat widget by setting the `disable_plug_chat_window` input to `true`.\\n\\n[code]\\n\\n <script> \\n --- \\n window.plugSDK.init({ \\n app_id: \\'<your_unique_app_id>\\', \\n disable_plug_chat_window: true, \\n }); \\n </script>\\n[/code] \\n \\nTo ensure seamless",
"title": "Install the Web SDK — DevRev | Docs"
},
{
"id": "ART-2894_KNOWLEDGE_NODE-4",
"text": "2| window.plugSDK.init({ \\n 3| app_id: \\'<your_unique_app_id>\\', \\n 4| disable_plug_chat_window: true, \\n 5| }); \\n 6| \\n 7| window.plugSDK.onEvent((payload) => { \\n 8| if (payload.type === \\'ON_PLUG_WIDGET_READY\\') { \\n 9| window.plugSDK.initSearchAgent(); \\n 10| } \\n 11| }); \\n 12| </script>\\n[/code] \\n \\nTo toggle `searchAgent`, call the following method on any event required:\\n\\n[code]\\n\\n",
"title": "Install PLuG search — DevRev | Docs"
},
{
"id": "ART-15509_KNOWLEDGE_NODE-4",
"text": "5 | }, []); |\\n```\\n\\nThe `init()` method can accept multiple inputs, which are explained below:\\n\\n| Input parameter | Description | Values |\\n| --- | --- | --- |\\n| `app_id` | The unique identifier for your Plug SDK. This parameter is required. | String |\\n| `disable_plug_chat_window` | The chat widget is enabled by default. Use this option if you want to disable the chat widget. | Boolean (True or False) |\\n| `enable_default_launcher` | Show/hide the default Plug widget launcher. | Boolean",
"title": "Methods | DevRev | Docs"
},
{
"id": "ART-2897_KNOWLEDGE_NODE-5",
"text": "window.plugSDK.init({ \\n 3| app_id: <your_unique_app_id>, \\n 4| }); \\n 5| }, []);\\n[/code] \\n \\nThe `init()` method can accept multiple inputs, which are explained below:\\n\\nInput parameter| Description| Values \\n---|---|--- \\n`app_id`| The unique identifier for your PLuG SDK. This parameter is required.| String \\n`disable_plug_chat_window`| The chat widget is enabled by default. Use this option if you want to disable the chat widget.| Boolean (True or False)",
"title": "Methods — DevRev | Docs"
},
{
"id": "ART-1466_KNOWLEDGE_NODE-20",
"text": "plugSDK. toggleTheme ( \\' light | dark \\' ) ;\\n\\nCalling toggleTheme() switches between the current themes. Specifying a theme as a parameter allows you to toggle directly to that specific theme.\\n\\nThe theme specified in this method takes precedence over the theme configured in the PLuG settings in your DevRev app.\\n\\nToggle widget.\\n\\nThe toggleWidget method allows you to control the visibility of the PLuG chat widget.\\n\\nPassing true opens the chat widget.\\n\\nPassing false closes the chat",
"title": "Methods — DevRev | Docs"
},
{
"id": "ART-15509_KNOWLEDGE_NODE-10",
"text": "`dark`.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | window.plugSDK.toggleTheme(\\'light | dark\\'); |\\n```\\n\\nCalling `toggleTheme()` switches between the current themes. Specifying a theme as a parameter allows you to toggle directly to that specific theme.\\n\\n##### \\n\\nThe theme specified in this method takes precedence over the theme configured in the Plug settings in your DevRev app.\\n\\nToggle widget\\n-------------\\n\\nThe `toggleWidget` method allows you to control the visibility of the Plug chat",
"title": "Methods | DevRev | Docs"
},
{
"id": "ART-2897_KNOWLEDGE_NODE-18",
"text": "search agent on your website. This initialization is required before performing any other actions with the PLuG widget SDK.\\n\\n[code]\\n\\n 1| useEffect(() => { \\n ---|--- \\n 2| window.plugSDK.init({ \\n 3| app_id: \\'<your_unique_app_id>\\', \\n 4| disable_plug_chat_window: true, \\n 5| }); \\n 6| \\n 7| window.plugSDK.onEvent((payload) => { \\n 8| if (payload.type === \\'ON_PLUG_WIDGET_READY\\') { \\n 9| window.plugSDK.initSearchAgent(); \\n",
"title": "Methods — DevRev | Docs"
}
] |
971f3502-0423-4061-886e-9bf60c80cc54
|
workflow-20 for If outside of Business hours
|
[
{
"id": "ART-2006_KNOWLEDGE_NODE-26",
"text": "define business hours, turn on the **Set business hours** toggle.\\n\\n * In the **Automated messages after business hours** field, enter the text you want to send as an automated reply.\\n * Define **Business start hours**, **Business end hours**, **UTC offset**, and **Business days** in the respective fields.\\n5. To send a button, turn on the **Enable a custom button** toggle.\\n\\n * In the **Text displayed on custom button** field, enter the text to be displayed on the button. For example,",
"title": "Automatic customer reply | Automate | Snap-ins | DevRev"
},
{
"id": "ART-4071_KNOWLEDGE_NODE-18",
"text": "\"is_out_of_schedule\": true, \\n 178| \"next_schedule_transition\": \"2023-01-01T12:00:00.000Z\", \\n 179| \"org_schedule\": { \\n 180| \"id\": \"foo\", \\n 181| \"status\": \"archived\", \\n 182| \"display_id\": \"foo\", \\n 183| \"name\": \"foo\", \\n 184| \"timezone\": \"foo\", \\n 185| \"valid_until\": \"2023-01-01T12:00:00.000Z\" \\n 186| }, \\n 187|",
"title": "Create Conversation — DevRev | Docs"
},
{
"id": "ART-15320_KNOWLEDGE_NODE-12",
"text": "\"in_policy\": true, |\\n| 201 | \"is_out_of_schedule\": true, |\\n| 202 | \"next_schedule_transition\": \"2023-01-01T12:00:00.000Z\", |\\n| 203 | \"org_schedule\": { |\\n| 204 | \"id\": \"string\", |\\n| 205 | \"status\": \"archived\", |\\n| 206 | \"display_id\": \"string\", |\\n| 207 | \"name\": \"string\", |\\n| 208 | \"timezone\": \"string\", |\\n| 209 | \"valid_until\": \"2023-01-01T12:00:00.000Z\" |\\n| 210 | }, |\\n| 211 | \"remaining_time\": 1, |\\n| 212 | \"status\": \"string\", |\\n| 213 | \"target_time\": \"2023-01-01T12:00:00.000Z\", |\\n|",
"title": "Create Conversation | DevRev | Docs"
},
{
"id": "ART-15327_KNOWLEDGE_NODE-12",
"text": "\"in_policy\": true, |\\n| 201 | \"is_out_of_schedule\": true, |\\n| 202 | \"next_schedule_transition\": \"2023-01-01T12:00:00.000Z\", |\\n| 203 | \"org_schedule\": { |\\n| 204 | \"id\": \"string\", |\\n| 205 | \"status\": \"archived\", |\\n| 206 | \"display_id\": \"string\", |\\n| 207 | \"name\": \"string\", |\\n| 208 | \"timezone\": \"string\", |\\n| 209 | \"valid_until\": \"2023-01-01T12:00:00.000Z\" |\\n| 210 | }, |\\n| 211 | \"remaining_time\": 1, |\\n| 212 | \"status\": \"string\", |\\n| 213 | \"target_time\": \"2023-01-01T12:00:00.000Z\", |\\n|",
"title": "Update Conversation | DevRev | Docs"
}
] |
c4f050e9-d6f0-43a4-9337-bbf05468baef
|
FORBIDDEN error cloning for EMEA
|
[
{
"id": "ART-1488_KNOWLEDGE_NODE-8",
"text": "Forbidden, {\"debug_message\":\"Unauthorized You are not authorized to perform this operation. Ref: bc7b7f58-148c-479c-b0a6-b4cbe43dd8a6\",\"message\":\"Forbidden\",\"type\":\"forbidden\"} \\n ---\\n[/code] \\n \\nYou are not an admin of the dev org where you want to create the snap-in.\\n\\nWas this page helpful?YesNo\\n\\n[Quotas and limitsUp Next](/public/snapin-development/quotas-limits)\\n\\n[Built",
"title": "Debugging — DevRev | Docs"
},
{
"id": "ART-1294_KNOWLEDGE_NODE-7",
"text": "\\'https://api.devrev.ai/internal/snap-ins.draft.create\\' failed with 403 Forbidden, {\"debug_message\":\"Unauthorized You are not authorized to perform this operation. Ref: bc7b7f58-148c-479c-b0a6-b4cbe43dd8a6\",\"message\":\"Forbidden\",\"type\":\"forbidden\"} |\\n```\\n\\nYou are not an admin of the dev org where you want to create the snap-in.\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/snapin-development/handling-errors-and-retrying)[#### Quotas and",
"title": "Debugging | DevRev | Docs"
},
{
"id": "ART-17711_KNOWLEDGE_NODE-1",
"text": "access.\\n\\nOnce Person A was re-added with the right permissions, the retry worked again.\\n\\nIf this happens, check who started the sync and make sure that person still exists in the org and has the right permissions. Until ownership handling is improved, retries for syncs started by users without access will fail with similar 401 or 403 errors.'",
"title": "Sync fails when original sync owners loses permissions"
},
{
"id": "ART-1958_KNOWLEDGE_NODE-28",
"text": "are not authorized to perform this action\". Relevant buttons may be inactive.\\nUsers can contact the organization\\'s admins to enable access in that case.\\n\\n![]()\\n\\nGranting access permissions\\n---------------------------\\n\\nUsers are granted access permissions to dashboards or reports through MFZ policies and sharing.\\n\\n### MFZ policies\\n\\nUse of MFZ policies facilitates the need to grant access to a wider group of users.\\n\\nAn org admin has permission to define and enable roles, in",
"title": "Access control | Computer by DevRev | DevRev"
},
{
"id": "ART-1364_KNOWLEDGE_NODE-2",
"text": "{\"message\":\"route not found\"}\\n[/code] \\n \\nStatus Code| Status| Description \\n---|---|--- \\n`400`| `Bad Request`| The request was malformed or contained invalid arguments. \\n`401`| `Unauthorized`| The user attempted to access an endpoint that requires authentication and no credentials were provided or their validation failed. \\n`403`| `Forbidden`| The user isn\\xe2\\x80\\x99t authorized to perform the requested action. \\n`404`| `Not Found`| The requested endpoint doesn\\xe2\\x80\\x99t exist.",
"title": "Errors — DevRev | Docs"
},
{
"id": "ART-1174_KNOWLEDGE_NODE-2",
"text": "HTTP/1.1 404 Not Found |\\n| Content-Type: application/json |\\n| Content-Length: 29 |\\n| {\"message\":\"route not found\"} |\\n```\\n\\n| Status Code | Status | Description |\\n| --- | --- | --- |\\n| `400` | `Bad Request` | The request was malformed or contained invalid arguments. |\\n| `401` | `Unauthorized` | The user attempted to access an endpoint that requires authentication and no credentials were provided or their validation failed. |\\n| `403` | `Forbidden` | The user isn\\xe2\\x80\\x99t authorized",
"title": "Errors | DevRev | Docs"
}
] |
bd6f760d-dca4-4fe2-9ee5-4e6a9d348283
|
Slack connector message handling CONV objects
|
[
{
"id": "ART-2035_KNOWLEDGE_NODE-54",
"text": "given DevRev user - Can be used to later send direct messages to the user on the Slack using Send message to Slack node. | - Slack connection - DevRev user id | - Slack user id |\\n| Start Thread Sync | - Set up 2 way message synchronization between a Slack thread and a DevRev object discussion. | - Slack connection - DevRev Object ID - Slack channel ID - Slack thread ID (message ID of parent message, returned by send message to Slack workflow node) | N/A |\\n| Start Channel Sync | -",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-33",
"text": "DevRev app.\\n\\nIf a message is sent to a Slack thread belonging to an archived conversation, the Slack snap-in creates a new follow-up conversation, and all messages sync to this new conversation.\\n\\n![]()\\n\\nA Slack channel can be linked to only one DevRev account workspace, and vice versa.\\n\\nConversation roll window\\n------------------------\\n\\nTo avoid multiple conversations for related customer messages, a **conversation roll window** is used.\\n\\n* The roll window remains active for five",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-55",
"text": "Set up 2 way message synchronization between a complete Slack channel and DevRev object discussion. | - Slack connection - DevRev object ID - Slack channel ID | N/A |\\n\\nAdditional capabilities and limitations\\n---------------------------------------\\n\\n### 2-way sync between DevRev and Slack\\n\\n* If two-way sync is enabled on an object, new messages received from non-Slack source channels will appear in DevRev but won't sync to the Slack thread.\\n* By default, messages from bots, service",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-36",
"text": "Slack Channel ID in the **Channel ID to send conversation notifications** snap-in configuration as the target to post notifications.\\n\\n* Any new message within tickets in the customer messages panel is also subjected to the same automation.\\n* To prevent notification overload, each conversation or ticket is subject to a five minute cooldown period between notifications. Multiple consecutive messages within this window will not trigger additional notifications.\\n* Notification threads are not",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-34",
"text": "minutes after a conversation is created.\\n* Any new message sent directly in the channel within this time frame is appended to the existing conversation.\\n* A new direct message from the customer resets the roll window timer.\\n* Any message sent from DevRev will be synced to the thread of the first message that initiated the conversation.\\n* Only messages within the thread of the originating message of the conversation are synced.\\n* Messages within Slack threads of follow-ups sent directly to",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-6174_KNOWLEDGE_NODE-30",
"text": "there.\\n\\n![]()\\n\\nSlack end-user experience\\n-------------------------\\n\\nWhen a conversation is converted to a ticket in Slack:\\n\\n* Ticket information appears within the same thread.\\n* All subsequent messages sync with the newly created ticket.\\n* The transition is seamless for the end user.\\n\\nConversation conversion scenarios\\n---------------------------------\\n\\nConsider converting a conversation to a ticket in these scenarios:\\n\\n* Complex issues requiring in-depth investigation\\n*",
"title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-56",
"text": "accounts, or AI agents in DevRev aren\\xe2\\x80\\x99t synced to Slack. To change this, enable the **Sync bot messages from DevRev to Slack** option in snap-in configurations.\\n* The snap-in supports syncing of message edits and deletions between platforms.\\n* Message attachment sync is supported both ways, with a file size limit of 250MB.\\n\\n### Inviting DevRev app to channels\\n\\n* Adding the DevRev app to many Slack channels can be challenging at scale.\\n* Use the /SlackInviteBot command from the",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-40",
"text": "channel determines the sync location in DevRev:\\n\\n* **External/Connect channels:** Syncs with the **Customer Messages** panel.\\n* **Internal channels:** Syncs with the **Internal Discussions** panel.\\n\\nSyncing different panels to separate Slack threads is not supported.\\n\\n![]()\\n\\nOnly shared tickets are synchronized between DevRev and Slack.\\n\\n### Follow-up and merged Tickets\\n\\nThe Slack snap-in supports follow-up and merged tickets.\\n\\n* When two tickets merge, and both have syncing",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-4271_KNOWLEDGE_NODE-28",
"text": "PLuG widget:\\n\\n * The ticket number and basic details appear in the same conversation pane.\\n * Users can click **Details** to view complete ticket information.\\n * If the **Tickets** tab is enabled in PLuG, users can track their ticket status there.\\n\\n### Slack experience\\n\\nWhen a conversation is converted to a ticket in Slack:\\n\\n * Ticket information is sent within the same thread.\\n * All subsequent messages sync with the newly created ticket.\\n * The transition is seamless for the",
"title": "Convert Conversations to Tickets | Conversations | Support | DevRev"
}
] |
0b2df1f4-ecc7-4f8f-a6e6-4a20f6833d6f
|
how to setup an account
|
[
{
"id": "ART-2000_KNOWLEDGE_NODE-25",
"text": "address.\\n\\nAccounts are associated with a workspace. An account can be a part of multiple workspaces at the same time. An account can also be linked to multiple opportunities. Accounts help you keep track of your customer contacts. Contacts are always linked to a workspace or an account.\\n\\nCreate an account\\n-----------------\\n\\nYou can create accounts in the following ways:\\n\\n### Using the DevRev app\\n\\n1. Go to **Accounts** > **+ Account**.\\n2. Fill in the details like account name,",
"title": "Accounts | Computer for Growth Teams | DevRev"
},
{
"id": "ART-2000_KNOWLEDGE_NODE-32",
"text": "an account, go to **Account** > **Workspace** and select **New workspace**.\\n\\n[PreviousComputer for Growth Teams](/docs/product/grow)[NextOpportunities](/docs/product/opportunity)\\n\\n#### On this page\\n\\n* [Create an account](#create-an-account)\\n* [Using the DevRev app](#using-the-devrev-app)\\n* [Bulk import accounts](#bulk-import-accounts)\\n* [Using DevRev APIs](#using-devrev-apis)\\n* [Account attributes](#account-attributes)\\n* [External reference](#external-reference)\\n* [Add a",
"title": "Accounts | Computer for Growth Teams | DevRev"
},
{
"id": "ART-2000_KNOWLEDGE_NODE-26",
"text": "description, websites, domains, type, annual revenue, forecast category, tags, tier, etc.\\n3. Fill in the required fields like external references and owner of the account.\\n4. Click **Create**.\\n\\n### Bulk import accounts\\n\\nTo bulk import accounts, see [Account and contact import](/docs/product/account-contact-import).\\n\\nYou can also use [AirSync](https://docs.devrev.ai/import) to migrate your accounts from various platforms such as Hubspot, Salesforce, Zendesk, Jira, Linear, ServiceNow and",
"title": "Accounts | Computer for Growth Teams | DevRev"
},
{
"id": "ART-2933_KNOWLEDGE_NODE-4",
"text": "request is given below:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"display_name\": \"<account name>\" |\\n| 3 | } |\\n```\\n\\n`display_name` must be of type string and can be any name you want to create the account with.\\n\\n1. Make a POST request to \\xe2\\x80\\x9c<https://api.devrev.ai/accounts.create>\\xe2\\x80\\x9d and include the PAT created in the authorization header of the request along with the payload with replaced IDs.\\n\\n In this example, you are using curl to make the requests but can",
"title": "Account creation | DevRev | Docs"
},
{
"id": "ART-2933_KNOWLEDGE_NODE-5",
"text": "use any tool you prefer.\\n\\n ```\\n | | |\\n | --- | --- |\\n | $ | curl --location \\'https://api.devrev.ai/accounts.create\\' \\\\ |\\n | > | --header \\'Content-Type: application/json\\' \\\\ |\\n | > | --header \\'Accept: application/json\\' \\\\ |\\n | > | --header \\'Authorization: Bearer <PAT>\\' \\\\ |\\n | > | --data \\'{ |\\n | > | \"display_name\": \"John Doe\" |\\n | > | }\\' |\\n ```\\n\\n You receive the following response.\\n\\n ```\\n | | |\\n | --- | --- |\\n | 1 | { |\\n | 2 |",
"title": "Account creation | DevRev | Docs"
},
{
"id": "ART-2933_KNOWLEDGE_NODE-1",
"text": "`accounts-create` and `rev-users.create` API. You can also [create accounts manually in DevRev app](https://docs.devrev.ai/product/customers#add-new-customers).\\nThe `accounts-create` API is used to create [accounts](https://docs.devrev.ai/product/grow#-account) which represents a customer organization and it holds information about the company, including its name, address, industry, domain, and website address.\\n\\nThe `rev-users.create` API is used to create",
"title": "Account creation | DevRev | Docs"
},
{
"id": "ART-2000_KNOWLEDGE_NODE-27",
"text": "more.\\n\\n### Using DevRev APIs\\n\\nYou can create an account using the accounts.create API. Follow the [Create accounts and contacts in DevRev](https://developer.devrev.ai/beta/guides/create-accounts-and-contacts-in-dev-rev) tutorial.\\n\\n### Account attributes\\n\\nAccounts have attributes that can be used to filter them.\\nYou can find all the stock attributes listed in **Settings** > **Object customization** > **Account** > **Stock fields**.\\nThese are the stock attributes that come with",
"title": "Accounts | Computer for Growth Teams | DevRev"
},
{
"id": "ART-2933_KNOWLEDGE_NODE-3",
"text": "associated with a workspace.\\n\\n##### \\n\\nJust want to get a token and get started? This [tutorial](/about/authentication#generate-a-personal-access-token-pat) teaches you the fastest way to get a token.\\n\\nYes\\n\\nNo\\n\\naccounts.create\\n\\nAccount is existing \\n\\'account ID\\'\\n\\nrev-orgs.list with \\n\\'account\\' filter\\n\\nrev-orgs.get with \\n\\'account ID\\'\\n\\nGet rev-org \\'display\\\\_id\\'\\n\\nCreate a \\'rev-user\\' under \\'contact\\'\\n\\nCreate an account\\n-----------------\\n\\nThe payload to make a",
"title": "Account creation | DevRev | Docs"
},
{
"id": "ART-1575_KNOWLEDGE_NODE-0",
"text": "b'Beta\\nAPI Reference accounts Create.\\n\\nPOST https:// api.devrev.ai / accounts.create\\nCreates an account, which is a record representing a customer or an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\ndisplay_name string Required\\nName of the account.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the account.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ndescription string Optional\\nDescription of the",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1252_KNOWLEDGE_NODE-0",
"text": "b'Create Account | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[accounts](/api-reference/accounts/accounts)\\n\\nCreate Account\\n==============\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/accounts.create\\n\\nPOST\\n\\n/accounts.create\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/accounts.create \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -H \"Content-Type:",
"title": "Create Account | DevRev | Docs"
},
{
"id": "ART-1837_KNOWLEDGE_NODE-0",
"text": "b'Beta\\nAPI Reference accounts Create.\\n\\nPOST https:// api.devrev.ai / accounts.create\\nCreates an account, which is a record representing a customer or an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\ndisplay_name string Required\\nName of the account.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the account.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ndescription string Optional\\nDescription of the",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1607_KNOWLEDGE_NODE-0",
"text": "b'Beta\\nAPI Reference accounts Create.\\n\\nPOST https:// api.devrev.ai / accounts.create\\nCreates an account, which is a record representing a customer or an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\ndisplay_name string Required\\nName of the account.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the account.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ndescription string Optional\\nDescription of the",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1302_KNOWLEDGE_NODE-0",
"text": "b'Beta\\nAPI Reference accounts Create.\\n\\nPOST https:// api.devrev.ai / accounts.create\\nCreates an account, which is a record representing a customer or an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\ndisplay_name string Required\\nName of the account.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the account.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ndescription string Optional\\nDescription of the",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1781_KNOWLEDGE_NODE-0",
"text": "b'Beta\\nAPI Reference accounts Create.\\n\\nPOST https:// api.devrev.ai / accounts.create\\nCreates an account, which is a record representing a customer or an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\ndisplay_name string Required\\nName of the account.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the account.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ndescription string Optional\\nDescription of the",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1785_KNOWLEDGE_NODE-0",
"text": "b'Beta\\nAPI Reference accounts Create.\\n\\nPOST https:// api.devrev.ai / accounts.create\\nCreates an account, which is a record representing a customer or an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\ndisplay_name string Required\\nName of the account.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the account.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ndescription string Optional\\nDescription of the",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1597_KNOWLEDGE_NODE-0",
"text": "b'Beta\\nAPI Reference accounts Create.\\n\\nPOST https:// api.devrev.ai / accounts.create\\nCreates an account, which is a record representing a customer or an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\ndisplay_name string Required\\nName of the account.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the account.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ndescription string Optional\\nDescription of the",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1579_KNOWLEDGE_NODE-0",
"text": "b'Beta\\nAPI Reference accounts Create.\\n\\nPOST https:// api.devrev.ai / accounts.create\\nCreates an account, which is a record representing a customer or an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\ndisplay_name string Required\\nName of the account.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the account.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ndescription string Optional\\nDescription of the",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1834_KNOWLEDGE_NODE-0",
"text": "b'Beta\\nAPI Reference accounts Create.\\n\\nPOST https:// api.devrev.ai / accounts.create\\nCreates an account, which is a record representing a customer or an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\ndisplay_name string Required\\nName of the account.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the account.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ndescription string Optional\\nDescription of the",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1978_KNOWLEDGE_NODE-33",
"text": "tickets but also all the tickets raised by the other users from their organization. You can add multiple customer admins from the same customer organization.\\n\\nOnly verified users can login into the portal.\\n\\nTo create a verified user:\\n\\n1. Go to **Accounts** in the DevRev app and create an account.\\n2. Create a contact under **Contacts** and link it to the account.\\n\\n### Set up customer admins\\n\\nTo set up customer admins, follow these steps:\\n\\n1. Log in on your DevRev app with your",
"title": "Customer portal | Computer for Support Teams | DevRev"
},
{
"id": "ART-1300_KNOWLEDGE_NODE-0",
"text": "b'Beta\\nAPI Reference accounts Create.\\n\\nPOST https:// api.devrev.ai / accounts.create\\nCreates an account, which is a record representing a customer or an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\ndisplay_name string Required\\nName of the account.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the account.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ndescription string Optional\\nDescription of the",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1978_KNOWLEDGE_NODE-41",
"text": "If no such contact is found, JIT provisioning automatically creates a user account, allowing immediate access to the portal. This means users can sign up and log in without manual contact creation within the app.\\n* **Existing contacts without mapped accounts**: If a user is already a contact within the app but does not have a mapped account, they can still log in and create a ticket. In this scenario, the login is performed under the default workspace assigned to the contact.\\n* **Account",
"title": "Customer portal | Computer for Support Teams | DevRev"
},
{
"id": "ART-1448_KNOWLEDGE_NODE-4",
"text": "Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nPOST\\n\\n/accounts.create\\n\\n[code]\\n\\n $| curl -X POST https://api.devrev.ai/accounts.create \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer <token>\" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"display_name\": \"foo\" \\n >| }\\'\\n[/code] \\n \\nTry it\\n\\n201accountsCreateExample\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"account\": { \\n 3|",
"title": "Create Account — DevRev | Docs"
},
{
"id": "ART-1779_KNOWLEDGE_NODE-0",
"text": "b'Beta\\nAPI Reference accounts Create.\\n\\nPOST https:// api.devrev.ai / accounts.create\\nCreates an account, which is a record representing a customer or an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\ndisplay_name string Required\\nName of the account.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the account.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ndescription string Optional\\nDescription of the",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1827_KNOWLEDGE_NODE-0",
"text": "b'Beta\\nAPI Reference accounts Create.\\n\\nPOST https:// api.devrev.ai / accounts.create\\nCreates an account, which is a record representing a customer or an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\ndisplay_name string Required\\nName of the account.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the account.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ndescription string Optional\\nDescription of the",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1788_KNOWLEDGE_NODE-0",
"text": "b'Beta\\nAPI Reference accounts Create.\\n\\nPOST https:// api.devrev.ai / accounts.create\\nCreates an account, which is a record representing a customer or an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\ndisplay_name string Required\\nName of the account.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the account.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ndescription string Optional\\nDescription of the",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1636_KNOWLEDGE_NODE-0",
"text": "b'Beta\\nAPI Reference accounts Create.\\n\\nPOST https:// api.devrev.ai / accounts.create\\nCreates an account, which is a record representing a customer or an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\ndisplay_name string Required\\nName of the account.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the account.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ndescription string Optional\\nDescription of the",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1590_KNOWLEDGE_NODE-0",
"text": "b'Beta\\nAPI Reference accounts Create.\\n\\nPOST https:// api.devrev.ai / accounts.create\\nCreates an account, which is a record representing a customer or an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\ndisplay_name string Required\\nName of the account.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the account.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ndescription string Optional\\nDescription of the",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1786_KNOWLEDGE_NODE-0",
"text": "b'Beta\\nAPI Reference accounts Create.\\n\\nPOST https:// api.devrev.ai / accounts.create\\nCreates an account, which is a record representing a customer or an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\ndisplay_name string Required\\nName of the account.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the account.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ndescription string Optional\\nDescription of the",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1308_KNOWLEDGE_NODE-0",
"text": "b'Beta\\nAPI Reference accounts Create.\\n\\nPOST https:// api.devrev.ai / accounts.create\\nCreates an account, which is a record representing a customer or an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\ndisplay_name string Required\\nName of the account.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the account.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ndescription string Optional\\nDescription of the",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1826_KNOWLEDGE_NODE-0",
"text": "b'Beta\\nAPI Reference accounts Create.\\n\\nPOST https:// api.devrev.ai / accounts.create\\nCreates an account, which is a record representing a customer or an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\ndisplay_name string Required\\nName of the account.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the account.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ndescription string Optional\\nDescription of the",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1653_KNOWLEDGE_NODE-0",
"text": "b'Beta\\nAPI Reference accounts Create.\\n\\nPOST https:// api.devrev.ai / accounts.create\\nCreates an account, which is a record representing a customer or an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\ndisplay_name string Required\\nName of the account.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the account.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ndescription string Optional\\nDescription of the",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-2933_KNOWLEDGE_NODE-17",
"text": "cURL with the `account` filter.\\n\\n ```\\n | | |\\n | --- | --- |\\n | $ | curl -G https://api.devrev.ai/rev-orgs.get \\\\ |\\n | > | -H \"Authorization: Bearer <apiKey>\" \\\\ |\\n | > | -d account=ACC-12345 \\\\ |\\n ```\\n\\n1. Make a POST request to \\xe2\\x80\\x9c<https://api.devrev.ai/rev-users.create>\\xe2\\x80\\x9d to create a rev-user.\\n\\n In the request, set `rev_org` to the value of the `display_id` from the previous reponse.\\n\\n ```\\n | | |\\n | --- | --- |\\n | $ | curl",
"title": "Account creation | DevRev | Docs"
},
{
"id": "ART-1543_KNOWLEDGE_NODE-0",
"text": "b'Beta\\nAPI Reference accounts Create.\\n\\nPOST https://api.devrev.ai / accounts.create\\n\\nCreates an account, which is a record representing a customer or an organization.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\ndisplay_name string Required\\n\\nName of the account.\\n\\nartifacts list of strings Optional\\n\\nThe IDs of the artifacts to associate with the account.\\n\\ncustom_fields map from strings to any Optional\\n\\nApplication-defined custom fields.\\n\\ndescription string",
"title": "Metric Definitions List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1805_KNOWLEDGE_NODE-0",
"text": "b'Beta\\nAPI Reference accounts Create.\\n\\nPOST https:// api.devrev.ai / accounts.create\\nCreates an account, which is a record representing a customer or an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\ndisplay_name string Required\\nName of the account.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the account.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ndescription string Optional\\nDescription of the",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1566_KNOWLEDGE_NODE-0",
"text": "b'Beta\\nAPI Reference accounts Create.\\n\\nPOST https://api.devrev.ai / accounts.create\\n\\nCreates an account, which is a record representing a customer or an organization.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\ndisplay_name string Required\\n\\nName of the account.\\n\\nartifacts list of strings Optional\\n\\nThe IDs of the artifacts to associate with the account.\\n\\ncustom_fields map from strings to any Optional\\n\\nApplication-defined custom fields.\\n\\ndescription string",
"title": "Transition (Beta) — DevRev | Docs"
},
{
"id": "ART-1637_KNOWLEDGE_NODE-0",
"text": "b'Beta\\nAPI Reference accounts Create.\\n\\nPOST https:// api.devrev.ai / accounts.create\\nCreates an account, which is a record representing a customer or an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\ndisplay_name string Required\\nName of the account.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the account.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ndescription string Optional\\nDescription of the",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1806_KNOWLEDGE_NODE-0",
"text": "b'Beta\\nAPI Reference accounts Create.\\n\\nPOST https:// api.devrev.ai / accounts.create\\nCreates an account, which is a record representing a customer or an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\ndisplay_name string Required\\nName of the account.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the account.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ndescription string Optional\\nDescription of the",
"title": "Self Post — DevRev | Docs"
},
{
"id": "ART-1650_KNOWLEDGE_NODE-0",
"text": "b'Beta\\nAPI Reference accounts Create.\\n\\nPOST https:// api.devrev.ai / accounts.create\\nCreates an account, which is a record representing a customer or an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\ndisplay_name string Required\\nName of the account.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the account.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ndescription string Optional\\nDescription of the",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1307_KNOWLEDGE_NODE-0",
"text": "b'Beta\\nAPI Reference accounts Create.\\n\\nPOST https:// api.devrev.ai / accounts.create\\nCreates an account, which is a record representing a customer or an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\ndisplay_name string Required\\nName of the account.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the account.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ndescription string Optional\\nDescription of the",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1825_KNOWLEDGE_NODE-0",
"text": "b'Beta\\nAPI Reference accounts Create.\\n\\nPOST https:// api.devrev.ai / accounts.create\\nCreates an account, which is a record representing a customer or an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\ndisplay_name string Required\\nName of the account.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the account.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ndescription string Optional\\nDescription of the",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1791_KNOWLEDGE_NODE-0",
"text": "b'Beta\\nAPI Reference accounts Create.\\n\\nPOST https:// api.devrev.ai / accounts.create\\nCreates an account, which is a record representing a customer or an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\ndisplay_name string Required\\nName of the account.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the account.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ndescription string Optional\\nDescription of the",
"title": "Self Delete — DevRev | Docs"
}
] |
a49e2fa4-92b1-434b-b3af-e993c8692331
|
predictive analytics for case volume and resource planning
|
[
{
"id": "ART-3184_KNOWLEDGE_NODE-13",
"text": "**Predictive Data Modeling**: Consolidated operational data with proactive alerts that surface issues before they impact customers\\n\\n### The benefits\\n\\n* Eliminated manual tracking through intelligent automation of customer activities\\n* Achieved unified insights with AI-powered centralized dashboards that autonomously generate reports and recommendations\\n* Enabled seamless scalability for reseller network growth through predictive resource allocation\\n* Reached nearly 100% customer",
"title": "LuxCreo boosts operational efficiency and agility with DevRev"
}
] |
464b1269-11a0-4f66-9b7f-ee3b72cb0a54
|
Response time tracking per channel with SLA compliance
|
[
{
"id": "ART-1986_KNOWLEDGE_NODE-26",
"text": "level.\\nSLAs help ensure that your customers receive timely responses and resolutions to inquiries.\\n\\nPolicy users can set SLA breach and warning targets for three metrics: *first response*, *next response*, and *full resolution*. Each metric has its own breach and warning target. You can specify whether the metrics are calculated using calendar hours or business hours while defining breach and warning targets.\\n\\nCreate an SLA\\n-------------\\n\\n1. Go to **Settings > SLA > + Create**.\\n2. In",
"title": "Service-level agreement | Computer for Support Teams | DevRev"
},
{
"id": "ART-4181_KNOWLEDGE_NODE-16",
"text": "breach\\n\\n![]()\\n\\nSLA timers on Conversation and Ticket panel\\n\\nEquip agents with the comprehensive context they need to prioritize based on service level commitments\\n\\n![]()\\n\\nSLA timers on Conversation and Ticket panel\\n\\nEquip agents with the comprehensive context they need to prioritize based on service level commitments\\n\\n![]()\\n\\nView SLA targets in Inbox view\\n\\nSee critical SLA information directly on your Omnichannel Inbox to prioritize and take action before breach",
"title": "Support like a lightning fast pit-crew"
},
{
"id": "ART-4181_KNOWLEDGE_NODE-18",
"text": "breach\\n\\n![]()\\n\\nSLA timers on Conversation and Ticket panel\\n\\nEquip agents with the comprehensive context they need to prioritize based on service level commitments\\n\\n![]()\\n\\nSLA timers on Conversation and Ticket panel\\n\\nEquip agents with the comprehensive context they need to prioritize based on service level commitments\\n\\n![]()\\n\\nView SLA targets in Inbox view\\n\\nSee critical SLA information directly on your Omnichannel Inbox to prioritize and take action before breach",
"title": "Support like a lightning fast pit-crew"
},
{
"id": "ART-4181_KNOWLEDGE_NODE-20",
"text": "breach\\n\\n![]()\\n\\nSLA timers on Conversation and Ticket panel\\n\\nEquip agents with the comprehensive context they need to prioritize based on service level commitments\\n\\n![]()\\n\\nSLA timers on Conversation and Ticket panel\\n\\nEquip agents with the comprehensive context they need to prioritize based on service level commitments\\n\\n![]()\\n\\nView SLA targets in Inbox view\\n\\nSee critical SLA information directly on your Omnichannel Inbox to prioritize and take action before breach",
"title": "Support like a lightning fast pit-crew"
},
{
"id": "ART-4181_KNOWLEDGE_NODE-14",
"text": "Exceptions\\n\\nCreate Exceptions for customers who require special treatment, overriding the Assignment Rules when necessary\\n\\n![]()\\n\\nDefault SLA Fallback\\n\\nAuto-assign a Default SLA to customers who do not meet any of the specified criteria\\n\\nEffortlessly monitor SLAs everywhere\\n====================================\\n\\nKeep track of SLAs on all channels. Focus on the most critical or time-sensitive customer issues, ensuring rapid",
"title": "Support like a lightning fast pit-crew"
},
{
"id": "ART-1508_KNOWLEDGE_NODE-21",
"text": "\"string\", |\\n| 357 | \"sla_type\": \"external\" |\\n| 358 | }, |\\n| 359 | \"sla_policy_id\": \"string\", |\\n| 360 | \"stage\": \"string\", |\\n| 361 | \"status\": \"string\" |\\n| 362 | }, |\\n| 363 | \"stage\": \"breached\", |\\n| 364 | \"target_time\": \"2023-01-01T12:00:00.000Z\" |\\n| 365 | }, |\\n| 366 | \"sla_tracker\": { |\\n| 367 | \"id\": \"string\", |\\n| 368 | \"applies_to_type\": \"conversation\", |\\n| 369 | \"display_id\": \"string\" |\\n| 370 | }, |\\n| 371 | \"source_channel\": \"string\", |\\n| 372 | \"source_channel_v2\": { |\\n| 373",
"title": "Export Conversations | DevRev | Docs"
},
{
"id": "ART-4177_KNOWLEDGE_NODE-6",
"text": "through tickets](https://vimeo.com/1027660342)[![]()\\n\\nUnderstanding Support Analytics and SLAs\\n\\nExplore actionable insights and trends in customer experience metrics with our support analytics dashboard](https://vimeo.com/1027659562)[![]()\\n\\nInteractive walkthrough of SLA tracking\\n\\nLearn how to use DevRev track SLAs of tickets, to ensure that your customer's requests are always responded to in time.](https://devrev.navattic.com/bv10lxn)\\n\\nBuild Products, Not",
"title": "DevRev University - DevRev for Startups"
},
{
"id": "ART-15325_KNOWLEDGE_NODE-16",
"text": "|\\n| 271 | \"stage\": \"breached\", |\\n| 272 | \"target_time\": \"2023-01-01T12:00:00.000Z\" |\\n| 273 | }, |\\n| 274 | \"sla_tracker\": { |\\n| 275 | \"id\": \"string\", |\\n| 276 | \"applies_to_type\": \"conversation\", |\\n| 277 | \"display_id\": \"string\" |\\n| 278 | }, |\\n| 279 | \"source_channel\": \"string\", |\\n| 280 | \"source_channel_v2\": { |\\n| 281 | \"id\": \"string\", |\\n| 282 | \"display_id\": \"string\" |\\n| 283 | }, |\\n| 284 | \"stage\": { |\\n| 285 | \"name\": \"string\" |\\n| 286 | }, |\\n| 287 | \"tags\": [ |\\n| 288 | { |\\n|",
"title": "List Conversations | DevRev | Docs"
},
{
"id": "ART-17231_KNOWLEDGE_NODE-153",
"text": "this object, which is used to track the SLA metrics. |\\n| `source_channel_v2` | reference\\xe2\\x86\\x92[#record:external\\\\_communication\\\\_channel] | | Source channel ID of the ticket |\\n| `stage` | enum | \\xe2\\x9c\\x94\\xef\\xb8\\x8e | Stage of the object |\\n| `tags` | reference (collection)\\xe2\\x86\\x92[#record:tag] | | Tags associated with the object |\\n| `target_close_date` | timestamp | | Timestamp when the work is expected to be complete |\\n| `title` | text | \\xe2\\x9c\\x94\\xef\\xb8\\x8e | Title",
"title": "Supported DevRev object types | DevRev | Docs"
},
{
"id": "ART-15319_KNOWLEDGE_NODE-16",
"text": "\"string\", |\\n| 267 | \"stage\": \"string\", |\\n| 268 | \"status\": \"string\" |\\n| 269 | }, |\\n| 270 | \"stage\": \"breached\", |\\n| 271 | \"target_time\": \"2023-01-01T12:00:00.000Z\" |\\n| 272 | }, |\\n| 273 | \"sla_tracker\": { |\\n| 274 | \"id\": \"string\", |\\n| 275 | \"applies_to_type\": \"conversation\", |\\n| 276 | \"display_id\": \"string\" |\\n| 277 | }, |\\n| 278 | \"source_channel\": \"string\", |\\n| 279 | \"source_channel_v2\": { |\\n| 280 | \"id\": \"string\", |\\n| 281 | \"display_id\": \"string\" |\\n| 282 | }, |\\n| 283 | \"stage\":",
"title": "Get Conversation (POST) | DevRev | Docs"
},
{
"id": "ART-15321_KNOWLEDGE_NODE-16",
"text": "\"string\", |\\n| 268 | \"stage\": \"string\", |\\n| 269 | \"status\": \"string\" |\\n| 270 | }, |\\n| 271 | \"stage\": \"breached\", |\\n| 272 | \"target_time\": \"2023-01-01T12:00:00.000Z\" |\\n| 273 | }, |\\n| 274 | \"sla_tracker\": { |\\n| 275 | \"id\": \"string\", |\\n| 276 | \"applies_to_type\": \"conversation\", |\\n| 277 | \"display_id\": \"string\" |\\n| 278 | }, |\\n| 279 | \"source_channel\": \"string\", |\\n| 280 | \"source_channel_v2\": { |\\n| 281 | \"id\": \"string\", |\\n| 282 | \"display_id\": \"string\" |\\n| 283 | }, |\\n| 284 | \"stage\":",
"title": "List Conversations (POST) | DevRev | Docs"
},
{
"id": "ART-15323_KNOWLEDGE_NODE-16",
"text": "\"target_time\": \"2023-01-01T12:00:00.000Z\" |\\n| 272 | }, |\\n| 273 | \"sla_tracker\": { |\\n| 274 | \"id\": \"string\", |\\n| 275 | \"applies_to_type\": \"conversation\", |\\n| 276 | \"display_id\": \"string\" |\\n| 277 | }, |\\n| 278 | \"source_channel\": \"string\", |\\n| 279 | \"source_channel_v2\": { |\\n| 280 | \"id\": \"string\", |\\n| 281 | \"display_id\": \"string\" |\\n| 282 | }, |\\n| 283 | \"stage\": { |\\n| 284 | \"name\": \"string\" |\\n| 285 | }, |\\n| 286 | \"tags\": [ |\\n| 287 | { |\\n| 288 | \"tag\": { |\\n| 289 | \"id\": \"string\",",
"title": "Get Conversation | DevRev | Docs"
}
] |
7d054456-fc7c-4a51-a13a-cb11fcad186c
|
cannot see or access onboarding tasks
|
[
{
"id": "ART-1958_KNOWLEDGE_NODE-28",
"text": "are not authorized to perform this action\". Relevant buttons may be inactive.\\nUsers can contact the organization\\'s admins to enable access in that case.\\n\\n![]()\\n\\nGranting access permissions\\n---------------------------\\n\\nUsers are granted access permissions to dashboards or reports through MFZ policies and sharing.\\n\\n### MFZ policies\\n\\nUse of MFZ policies facilitates the need to grant access to a wider group of users.\\n\\nAn org admin has permission to define and enable roles, in",
"title": "Access control | Computer by DevRev | DevRev"
}
] |
c6ec219d-4967-4986-835f-55b84483fbb2
|
manually create a linked ticket
|
[
{
"id": "ART-1947_KNOWLEDGE_NODE-36",
"text": "Conversations can be immediately linked to a ticket, a ticket to an issue and subsequently to a part (product capabilities and features).\\n\\n| Link | Control |\\n| --- | --- |\\n| Conversation \\xe2\\x86\\x92 Ticket | Open the conversation and click **Tickets > + Link tickets**. Either create a new ticket or select an existing ticket. |\\n| Ticket \\xe2\\x86\\x92 Issue | Open the ticket and click **Issues > + Link issues**. Either create a new issue or select an existing issue. |\\n| Issue \\xe2\\x86\\x92",
"title": "Apps | Computer by DevRev | DevRev"
},
{
"id": "ART-1979_KNOWLEDGE_NODE-39",
"text": "other tickets or issues that relate to this ticket, click **Link Records** and select the relevant items.\\n7. If you would like to immediately create another ticket, select **Create multiple**.\\n8. Click **Create**.\\n\\nIf a ticket is created from an existing conversation, then the ticket's title and description are populated automatically from the conversation.\\n\\n![]()\\n\\nYou can create a child issue by clicking **+ Link issue** > **Add a child issue**. You can link the other existing issue as",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-1947_KNOWLEDGE_NODE-37",
"text": "Ticket | Open the issue and click **Tickets > + Link tickets**. Either create a new ticket or select an existing ticket. |\\n| Issue \\xe2\\x86\\x92 Issue | Open the issue and click **Issues > + Link issues**. Either create a new issue or select an existing issue. |\\n\\n| Conversation | Ticket | Issue |\\n| --- | --- | --- |\\n| | | > |\\n\\nTo delete a ticket or issue, select the work item in the list view and click the **Delete** icon in the taskbar that appears.\\n\\n![]()\\n\\n[PreviousCore",
"title": "Apps | Computer by DevRev | DevRev"
},
{
"id": "ART-6174_KNOWLEDGE_NODE-28",
"text": "tickets\\n--------------------------------\\n\\n**Manual conversion**\\n\\nGo to the conversation record pane and select **Convert to Ticket** to create a new ticket from the conversation.\\n\\n![]()\\n\\n**Automated conversion via workflows**\\n\\nSet up automated [workflows](./workflow-engine) to convert conversations to tickets based on specific triggers:\\n\\n* When a conversation meets defined criteria\\n* When the AI agent identifies an issue requiring escalation\\n* According to custom business",
"title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev"
},
{
"id": "ART-1992_KNOWLEDGE_NODE-32",
"text": "other [tickets](./tickets) or issues that relate to this issue, click **Link Records** and select the relevant items.\\n7. If you would like to immediately create another issue, select **Create multiple**.\\n8. Click **Create**.\\n\\nTags\\n----\\n\\n* Stalled\\n* Priority/Escalated\\n* Fast/Slow Moving\\n* Blocked\\n* Resolution: [*values*]\\n* Impact: [*values*]\\n* Reason: [*values*]\\n\\nAn *autonomous issue* is an issue created automatically from an external event, such as a new VCS branch or pull",
"title": "Issues | Computer for Builders | DevRev"
},
{
"id": "ART-15664_KNOWLEDGE_NODE-9",
"text": "--location \\'https://api.devrev.ai/links.create\\' \\\\ |\\n| > | --header \\'Content-Type: application/json\\' \\\\ |\\n| > | --header \\'Authorization: Bearer <TOKEN>\\' \\\\ |\\n| > | --data \\'{ |\\n| > | \"custom_link_type\": \"don:core:dvrv-us-1:devo/demo:custom_link_type/1\", |\\n| > | \"link_type\": \"custom_link\", |\\n| > | \"source\": \"don:core:dvrv-us-1:devo/demo:ticket/1\", |\\n| > | \"target\": \"don:core:dvrv-us-1:devo/demo:custom_object/campaign/1\" |\\n| > | }\\' |\\n```\\n\\n##### \\n\\nWhen creating a link:\\n\\n* Set",
"title": "Links | DevRev | Docs"
},
{
"id": "ART-2048_KNOWLEDGE_NODE-27",
"text": "allows you to create parent/child relationships between issues, you cannot do the same with tickets. If your workflow requires manual creation of parent/child relationships in DevRev work items, you should use issues. If that is not a requirement and tickets are preferred for another reason, you can specify tickets as the target for ClickUp tasks.\\n\\nImport from ClickUp\\n-------------------\\n\\nFollow the steps below to import from ClickUp:\\n\\n1. In **Marketplace**, search for **ClickUp** and",
"title": "ClickUp AirSync | AirSync | Snap-ins | DevRev"
},
{
"id": "ART-4271_KNOWLEDGE_NODE-26",
"text": "conversation metadata including: \\n * Source channel\\n * Customer account information\\n * External members added as **reported by** on the ticket\\n * An AI-generated ticket title and description based on customer messages.\\n\\n### How to convert Conversations to Tickets\\n\\n**Manual Conversion**\\n\\nTo manually convert a conversation to a ticket:\\n\\n 1. Open the conversation record pane view.\\n 2. Click **Convert to Ticket** to initiate the conversion.\\n\\n**Automated Conversion",
"title": "Convert Conversations to Tickets | Conversations | Support | DevRev"
},
{
"id": "ART-2046_KNOWLEDGE_NODE-29",
"text": "Ticket** button to create a ticket in DevRev by filling necessary attributes. You can turn this feature off in the app configuration if you want.\\n* To view comments on the tickets linked to the discussions that support teams had with customers or internally on DevRev, head over to the DevRev activity tab which is present in the same line as the **Comments** tab of Jira.\\n* To send comments from the Jira issue to the DevRev ticket, select the ticket from the dropdown, type in the comment, and",
"title": "DevRev for Jira app | Jira Software AirSync | AirSync | Snap-ins | DevRev"
},
{
"id": "ART-1947_KNOWLEDGE_NODE-32",
"text": "same conversation. This means you do not need to ask your external users to write in separately about each topic they\\'d like to discuss, while the workspace can still track each item separately.\\n\\nIn the DevRev app, a support engineer can create a ticket based on a conversation they had with someone using the Plug widget. This ticket and conversation are linked.\\n\\nA ticket should describe what the external user is experiencing in a language that\\'s familiar to them. Developer-specific",
"title": "Apps | Computer by DevRev | DevRev"
},
{
"id": "ART-2046_KNOWLEDGE_NODE-28",
"text": "configuration.\\n3. Enable the desired features by toggling them on. Only enabled features will be visible to all users within your Atlassian organization.\\n\\nFeatures\\n--------\\n\\n* The side panel on the Jira issue displays DevRev tickets linked to the Jira issue and their counterparts in DevRev.\\n\\n ![]()\\n* If there are multiple tickets linked to the issue, look at the details of each ticket by selecting a ticket with the dropdown field provided.\\n\\n ![]()\\n* Click on the **Create New",
"title": "DevRev for Jira app | Jira Software AirSync | AirSync | Snap-ins | DevRev"
},
{
"id": "ART-1558_KNOWLEDGE_NODE-278",
"text": "authorization request.\\n\\nAPI Reference links Create.\\n\\nPOST https://api.devrev.ai / links.create\\n\\nCreates a link between two objects to indicate a relationship.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\n\\nType of link used to define the relationship.\\n\\nShow 13 enum values\\nsource string Required\\n\\nThe ID of the source object.\\n\\ntarget string Required\\n\\nThe ID of the target object.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9",
"title": "Metric Definitions List (Beta) — DevRev | Docs"
},
{
"id": "ART-1551_KNOWLEDGE_NODE-278",
"text": "authorization request.\\n\\nAPI Reference links Create.\\n\\nPOST https://api.devrev.ai / links.create\\n\\nCreates a link between two objects to indicate a relationship.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\n\\nType of link used to define the relationship.\\n\\nShow 13 enum values\\nsource string Required\\n\\nThe ID of the source object.\\n\\ntarget string Required\\n\\nThe ID of the target object.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9",
"title": "Update (Beta) — DevRev | Docs"
},
{
"id": "ART-1547_KNOWLEDGE_NODE-278",
"text": "authorization request.\\n\\nAPI Reference links Create.\\n\\nPOST https://api.devrev.ai / links.create\\n\\nCreates a link between two objects to indicate a relationship.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\n\\nType of link used to define the relationship.\\n\\nShow 13 enum values\\nsource string Required\\n\\nThe ID of the source object.\\n\\ntarget string Required\\n\\nThe ID of the target object.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9",
"title": "Get Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1545_KNOWLEDGE_NODE-278",
"text": "authorization request.\\n\\nAPI Reference links Create.\\n\\nPOST https://api.devrev.ai / links.create\\n\\nCreates a link between two objects to indicate a relationship.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\n\\nType of link used to define the relationship.\\n\\nShow 13 enum values\\nsource string Required\\n\\nThe ID of the source object.\\n\\ntarget string Required\\n\\nThe ID of the target object.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9",
"title": "Create (Beta) — DevRev | Docs"
},
{
"id": "ART-1564_KNOWLEDGE_NODE-278",
"text": "authorization request.\\n\\nAPI Reference links Create.\\n\\nPOST https://api.devrev.ai / links.create\\n\\nCreates a link between two objects to indicate a relationship.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\n\\nType of link used to define the relationship.\\n\\nShow 13 enum values\\nsource string Required\\n\\nThe ID of the source object.\\n\\ntarget string Required\\n\\nThe ID of the target object.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9",
"title": "List (Beta) — DevRev | Docs"
},
{
"id": "ART-1543_KNOWLEDGE_NODE-278",
"text": "authorization request.\\n\\nAPI Reference links Create.\\n\\nPOST https://api.devrev.ai / links.create\\n\\nCreates a link between two objects to indicate a relationship.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\n\\nType of link used to define the relationship.\\n\\nShow 13 enum values\\nsource string Required\\n\\nThe ID of the source object.\\n\\ntarget string Required\\n\\nThe ID of the target object.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9",
"title": "Metric Definitions List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1549_KNOWLEDGE_NODE-278",
"text": "authorization request.\\n\\nAPI Reference links Create.\\n\\nPOST https://api.devrev.ai / links.create\\n\\nCreates a link between two objects to indicate a relationship.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\n\\nType of link used to define the relationship.\\n\\nShow 13 enum values\\nsource string Required\\n\\nThe ID of the source object.\\n\\ntarget string Required\\n\\nThe ID of the target object.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9",
"title": "List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1566_KNOWLEDGE_NODE-278",
"text": "authorization request.\\n\\nAPI Reference links Create.\\n\\nPOST https://api.devrev.ai / links.create\\n\\nCreates a link between two objects to indicate a relationship.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\n\\nType of link used to define the relationship.\\n\\nShow 13 enum values\\nsource string Required\\n\\nThe ID of the source object.\\n\\ntarget string Required\\n\\nThe ID of the target object.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9",
"title": "Transition (Beta) — DevRev | Docs"
}
] |
4499debc-fcfe-453e-8460-de2f35a60625
|
toggle to enforce the condition meaning in workflow
|
[
{
"id": "ART-1645_KNOWLEDGE_NODE-54",
"text": "] \\n >| } \\n >| ] \\n >| }\\'\\n[/code] \\n \\nAny attempt to update a _bug_ object to the _completed_ stage without populating the _RCA_ field is rejected.\\n\\nThe supported operators are `==`, `!=`, `>`, `>=`, `<`, `<=`. The `expression` is a boolean expression that must return a boolean value.\\n\\nThe `effects` array contains the list of effects of the condition. The following effects are supported:\\n\\n * `require`: Whether the field must be set for the condition",
"title": "Object customization (Beta) — DevRev | Docs"
},
{
"id": "ART-15487_KNOWLEDGE_NODE-50",
"text": "\"fields\": [ \"custom_fields.rca\" ], |\\n| > | \"require\": true |\\n| > | } |\\n| > | ] |\\n| > | } |\\n| > | ] |\\n| > | }\\' |\\n```\\n\\nAny attempt to update a *bug* object to the *completed* stage without populating\\nthe *RCA* field is rejected.\\n\\nThe supported operators are `==`, `!=`, `&&`, `||`. The `expression` is a\\nbinary expression that must return a boolean value.\\n\\nThe `effects` array contains the list of effects of the condition. The following effects are supported:\\n\\n* `require`: Whether",
"title": "Object customization | DevRev | Docs"
}
] |
ac9c8c75-b428-420a-99b1-20eff816a887
|
slack reply not pulled in
|
[
{
"id": "ART-2035_KNOWLEDGE_NODE-41",
"text": "Slack threads, all the messages from both Slack threads reach only the primary ticket in DevRev, while messages from DevRev only sync to the primary ticket\\xe2\\x80\\x99s Slack thread.\\n* If only one ticket has a syncing Slack thread, that thread syncs with the primary ticket.\\n* No messages from the duplicate ticket sync to Slack.\\n* If a ticket is immutable but receives a new customer message in its Slack thread, a follow-up ticket is automatically created for future discussions.\\n\\n### New",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-57",
"text": "**Slack snap-in event discussions panel** to automatically invite the DevRev app to all public channels.\\n + Private channels still require manual addition.\\n\\n### When sync is not possible\\n\\nIf sync isn\\xe2\\x80\\x99t possible, the form will display a clear warning. Possible reasons include:\\n\\n* The thread is already in sync with another DevRev object.\\n* Sync is not supported for the object in the given Slack channel.\\n* The DevRev app is not a member of the channel.\\n* The channel is",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-35",
"text": "the channel will not sync to DevRev.\\n\\nConversation notifications\\n--------------------------\\n\\nAny new message added to a conversation within your DevRev workspace, regardless of its originating source channel or platform, can trigger a notification in a designated Slack channel, helping your team stay updated on customer interactions.\\n\\n### To enable conversation notifications\\n\\n1. Turn on **Enable the conversation notification feature** in the Slack snap-in configuration.\\n2. Provide a",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-33",
"text": "DevRev app.\\n\\nIf a message is sent to a Slack thread belonging to an archived conversation, the Slack snap-in creates a new follow-up conversation, and all messages sync to this new conversation.\\n\\n![]()\\n\\nA Slack channel can be linked to only one DevRev account workspace, and vice versa.\\n\\nConversation roll window\\n------------------------\\n\\nTo avoid multiple conversations for related customer messages, a **conversation roll window** is used.\\n\\n* The roll window remains active for five",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-40",
"text": "channel determines the sync location in DevRev:\\n\\n* **External/Connect channels:** Syncs with the **Customer Messages** panel.\\n* **Internal channels:** Syncs with the **Internal Discussions** panel.\\n\\nSyncing different panels to separate Slack threads is not supported.\\n\\n![]()\\n\\nOnly shared tickets are synchronized between DevRev and Slack.\\n\\n### Follow-up and merged Tickets\\n\\nThe Slack snap-in supports follow-up and merged tickets.\\n\\n* When two tickets merge, and both have syncing",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-48",
"text": "channel.\\n\\n1. **Sync messages with the thread (for incidents created from Slack)**\\n\\n* Works only for incidents created from Slack.\\n* It syncs messages with the originating thread, similar to ticket and issue work items.\\n\\n1. **Sync messages with the notification thread**\\n\\n* Syncs with the thread of the incident notification sent on the channel mentioned in the **Channel ID to send incident notifications** configuration.\\n* Works for all incidents irrespective of source channel or",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-34",
"text": "minutes after a conversation is created.\\n* Any new message sent directly in the channel within this time frame is appended to the existing conversation.\\n* A new direct message from the customer resets the roll window timer.\\n* Any message sent from DevRev will be synced to the thread of the first message that initiated the conversation.\\n* Only messages within the thread of the originating message of the conversation are synced.\\n* Messages within Slack threads of follow-ups sent directly to",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-55",
"text": "Set up 2 way message synchronization between a complete Slack channel and DevRev object discussion. | - Slack connection - DevRev object ID - Slack channel ID | N/A |\\n\\nAdditional capabilities and limitations\\n---------------------------------------\\n\\n### 2-way sync between DevRev and Slack\\n\\n* If two-way sync is enabled on an object, new messages received from non-Slack source channels will appear in DevRev but won't sync to the Slack thread.\\n* By default, messages from bots, service",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-58",
"text": "private or a DM.\\n\\n> In such cases, the object can still be created, but without two-way sync.\\n\\nDevRev object customization support\\n-----------------------------------\\n\\nThe Slack snap-in honors DevRev\\xe2\\x80\\x99s object customizations, including:\\n\\n* Custom fields and subtypes\\n* Stock field overrides\\n* Slack-specific client overrides\\n* Summary view card\\n\\nThe summary view card of all objects can be customized.\\n\\n* Only fields marked with **Show in Summary = true** in object",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-30",
"text": "organization.\\n\\nList of available commands\\n--------------------------\\n\\nAfter installation, visit your Slack workspace and enter the command /devrev help. A pop-up modal will display all the available commands.\\n\\nCreate DevRev conversations from Slack\\n--------------------------------------\\n\\nThe snap-in enables support teams to manage customer interactions directly from DevRev. You can enable this feature by toggling the **Sync conversations from Slack to DevRev** setting.\\n\\nTo start",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-4021_KNOWLEDGE_NODE-25",
"text": "scraped.\\n\\nConfiguration\\n-------------\\n\\n1. Create a Slack app for your workspace at <https://api.slack.com/apps>.\\n2. In the **App features** section, generate agent token in **OAuth & Permissions**.\\n3. Give the app agent the following access:\\n\\n * channels:history\\n * channels:read\\n * groups:history\\n4. Invite the agent to the workspace.\\n5. Save the agent access token as a connection of type snap-in secret in the DevRev app.\\n\\nHow to use\\n----------\\n\\n1. Install the",
"title": "Slack scraper | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-54",
"text": "given DevRev user - Can be used to later send direct messages to the user on the Slack using Send message to Slack node. | - Slack connection - DevRev user id | - Slack user id |\\n| Start Thread Sync | - Set up 2 way message synchronization between a Slack thread and a DevRev object discussion. | - Slack connection - DevRev Object ID - Slack channel ID - Slack thread ID (message ID of parent message, returned by send message to Slack workflow node) | N/A |\\n| Start Channel Sync | -",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-42",
"text": "ticket notifications\\n\\n* Enable through the **Notify on new ticket creation** snap-in configuration.\\n* Provide a Slack channel ID in the **Channel ID to send ticket notifications** configuration.\\n* Snap-in will send notifications to the target channel whenever a new ticket is created, regardless of the source channel or platform.\\n* Notification message threads are **not** synced between platforms.\\n\\n### Notifications for ticket state update\\n\\n* Enable through **Notify on ticket state",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-4199_KNOWLEDGE_NODE-27",
"text": "message.channels.\\n7. Add this custom app and the **DevRev Slack Bot** into the Slack channel from which you want to create the DevRev object.\\n\\nConfigure DevRev\\n----------------\\n\\n1. Add the Slack Signing Secret and Slack Bot Token copied from the custom Slack bot app.\\n2. Add the channel IDs for either incidents, tickets or issues.\\n3. Click the respective buttons to enable the sync between threads.\\n4. Select the part ID to associate a particular part.\\n5. Click **Save** and copy the",
"title": "Slack message agent | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-44",
"text": "directly from Slack:\\n\\n* Using the /devrev create-issue command.\\n* Using the **Create a new issue** message action.\\n\\nBoth the options open a new pop-up modal with a new issue form. Some of the fields are pre-populated based on the messages in the thread.\\n\\n* The **Share with everyone** functionality operates identically to ticket creation. Only shared issues are synchronized between the platforms.\\n* The messages are always synced in the **Internal Discussions** panel with Slack thread.\\n*",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-968_KNOWLEDGE_NODE-2",
"text": "The tagging will occur once the\\nticket is created from a Slack channel provided the ticket-share acknowledgment\\ncheckbox is enabled(the conversation stays private otherwise). This app connects with a\\nSnapin at DevRev that would invoke the app at the time of ticket creation. The ticket\\xe2\\x80\\x99s\\nsource(Slack) serves as the delimiter.\\nYield:\\n\\nThe group\\xe2\\x80\\x99s ID is obtained within the configuration of the snapin at DevRev\\nas shown below.\\n\\nGroup ID to be obtained from within the",
"title": "Rocketium: On call Tagging - Slack"
},
{
"id": "ART-6174_KNOWLEDGE_NODE-30",
"text": "there.\\n\\n![]()\\n\\nSlack end-user experience\\n-------------------------\\n\\nWhen a conversation is converted to a ticket in Slack:\\n\\n* Ticket information appears within the same thread.\\n* All subsequent messages sync with the newly created ticket.\\n* The transition is seamless for the end user.\\n\\nConversation conversion scenarios\\n---------------------------------\\n\\nConsider converting a conversation to a ticket in these scenarios:\\n\\n* Complex issues requiring in-depth investigation\\n*",
"title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev"
},
{
"id": "ART-1979_KNOWLEDGE_NODE-61",
"text": "following scenarios can lead to the creation of follow up ticket:\\n\\n* Customers communicated on an archived/immutable ticket from any channel such as email.\\n* Customer communicated on a merged ticket and the primary ticket is also archived.\\n\\nAfter creation of a follow up ticket the customer messages will reflect only on the new followup ticket and the customer will continue to see response on the same thread in channels like email & slack. The user can continue responding on the new follow",
"title": "Tickets | Computer for Support Teams | DevRev"
}
] |
f57edb8e-1ab2-4039-8489-111cb998eb70
|
make articles visible to public without login
|
[
{
"id": "ART-1985_KNOWLEDGE_NODE-35",
"text": "and no longer required can be removed by archiving them.\\n\\nVisibility settings\\n-------------------\\n\\n### Article visibility\\n\\nTo control who can view the articles, open the **Visible to** menu. This displays all external groups that the article can be shared with. By default, the following groups are available:\\n\\n* **Customers**: Allows public access without verification.\\n\\n ![]()\\n\\n Public access requires the public portal to be enabled. If the public portal is not enabled, only",
"title": "Articles | Knowledge Base | Computer for Support Teams | DevRev"
},
{
"id": "ART-1982_KNOWLEDGE_NODE-27",
"text": "visibility settings. Here are a few scenarios:\\n\\n* If a collection is not **Public**, none of the articles within it will be visible to customers, even if the articles are set to be **Visible to Customers**.\\n* If a collection is **Public**, only the articles set to be **Visible to Customers** will be publicly accessible. If an article within the public collection is configured with visibility for **Verified Customers**, non-signed-in customers won\\xe2\\x80\\x99t be able to view it.\\n* If a",
"title": "Collections | Knowledge Base | Computer for Support Teams | DevRev"
},
{
"id": "ART-1985_KNOWLEDGE_NODE-38",
"text": "and **Public Portal**.\\n\\n### Share an article\\n\\nOnce you've created an article, you have two options to share it:\\n\\n* Use **Copy external link** to share with your customers, allowing them to access the article directly.\\n* Use **Copy internal link** to share with your internal organizational team members.\\n\\nThe ability to view the article depends on the settings for **Visible to** and **Status** that have been configured.\\n\\n* If you are sharing an external link with non-signed-in",
"title": "Articles | Knowledge Base | Computer for Support Teams | DevRev"
},
{
"id": "ART-1985_KNOWLEDGE_NODE-39",
"text": "customers, the article should be visible to customers. If the **Visible to** option is set to **Verified Customers**, only signed-in customers are able to view the article.\\n* When sharing an external link with customers, the article status should be *Published*. If it is in *Draft* mode, they won\\xe2\\x80\\x99t be able to view it.\\n\\nArticle Formatting\\n------------------\\n\\nWhen you\\xe2\\x80\\x99re creating a new article or editing an existing article, formatting options are displayed. While",
"title": "Articles | Knowledge Base | Computer for Support Teams | DevRev"
},
{
"id": "ART-1982_KNOWLEDGE_NODE-28",
"text": "collection is **Public** but all the articles within it are intended for internal use only, the collection itself won\\xe2\\x80\\x99t be visible to the public in the help center.\\n\\nCollection management\\n---------------------\\n\\n### Create a collection\\n\\n1. Go to **Settings > Support > Article Collections**.\\n2. Click **+Collection** and fill in the following details:\\n\\n * Title\\n * Description\\n * Parent\\n3. Enable the **Publish Collection** option if you want your customers to see the",
"title": "Collections | Knowledge Base | Computer for Support Teams | DevRev"
},
{
"id": "ART-1978_KNOWLEDGE_NODE-39",
"text": "toggle and craft your own title and description.\\n7. Enable **Public portal** to allow unauthenticated users to view/search public articles.\\n8. Click **Save & publish** to make the changes visible on your portal.\\n\\nIf you want to customize the font color and favicon, contact DevRev support. For favicon customization, an icon in .ico format is needed.\\n\\nCustomize portal URL\\n--------------------\\n\\nBy default, your customer portal is hosted at support.devrev.ai/<yourcompany>. The",
"title": "Customer portal | Computer for Support Teams | DevRev"
},
{
"id": "ART-1985_KNOWLEDGE_NODE-34",
"text": "delete an article.\\n\\n### Bulk change options\\n\\nIn the main knowledge base view, you can select multiple articles to delete articles in bulk or to modify article settings, such as transitioning multiple articles from *Draft* to *Published* stage.\\n\\nStatus settings\\n---------------\\n\\n* *Draft*: The article isn't ready to be released to the public. You can make edits at this stage.\\n* *Published*: The article has already been released to the public.\\n* *Archived*: Articles that are outdated",
"title": "Articles | Knowledge Base | Computer for Support Teams | DevRev"
},
{
"id": "ART-1985_KNOWLEDGE_NODE-37",
"text": "Storage limits for articles\\n\\n* There is no limit to the number of articles that can be created in the DevRev knowledge base.\\n* Each article is stored as an artifact, with a maximum size of 250 MB per artifact.\\n\\n### Enable customer access for your knowledge base\\n\\nTo make your help center, including your knowledge base, accessible to the public, go to **[Settings > Plug & Portal > Portal Settings](https://app.devrev.ai/?setting=portal-settings%2Fconfiguration)** and enable **Help Center**",
"title": "Articles | Knowledge Base | Computer for Support Teams | DevRev"
},
{
"id": "ART-1304_KNOWLEDGE_NODE-33",
"text": "Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe authors of the article.\\ncustom_fields map from",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1301_KNOWLEDGE_NODE-34",
"text": "properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe authors of the article.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ncustom_schema_spec object Optional\\nRequested custom schemas described abstractly. Every",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1560_KNOWLEDGE_NODE-28",
"text": "object Required\\nShow 3 properties\\ntitle string Required\\n\\nName of the article.\\n\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\n\\nType of the article.\\n\\nauthored_by list of strings Optional\\n\\nThe authors of the article.\\n\\ncustom_fields map from strings to any Optional\\n\\nApplication-defined custom fields.\\n\\ncustom_schema_spec object Optional\\n\\nRequested",
"title": "Assign (Beta) — DevRev | Docs"
},
{
"id": "ART-17231_KNOWLEDGE_NODE-40",
"text": "article is shared and the corresponding roles. |\\n| `status` | enum | | Status of the article. |\\n| `tags` | reference (collection)\\xe2\\x86\\x92[#record:tag] | | Tags associated with the article. |\\n| `title` | text | \\xe2\\x9c\\x94\\xef\\xb8\\x8e | Title of the article. |\\n| `type` | enum | | Type of the article. |\\n| `visible_to` | enum | | |\\n\\n#### Enum values\\n\\n**access\\\\_level**\\n\\n| Value | Name | Description |\\n| --- | --- | --- |\\n| `EXTERNAL` | - | - |\\n| `INTERNAL` | - | - |\\n|",
"title": "Supported DevRev object types | DevRev | Docs"
},
{
"id": "ART-1566_KNOWLEDGE_NODE-28",
"text": "object Required\\nShow 3 properties\\ntitle string Required\\n\\nName of the article.\\n\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\n\\nType of the article.\\n\\nauthored_by list of strings Optional\\n\\nThe authors of the article.\\n\\ncustom_fields map from strings to any Optional\\n\\nApplication-defined custom fields.\\n\\ncustom_schema_spec object Optional\\n\\nRequested",
"title": "Transition (Beta) — DevRev | Docs"
},
{
"id": "ART-1545_KNOWLEDGE_NODE-28",
"text": "object Required\\nShow 3 properties\\ntitle string Required\\n\\nName of the article.\\n\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\n\\nType of the article.\\n\\nauthored_by list of strings Optional\\n\\nThe authors of the article.\\n\\ncustom_fields map from strings to any Optional\\n\\nApplication-defined custom fields.\\n\\ncustom_schema_spec object Optional\\n\\nRequested",
"title": "Create (Beta) — DevRev | Docs"
},
{
"id": "ART-1302_KNOWLEDGE_NODE-34",
"text": "properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe authors of the article.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ncustom_schema_spec object Optional\\nRequested custom schemas described abstractly. Every",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1547_KNOWLEDGE_NODE-28",
"text": "object Required\\nShow 3 properties\\ntitle string Required\\n\\nName of the article.\\n\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\n\\nType of the article.\\n\\nauthored_by list of strings Optional\\n\\nThe authors of the article.\\n\\ncustom_fields map from strings to any Optional\\n\\nApplication-defined custom fields.\\n\\ncustom_schema_spec object Optional\\n\\nRequested",
"title": "Get Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1549_KNOWLEDGE_NODE-28",
"text": "object Required\\nShow 3 properties\\ntitle string Required\\n\\nName of the article.\\n\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\n\\nType of the article.\\n\\nauthored_by list of strings Optional\\n\\nThe authors of the article.\\n\\ncustom_fields map from strings to any Optional\\n\\nApplication-defined custom fields.\\n\\ncustom_schema_spec object Optional\\n\\nRequested",
"title": "List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1558_KNOWLEDGE_NODE-28",
"text": "object Required\\nShow 3 properties\\ntitle string Required\\n\\nName of the article.\\n\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\n\\nType of the article.\\n\\nauthored_by list of strings Optional\\n\\nThe authors of the article.\\n\\ncustom_fields map from strings to any Optional\\n\\nApplication-defined custom fields.\\n\\ncustom_schema_spec object Optional\\n\\nRequested",
"title": "Metric Definitions List (Beta) — DevRev | Docs"
},
{
"id": "ART-1564_KNOWLEDGE_NODE-28",
"text": "object Required\\nShow 3 properties\\ntitle string Required\\n\\nName of the article.\\n\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\n\\nType of the article.\\n\\nauthored_by list of strings Optional\\n\\nThe authors of the article.\\n\\ncustom_fields map from strings to any Optional\\n\\nApplication-defined custom fields.\\n\\ncustom_schema_spec object Optional\\n\\nRequested",
"title": "List (Beta) — DevRev | Docs"
},
{
"id": "ART-1306_KNOWLEDGE_NODE-31",
"text": "creates an article.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1562_KNOWLEDGE_NODE-28",
"text": "object Required\\nShow 3 properties\\ntitle string Required\\n\\nName of the article.\\n\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\n\\nType of the article.\\n\\nauthored_by list of strings Optional\\n\\nThe authors of the article.\\n\\ncustom_fields map from strings to any Optional\\n\\nApplication-defined custom fields.\\n\\ncustom_schema_spec object Optional\\n\\nRequested",
"title": "Get (Beta) — DevRev | Docs"
},
{
"id": "ART-1543_KNOWLEDGE_NODE-28",
"text": "object Required\\nShow 3 properties\\ntitle string Required\\n\\nName of the article.\\n\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\n\\nType of the article.\\n\\nauthored_by list of strings Optional\\n\\nThe authors of the article.\\n\\ncustom_fields map from strings to any Optional\\n\\nApplication-defined custom fields.\\n\\ncustom_schema_spec object Optional\\n\\nRequested",
"title": "Metric Definitions List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1551_KNOWLEDGE_NODE-28",
"text": "object Required\\nShow 3 properties\\ntitle string Required\\n\\nName of the article.\\n\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\n\\nType of the article.\\n\\nauthored_by list of strings Optional\\n\\nThe authors of the article.\\n\\ncustom_fields map from strings to any Optional\\n\\nApplication-defined custom fields.\\n\\ncustom_schema_spec object Optional\\n\\nRequested",
"title": "Update (Beta) — DevRev | Docs"
},
{
"id": "ART-1306_KNOWLEDGE_NODE-45",
"text": "object.\\nid string Required\\nThe article\\'s ID.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\napplies_to_parts object Optional\\nShow property\\nartifacts object Optional\\nShow property\\nauthored_by object Optional\\nShow property\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ncustom_schema_spec object Optional\\nRequested custom schemas described abstractly. Every provided schema\\'s custom field must be specified,",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1828_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1595_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1819_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Sla Trackers Get — DevRev | Docs"
},
{
"id": "ART-1577_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1609_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1308_KNOWLEDGE_NODE-31",
"text": "Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe authors of the article.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ncustom_schema_spec object Optional\\nRequested custom schemas described",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1790_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1651_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1824_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1806_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Self Post — DevRev | Docs"
},
{
"id": "ART-1305_KNOWLEDGE_NODE-33",
"text": "creates an article.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1592_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1801_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1307_KNOWLEDGE_NODE-31",
"text": "regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\"",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1597_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1655_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1833_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1636_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1591_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1829_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1509_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Prepare — DevRev | Docs"
},
{
"id": "ART-1300_KNOWLEDGE_NODE-30",
"text": "resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1593_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1652_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1780_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1784_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Locate Post — DevRev | Docs"
},
{
"id": "ART-1639_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Export Post — DevRev | Docs"
},
{
"id": "ART-1804_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Self — DevRev | Docs"
},
{
"id": "ART-1781_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1836_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1605_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1787_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1588_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1827_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1643_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1826_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1802_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1654_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1633_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1782_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1831_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1607_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-15323_KNOWLEDGE_NODE-5",
"text": "\"display_name\": \"string\", |\\n| 75 | \"display_picture\": { |\\n| 76 | \"display_id\": {}, |\\n| 77 | \"id\": {}, |\\n| 78 | \"file\": {} |\\n| 79 | }, |\\n| 80 | \"email\": \"string\", |\\n| 81 | \"full_name\": \"string\", |\\n| 82 | \"state\": \"active\" |\\n| 83 | }, |\\n| 84 | \"modified_date\": \"2023-01-01T12:00:00.000Z\", |\\n| 85 | \"object\": \"string\", |\\n| 86 | \"object_display_id\": \"string\", |\\n| 87 | \"object_type\": \"article\", |\\n| 88 | \"visibility\": \"external\", |\\n| 89 | \"artifacts\": [ |\\n| 90 | { |\\n| 91 |",
"title": "Get Conversation | DevRev | Docs"
},
{
"id": "ART-1779_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1303_KNOWLEDGE_NODE-31",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Export Post — DevRev | Docs"
},
{
"id": "ART-1641_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1786_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-4064_KNOWLEDGE_NODE-2",
"text": "This call creates an article.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\nowned_bylist of stringsRequired\\n\\nThe users that own the article.\\n\\nresourceobjectRequired\\n\\nShow 4 properties\\n\\ntitlestringRequired`format: \"text\"`\\n\\nName of the article.\\n\\naccess_levelenumOptional\\n\\nAllowed values: externalinternalprivatepublicrestricted\\n\\naliaseslist of stringsOptional\\n\\nThe aliases of the article.\\n\\napplies_to_partslist of stringsOptional\\n\\nThe parts that the article applies",
"title": "Create Article — DevRev | Docs"
},
{
"id": "ART-1649_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1575_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1805_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1825_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1822_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1803_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1792_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1832_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1838_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "List Post — DevRev | Docs"
}
] |
c1240672-a533-43f7-bb75-f7d77766e7e2
|
Organisation-wide Email Signature formatting and adding links
|
[
{
"id": "ART-3207_KNOWLEDGE_NODE-35",
"text": "**Configuration** section.\\n\\nEmail HTML\\n\\n* For inserting an image: <img src=\"image link\" />\\n* For inserting a link: <a href=\"link\\\\_address\">link title</a>\\n\\n**Signature example**:\\n\\n```\\n```\\n1 <table\\n\\n\\n\\n2 style=\"font-family: Arial, Helvetica, sans-serif; font-size: 12px; border: solid; border-width: 1px; border-color: gray\"\\n\\n\\n\\n3 >\\n\\n\\n\\n4 <tr>\\n\\n\\n\\n5 <td style=\"padding-right: 20px\">\\n\\n\\n\\n6 <img\\n\\n\\n\\n7",
"title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev"
}
] |
91c63897-0036-4262-90dc-a7933506fa81
|
crawler API job stuck running no URLs scraped
|
[
{
"id": "ART-13044_KNOWLEDGE_NODE-3",
"text": "Error\\n\\nPOST\\n\\n/web-crawler-jobs.control\\n\\n[code]\\n\\n $| curl -X POST https://api.devrev.ai/web-crawler-jobs.control \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer <token>\" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"action\": \"abort\", \\n >| \"id\": \"foo\" \\n >| }\\'\\n[/code] \\n \\nTry it\\n\\n200webCrawlerJobWebCrawlerJobsControlExample\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"web_crawler_job\": { \\n 3| \"id\":",
"title": "Control Web Crawler Jobs — DevRev | Docs"
},
{
"id": "ART-15485_KNOWLEDGE_NODE-1",
"text": "https://api.devrev.ai/web-crawler-jobs.control \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{ |\\n| > | \"action\": \"abort\", |\\n| > | \"id\": \"string\" |\\n| > | }\\' |\\n```\\n\\n[Try it](/api-reference/web-crawler-job/web-crawler-jobs-control?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"web_crawler_job\": { |\\n| 3 | \"id\": \"string\", |\\n| 4 | \"accept_regexs\": [ |\\n| 5 | \"string\" |\\n| 6 | ], |\\n| 7 |",
"title": "Control Web Crawler Jobs | DevRev | Docs"
},
{
"id": "ART-4236_KNOWLEDGE_NODE-1",
"text": "abortpauseresume\\n\\nidstringRequired`format: \"id\"`\\n\\nThe ID of the job.\\n\\n### Response\\n\\nThe response to resume a web crawler job.\\n\\nweb_crawler_jobobject\\n\\nShow 21 properties\\n\\nPOST\\n\\n/web-crawler-jobs.control\\n\\n[code]\\n\\n $| curl -X POST https://api.devrev.ai/web-crawler-jobs.control \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer <token>\" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"action\": \"abort\", \\n >| \"id\": \"id\"",
"title": "Control Web Crawler Jobs (Beta) — DevRev | Docs"
}
] |
d5bee897-fe51-445d-aa6d-83256e29e3d3
|
reasons why a sync might fail in DevRev Airdrop
|
[
{
"id": "ART-13117_KNOWLEDGE_NODE-0",
"text": "b\"Will Airdrop recreate/duplicate merged accounts or contacts?\\n\\nNo, Airdrop can recognize that you merged an account or contact, so it will not create them again and will keep updating any linked tickets or other linked objects.Updates from an account in the external system are not synced to DevRev, why not? I merged the account with another in DevRev.\\n\\nOnce you merge an account or contact, Airdrop stops syncing updates to it (just to the account or contact, not to the linked items, linked",
"title": "Airdrop duplicates merging"
},
{
"id": "ART-15160_KNOWLEDGE_NODE-0",
"text": "b\"Airdrop does not sync comments created by automations or workflows back to external systems, because such comments usually don't contain any information relevant to the external system.\\n\\nExamples of such comments are comments that ask users whether the issue was correctly classified. Since these are not relevant outside DevRev (and would even pollute customers' data in the external system), they are not synced in syncs to the external system.\"",
"title": "Airdrop automation-created comment sync"
},
{
"id": "ART-17216_KNOWLEDGE_NODE-6",
"text": "external_sync_units: externalSyncUnits, |\\n| 3 | }); |\\n```\\n\\nor an error:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | await adapter.emit(ExtractorEventType.ExtractionExternalSyncUnitsError, { |\\n| 2 | error: { |\\n| 3 | message: \"Failed to extract external sync units. Lambda timeout.\", |\\n| 4 | }, |\\n| 5 | }); |\\n```\\n\\n**The snap-in must always emit a single message.**\\n\\nTo test your changes, start a new airdrop in the DevRev App. If external sync units extraction is successful, you should be",
"title": "External sync units extraction | DevRev | Docs"
},
{
"id": "ART-15731_KNOWLEDGE_NODE-0",
"text": "b'If the comment was created from an Agent or any other kind of system user, those comments will not get extracted and synced back. Only comments made by either a dev or rev user will get synced in reverse via Airdrop.'",
"title": "Comments aren't syncing from DevRev to external system"
},
{
"id": "ART-17711_KNOWLEDGE_NODE-0",
"text": "b'We ran into a case where an AirSync was started by one person (Person A) and later failed. Another user (Person B) tried to click Retry, but it didn\\xe2\\x80\\x99t work. The logs showed 401 and 403 errors in communication between the snap-in and the snap-in manager.\\n\\nIt turned out that AirSync assigns the sync owner to whoever started it. Since Person A had been removed from the org or lost permissions, the retry failed \\xe2\\x80\\x94 the system still expected the original owner to have valid",
"title": "Sync fails when original sync owners loses permissions"
},
{
"id": "ART-17711_KNOWLEDGE_NODE-1",
"text": "access.\\n\\nOnce Person A was re-added with the right permissions, the retry worked again.\\n\\nIf this happens, check who started the sync and make sure that person still exists in the org and has the right permissions. Until ownership handling is improved, retries for syncs started by users without access will fail with similar 401 or 403 errors.'",
"title": "Sync fails when original sync owners loses permissions"
},
{
"id": "ART-4109_KNOWLEDGE_NODE-5",
"text": "Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/beta/api-reference/accounts/update)[#### Get Airdrop Sync Unit\\n\\nNext](/beta/api-reference/airdrop/sync-units-get)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'",
"title": "Execute-Async Ai Agents Events | DevRev | Docs"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-57",
"text": "**Slack snap-in event discussions panel** to automatically invite the DevRev app to all public channels.\\n + Private channels still require manual addition.\\n\\n### When sync is not possible\\n\\nIf sync isn\\xe2\\x80\\x99t possible, the form will display a clear warning. Possible reasons include:\\n\\n* The thread is already in sync with another DevRev object.\\n* Sync is not supported for the object in the given Slack channel.\\n* The DevRev app is not a member of the channel.\\n* The channel is",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-15679_KNOWLEDGE_NODE-0",
"text": "b'We are querying FeedComments, which are tied to FeedItems - as you can see in this [diagram from Salesforce](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_erd_chatter.htm). In the query, we say \"we want all FeedComments whose parent FeedItemId is in (all ids from FeedItem where the type is either CaseCommentPost or EmailMessageEvent)\". However, when querying FeedItems Salesforce can complain that the query requires a filter by Id to work,",
"title": "Why is ViewAllData permission needed for Salesforce imports"
},
{
"id": "ART-15679_KNOWLEDGE_NODE-1",
"text": "as is the error we get in the response: Malformed query,\\xc2\\xa0 FeedItem requires a filter by Id. To protect their own backend, Salesforce will not allow you to query the entire table unless you have permission to see absolutely everything that\\'s in it or all the parent objects - as it makes no sense to show someone the comment to a case if they don\\'t have access to cases.\\n\\nTo be able to query on the FeedItem table directly, we require one of the two: either you have ViewAllData",
"title": "Why is ViewAllData permission needed for Salesforce imports"
},
{
"id": "ART-15679_KNOWLEDGE_NODE-2",
"text": "permissions or mark that Apex class as \"Without Sharing\". As the [Salesforce documentation for FeedItems](https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_feeditem.htm) states:\\n\\nIf you\\xe2\\x80\\x99re using API version 23.0 or later and have View All Data permission, you can directly query for a FeedItem. The following example returns the 20 most recent feed items.SELECT ID, CreatedDate, CreatedById, CreatedBy.FirstName,",
"title": "Why is ViewAllData permission needed for Salesforce imports"
},
{
"id": "ART-15679_KNOWLEDGE_NODE-3",
"text": "CreatedBy.LastName, ParentId, Parent.Name, Body,\\n (SELECT ID, FieldName, OldValue, NewValue FROM FeedTrackedChanges ORDER BY ID DESC) \\nFROM FeedItem \\nWHERE CreatedDate > LAST_MONTH \\nORDER BY CreatedDate DESC\\n\\nWithout the ViewAllData permission we cannot efficiently query the FeedItems.'",
"title": "Why is ViewAllData permission needed for Salesforce imports"
},
{
"id": "ART-15661_KNOWLEDGE_NODE-0",
"text": "b'The key permission requirement for Salesforce Airdrop is the \"View All Data\" permission. This is important to note because:\\n\\nThe connection owner (the user performing the Airdrop) must have the \"View All Data\" permission in Salesforce.\\n\\nImportant distinction: There is a similar permission called \"View Data\", which is not sufficient - you specifically need \"View All Data\".\\n\\nWithout this permission, you may encounter sync failures, particularly when trying to extract comments or feed items",
"title": "Salesforce permissions requirements"
},
{
"id": "ART-2053_KNOWLEDGE_NODE-67",
"text": "parent-child link is created in DevRev. These types of links are skipped in the Jira loader as there is no parent link in Jira, and they are shown as skipped in reports. This link is only created once per issue.\\n* Deleting and reimporting sometimes produce dead links in DevRev, which could point to non-existing issues which were deleted in AirSync settings. These links do not show up in UI, but they could be extracted, and they show up as failed in the reports.\\n* Changing an epic into an",
"title": "Jira Software AirSync | AirSync | Snap-ins | DevRev"
},
{
"id": "ART-2053_KNOWLEDGE_NODE-64",
"text": "state in Jira is not changed.\\n* Comments originating from DevRev and synced to Jira are not synced back to DevRev if they are edited in Jira.\\n\\n### Sub-tasks\\n\\n* When creating a Sub-task in DevRev, the creator has to specify a parent issue in the parent field. This issue also has to be of some Jira subtype so it is synced. If the parent is empty, the Sub-task is not created in Jira, and it shows up as failed in the report under Issues column.\\n\\n### Epics -> Enhancements\\n\\nIf you choose to",
"title": "Jira Software AirSync | AirSync | Snap-ins | DevRev"
},
{
"id": "ART-15816_KNOWLEDGE_NODE-2",
"text": "incremental sync timeframe\\n\\nExample:\\n\\nTime-scoped sync cutoff: January 1, 2024\\n\\nIssue A: Last updated December 2023 \\xe2\\x86\\x92 Not imported initially\\n\\nLater: Issue A gets a new comment in March 2024\\n\\nIncremental sync imports Issue A + only the new March comment\\n\\nResult: All comments before January 2024 are permanently lost2. Broken Issue Links\\n\\nThe Problem:\\n\\nLinks between issues can fail if one issue was imported but the linked issue wasn't.\\n\\nExample:\\n\\nIssue X (updated",
"title": "Jira Time-Scoped syncs limitations"
},
{
"id": "ART-2053_KNOWLEDGE_NODE-63",
"text": "type is PAT based. When creating a PAT, the user can specify the expiration date. For long running migrations, it is recommended to set the PAT to never expire, as on expiration, the PAT must be recreated manually in Jira.\\n\\n### Updates\\n\\n* If a Jira field is not writable in the creation or edit screen, AirSync may fail to create or update that issue in Jira with the corresponding change in DevRev.\\n* If there is no direct transition from the current issue state to the next state in Jira, the",
"title": "Jira Software AirSync | AirSync | Snap-ins | DevRev"
},
{
"id": "ART-15161_KNOWLEDGE_NODE-2",
"text": "settings\\n\\nWait for the sync to complete\\n\\nVerify that all articles are now showing in DevRev collections Notes\\n\\nArticle creation dates should be preserved from the original Zendesk articles\\n\\nAll accessible Zendesk articles should be imported during a successful manual sync\\n\\nEnsure the account used for integration has sufficient permissions to access all articles in Zendesk\"",
"title": "Zendesk Articles are Extracted Only During Manual Sync"
}
] |
7bb5a2a2-2cad-4c9c-907b-3b4c4cebcbc6
|
send email to customers directly without customer initiated conversation
|
[
{
"id": "ART-2027_KNOWLEDGE_NODE-39",
"text": "Notifications**.\\n\\n* Each notification type\\xe2\\x80\\x94such as being assigned, mentioned, or when a customer esponds\\xe2\\x80\\x94can be toggled for both in-app and email delivery.\\n\\n### The email composer in Tickets\\n\\nInside every ticket, under the **Customer Messages** tab, agents can access a fully featured email composer. This allows direct email communication with customers from within DevRev.\\n\\nHere\\xe2\\x80\\x99s what the email component supports:\\n\\n| Feature | Icon / Access Point |",
"title": "Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-4020_KNOWLEDGE_NODE-24",
"text": "[Documentation](/docs)\\n3. [Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Send customized emails](/docs/automations/send-emails)\\n\\nSend customized emails\\n======================\\n\\nThe [**send customized emails**](https://marketplace.devrev.ai/marketplace/send-emails) snap-in automates email sending. Once activated, this operation becomes available in the Workflow builder, enabling the delivery of personalized messages.\\n\\nConfiguration\\n-------------\\n\\n1. Create a **SendGrid**",
"title": "Send customized emails | Automate | Snap-ins | DevRev"
},
{
"id": "ART-4020_KNOWLEDGE_NODE-25",
"text": "account.\\n2. Generate an **API key**.\\n3. Create a SendGrid connection:\\n a. Go to **Settings** > **Snap-ins** > **+ Connection**\\n b. Select **SendGrid**.\\n c. Add the **API key** and click **Save**.\\n\\nInstallation\\n------------\\n\\n1. Install the [**send customized emails**](https://marketplace.devrev.ai/marketplace/send-emails) from the DevRev marketplace.\\n2. Open the Workflow Builder and locate the **send customized emails** action node.\\n3. Configure the node by selecting the",
"title": "Send customized emails | Automate | Snap-ins | DevRev"
},
{
"id": "ART-1627_KNOWLEDGE_NODE-1",
"text": "---|--- \\n >| -H \"Authorization: Bearer <token>\" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"email\": { \\n >| \"body\": \"body\", \\n >| \"recipients\": [ \\n >| \"recipients\", \\n >| \"recipients\" \\n >| ], \\n >| \"sender\": \"sender\", \\n >| \"subject\": \"subject\" \\n >| } \\n >| }\\'\\n[/code] \\n \\nTry it\\n\\n200Successful\\n\\n[code]\\n\\n 1| {} \\n ---|---\\n[/code] \\n \\n[Submit",
"title": "Send Surveys (Beta) — DevRev | Docs"
},
{
"id": "ART-4020_KNOWLEDGE_NODE-26",
"text": "SendGrid connection and providing inputs such as:\\n\\n * **Sender email**\\n * **Recipient emails**\\n * **Email body or email template name (use only one)**\\n * **Fields to replace in the email template** for dynamic content substitution\\n\\n ![]()\\n\\n Use either the email body or the email template name, but not both. The email template name must match a template created in SendGrid. The **Fields to replace in the email template** allows dynamic value substitution. For example, if the",
"title": "Send customized emails | Automate | Snap-ins | DevRev"
},
{
"id": "ART-1974_KNOWLEDGE_NODE-24",
"text": "Teams](/docs/product/support)\\n[Conversations](/docs/product/conversation)\\n\\nConversations\\n=============\\n\\nA conversation is an object type that's used to track any synchronous or near-synchronous discussions. A conversation maybe started by a customer, a builder, or a system (auto-created).\\n\\nA new conversation is routed to the customer org's default owner unless it matches keywords in the support routing snap-in configuration.\\n\\nConversations from new or unidentified customer orgs have",
"title": "Conversations | Computer for Support Teams | DevRev"
},
{
"id": "ART-3207_KNOWLEDGE_NODE-44",
"text": "sharing settings:\\n\\n* **Signature**: Added to all personal emails sent via DevRev\\n* **Share files as links**: Ensures deliverability of attachments via secure links\\n\\n3. Configure email forwarding for your email provider\\n-----------------------------------------------------\\n\\nFor conversation or tickets to be created in DevRev, the emails must be forwarded from your email provider. The forwarding instructions are available **under the Installation section** of the Email Integration",
"title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev"
}
] |
18d0e338-823b-4188-9cfe-d9cc8f2378b5
|
upload document as artifact and make it accessible on internet using Artifacts API
|
[
{
"id": "ART-1183_KNOWLEDGE_NODE-1",
"text": "| -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{ |\\n| > | \"file_name\": \"string\" |\\n| > | }\\' |\\n```\\n\\n[Try it](/api-reference/artifacts/prepare?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"form_data\": [ |\\n| 3 | { |\\n| 4 | \"key\": \"string\", |\\n| 5 | \"value\": \"string\" |\\n| 6 | } |\\n| 7 | ], |\\n| 8 | \"id\": \"ARTIFACT-12345\", |\\n| 9 | \"url\": \"string\" |\\n| 10 | } |\\n```\\n\\nCreates an artifact and generates an upload URL for its data.\\n\\n###",
"title": "Prepare Artifacts | DevRev | Docs"
},
{
"id": "ART-1784_KNOWLEDGE_NODE-49",
"text": "Content-Type: application/json \" \\\\ > -d \\' { > \"id\": \"ARTIFACT-12345\" > } \\'\\n200 Successful 1 { 2 \" expires_at \" : \" 2023-01-01T12:00:00Z \" , 3 \" url \" : \" url \" 4 }\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being",
"title": "Locate Post — DevRev | Docs"
},
{
"id": "ART-1826_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1791_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Self Delete — DevRev | Docs"
},
{
"id": "ART-1607_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1650_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1828_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1301_KNOWLEDGE_NODE-56",
"text": "an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an object.\\nform_data list of objects\\nThe POST policy form data.\\nShow 2 properties\\nid string\\nThe generated artifact\\'s ID.\\nurl string\\nThe URL that the file\\'s data should be uploaded to.\\nAPI Reference artifacts",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1780_KNOWLEDGE_NODE-51",
"text": "an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an object.\\nform_data list of objects\\nThe POST policy form data.\\nShow 2 properties\\nid string\\nThe generated artifact\\'s ID.\\nurl string\\nThe URL that the file\\'s data should be uploaded to.\\nAPI Reference artifacts",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1302_KNOWLEDGE_NODE-56",
"text": "an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an object.\\nform_data list of objects\\nThe POST policy form data.\\nShow 2 properties\\nid string\\nThe generated artifact\\'s ID.\\nurl string\\nThe URL that the file\\'s data should be uploaded to.\\nAPI Reference artifacts",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1308_KNOWLEDGE_NODE-53",
"text": "an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an object.\\nform_data list of objects\\nThe POST policy form data.\\nShow 2 properties\\nid string\\nThe generated artifact\\'s ID.\\nurl string\\nThe URL that the file\\'s data should be uploaded to.\\nAPI Reference artifacts",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1792_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1821_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1803_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1591_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1593_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1654_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1804_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Self — DevRev | Docs"
},
{
"id": "ART-1834_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1785_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1609_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1788_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1824_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1636_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1827_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1805_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1806_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Self Post — DevRev | Docs"
},
{
"id": "ART-1837_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1786_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1592_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1838_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1653_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1183_KNOWLEDGE_NODE-0",
"text": "b'Prepare Artifacts | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[artifacts](/api-reference/artifacts/attachments)\\n\\nPrepare Artifacts\\n=================\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/artifacts.prepare\\n\\nPOST\\n\\n/artifacts.prepare\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/artifacts.prepare \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| >",
"title": "Prepare Artifacts | DevRev | Docs"
},
{
"id": "ART-1818_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Sla Trackers Get Post — DevRev | Docs"
},
{
"id": "ART-1575_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1651_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1823_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1605_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1633_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1790_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1825_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "List — DevRev | Docs"
},
{
"id": "ART-15266_KNOWLEDGE_NODE-1",
"text": "|\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{ |\\n| > | \"id\": \"ARTIFACT-12345\" |\\n| > | }\\' |\\n```\\n\\n[Try it](/api-reference/artifacts/versions-prepare?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"form_data\": [ |\\n| 3 | { |\\n| 4 | \"key\": \"string\", |\\n| 5 | \"value\": \"string\" |\\n| 6 | } |\\n| 7 | ], |\\n| 8 | \"url\": \"string\" |\\n| 9 | } |\\n```\\n\\nPrepares a new version for an artifact, returning the",
"title": "Prepare Artifacts Versions | DevRev | Docs"
},
{
"id": "ART-1833_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1829_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1590_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1652_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1509_KNOWLEDGE_NODE-49",
"text": "artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an object.\\nform_data list of objects\\nThe POST policy form data.\\nShow 2 properties\\nid string\\nThe generated artifact\\'s ID.\\nurl string\\nThe URL that the file\\'s data should be uploaded",
"title": "Prepare — DevRev | Docs"
},
{
"id": "ART-1577_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1789_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1822_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1597_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1649_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1639_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Export Post — DevRev | Docs"
},
{
"id": "ART-1641_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1781_KNOWLEDGE_NODE-50",
"text": "artifact.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the artifact to get the URL for.\\nversion string Optional\\nThe version of the artifact that needs to be fetched.\\nResponse.\\n\\nThis endpoint returns an object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1835_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1182_KNOWLEDGE_NODE-1",
"text": "<token>\" \\\\ |\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{ |\\n| > | \"id\": \"ARTIFACT-12345\" |\\n| > | }\\' |\\n```\\n\\n[Try it](/api-reference/artifacts/locate-post?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"url\": \"string\", |\\n| 3 | \"expires_at\": \"2023-01-01T12:00:00.000Z\" |\\n| 4 | } |\\n```\\n\\nGets the download URL for the artifact.\\n\\n### Headers\\n\\nAuthorizationstringRequired\\n\\nBearer authentication of the form `Bearer <token>`, where token",
"title": "Locate Artifacts (POST) | DevRev | Docs"
},
{
"id": "ART-1830_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1819_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Sla Trackers Get — DevRev | Docs"
},
{
"id": "ART-1579_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1787_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1637_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1831_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1595_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1802_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1303_KNOWLEDGE_NODE-53",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Export Post — DevRev | Docs"
},
{
"id": "ART-1832_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1801_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1588_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1784_KNOWLEDGE_NODE-50",
"text": "uploaded.\\nResponse.\\n\\nThis endpoint returns an object.\\nform_data list of objects\\nThe POST policy form data.\\nShow 2 properties\\nid string\\nThe generated artifact\\'s ID.\\nurl string\\nThe URL that the file\\'s data should be uploaded to.\\nPOST / artifacts.prepare\\ncURL\\n$ curl -X POST https://api.devrev.ai/artifacts.prepare \\\\ > -H \" Authorization: Bearer <token> \" \\\\ > -H \" Content-Type: application/json \" \\\\ > -d \\' { > \"file_name\": \"file_name\" > } \\'\\n200 Successful 1 { 2 \" form_data \" : [",
"title": "Locate Post — DevRev | Docs"
},
{
"id": "ART-1655_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1501_KNOWLEDGE_NODE-1",
"text": "version for.\\n\\n### Response\\n\\nThe response to preparing a new artifact version.\\n\\nform_datalist of objects\\n\\nThe POST policy form data.\\n\\nShow 2 properties\\n\\nurlstring`format: \"text\"`\\n\\nThe URL that the file\\xe2\\x80\\x99s data should be uploaded to.\\n\\nPOST\\n\\n/artifacts.versions.prepare\\n\\ncURL\\n\\n[code]\\n\\n $| curl -X POST https://api.devrev.ai/artifacts.versions.prepare \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer <token>\" \\\\ \\n >| -H \"Content-Type:",
"title": "Prepare Artifacts Versions (Beta) — DevRev | Docs"
},
{
"id": "ART-1181_KNOWLEDGE_NODE-1",
"text": "id=ARTIFACT-12345 |\\n```\\n\\n[Try it](/api-reference/artifacts/locate?explorer=true)\\n\\n200Retrieved\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"url\": \"string\", |\\n| 3 | \"expires_at\": \"2023-01-01T12:00:00.000Z\" |\\n| 4 | } |\\n```\\n\\nGets the download URL for the artifact.\\n\\n### Headers\\n\\nAuthorizationstringRequired\\n\\nBearer authentication of the form `Bearer <token>`, where token is your auth token.\\n\\n### Query parameters\\n\\nidstringRequired`format: \"id\"`\\n\\nThe ID of the artifact to",
"title": "Locate Artifacts | DevRev | Docs"
},
{
"id": "ART-1379_KNOWLEDGE_NODE-1",
"text": "__\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[API Reference](/public/api-reference/getting-started)[Artifacts](/public/api-reference/artifacts/attachments)\\n\\n# Prepare Artifacts\\n\\nPOST\\n\\nhttps://api.devrev.ai/artifacts.prepare\\n\\nTry it\\n\\nCreates an artifact and generates an upload URL for its data.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\nfile_namestringRequired`format: \"text\"`\\n\\nThe name",
"title": "Prepare Artifacts — DevRev | Docs"
},
{
"id": "ART-1306_KNOWLEDGE_NODE-53",
"text": "fetched.\\nResponse.\\n\\nThis endpoint returns an object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1305_KNOWLEDGE_NODE-55",
"text": "fetched.\\nResponse.\\n\\nThis endpoint returns an object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1181_KNOWLEDGE_NODE-0",
"text": "b'Locate Artifacts | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[artifacts](/api-reference/artifacts/attachments)\\n\\nLocate Artifacts\\n================\\n\\nCopy page\\n\\nGET\\n\\nhttps://api.devrev.ai/artifacts.locate\\n\\nGET\\n\\n/artifacts.locate\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -G https://api.devrev.ai/artifacts.locate \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -d",
"title": "Locate Artifacts | DevRev | Docs"
},
{
"id": "ART-1836_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1785_KNOWLEDGE_NODE-50",
"text": "new version for.\\nResponse.\\n\\nThis endpoint returns an object.\\nform_data list of objects\\nThe POST policy form data.\\nShow 2 properties\\nurl string\\nThe URL that the file\\'s data should be uploaded to.\\nPOST / artifacts.versions.prepare\\ncURL\\n$ curl -X POST https://api.devrev.ai/artifacts.versions.prepare \\\\ > -H \" Authorization: Bearer <token> \" \\\\ > -H \" Content-Type: application/json \" \\\\ > -d \\' { > \"id\": \"ARTIFACT-12345\" > } \\'\\n200 Successful 1 { 2 \" form_data \" : [ 3 { 4 \" key \" : \"",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1643_KNOWLEDGE_NODE-48",
"text": "object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1302_KNOWLEDGE_NODE-55",
"text": "artifacts.locate\\nGets the download URL for the artifact.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the artifact to get the URL for.\\nversion string Optional\\nThe version of the artifact that needs to be fetched.\\nResponse.\\n\\nThis endpoint returns an object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1308_KNOWLEDGE_NODE-52",
"text": "artifacts.locate\\nGets the download URL for the artifact.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the artifact to get the URL for.\\nversion string Optional\\nThe version of the artifact that needs to be fetched.\\nResponse.\\n\\nThis endpoint returns an object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1372_KNOWLEDGE_NODE-3",
"text": "Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nPOST\\n\\n/artifacts.locate\\n\\n[code]\\n\\n $| curl -X POST https://api.devrev.ai/artifacts.locate \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer <token>\" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"id\": \"ARTIFACT-12345\" \\n >| }\\'\\n[/code] \\n \\nTry it\\n\\n200artifactsLocatePostExample\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"url\": \"foo\",",
"title": "Locate Artifacts (POST) — DevRev | Docs"
},
{
"id": "ART-1301_KNOWLEDGE_NODE-55",
"text": "artifacts.locate\\nGets the download URL for the artifact.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the artifact to get the URL for.\\nversion string Optional\\nThe version of the artifact that needs to be fetched.\\nResponse.\\n\\nThis endpoint returns an object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1377_KNOWLEDGE_NODE-1",
"text": "__\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[API Reference](/public/api-reference/getting-started)[Artifacts](/public/api-reference/artifacts/attachments)\\n\\n# Locate Artifacts\\n\\nGET\\n\\nhttps://api.devrev.ai/artifacts.locate\\n\\nTry it\\n\\nGets the download URL for the artifact.\\n\\n### Query parameters\\n\\nidstringRequired`format: \"id\"`\\n\\nThe ID of the artifact to get the URL",
"title": "Locate Artifacts — DevRev | Docs"
},
{
"id": "ART-1372_KNOWLEDGE_NODE-1",
"text": "__\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[API Reference](/public/api-reference/getting-started)[Artifacts](/public/api-reference/artifacts/attachments)\\n\\n# Locate Artifacts (POST)\\n\\nPOST\\n\\nhttps://api.devrev.ai/artifacts.locate\\n\\nTry it\\n\\nGets the download URL for the artifact.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\nidstringRequired`format: \"id\"`\\n\\nThe ID of the artifact to get the",
"title": "Locate Artifacts (POST) — DevRev | Docs"
},
{
"id": "ART-1307_KNOWLEDGE_NODE-53",
"text": "Optional\\nThe version of the artifact that needs to be fetched.\\nResponse.\\n\\nThis endpoint returns an object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1300_KNOWLEDGE_NODE-52",
"text": "string Required\\nThe ID of the artifact to get the URL for.\\nversion string Optional\\nThe version of the artifact that needs to be fetched.\\nResponse.\\n\\nThis endpoint returns an object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1304_KNOWLEDGE_NODE-55",
"text": "expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an object.\\nform_data list of objects\\nThe POST policy form data.\\nShow 2 properties\\nid",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1783_KNOWLEDGE_NODE-49",
"text": "for.\\nversion string Optional\\nThe version of the artifact that needs to be fetched.\\nResponse.\\n\\nThis endpoint returns an object.\\nurl string\\nThe artifact\\'s download URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nPOST / artifacts.locate\\ncURL\\n$ curl -X POST https://api.devrev.ai/artifacts.locate \\\\ > -H \" Authorization: Bearer <token> \" \\\\ > -H \" Content-Type: application/json \" \\\\ > -d \\' { > \"id\": \"ARTIFACT-12345\" > } \\'\\n200 Successful 1 { 2 \" expires_at \" : \"",
"title": "Locate — DevRev | Docs"
},
{
"id": "ART-1307_KNOWLEDGE_NODE-54",
"text": "string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an object.\\nform_data list of objects\\nThe POST policy form data.\\nShow 2 properties\\nid string\\nThe generated artifact\\'s ID.\\nurl string\\nThe URL that the file\\'s data should be uploaded to.\\nAPI Reference artifacts Versions Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.versions.prepare\\nPrepares a new version for an artifact, returning the URL and form data to upload the updated",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1300_KNOWLEDGE_NODE-53",
"text": "object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an object.\\nform_data list of objects\\nThe POST policy form data.\\nShow 2 properties\\nid string\\nThe generated artifact\\'s ID.\\nurl string\\nThe URL that the file\\'s data should be uploaded to.\\nAPI Reference artifacts Versions Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.versions.prepare\\nPrepares a new",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1779_KNOWLEDGE_NODE-52",
"text": "URL.\\nexpires_at datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Prepare.\\n\\nPOST https:// api.devrev.ai / artifacts.prepare\\nCreates an artifact and generates an upload URL for its data.\\nRequest.\\n\\nThis endpoint expects an object.\\nfile_name string Required\\nThe name of the file that\\'s being uploaded.\\nfile_type string Optional\\nThe type of file that\\'s being uploaded.\\nResponse.\\n\\nThis endpoint returns an object.\\nform_data list of objects\\nThe POST policy",
"title": "Get — DevRev | Docs"
}
] |
bebd0dc0-8a3d-46ac-84b3-168ad2d34320
|
add url source to Load Knowledge Base
|
[
{
"id": "ART-15716_KNOWLEDGE_NODE-18",
"text": "external knowledge bases via a\\xc2\\xa0URL or sitemap, and offers\\xc2\\xa0migration tools\\xc2\\xa0for certain platforms.\\n\\nIf you have a\\xc2\\xa0CSV file:\\n\\nIf the CSV contains\\xc2\\xa0URLs\\xc2\\xa0pointing to existing articles (from which content can be extracted), it may be usable.\\n\\nHowever, if the CSV contains the\\xc2\\xa0actual article content directly, DevRev currently\\xc2\\xa0does not support\\xc2\\xa0importing knowledge base articles from CSV files.\\n\\nFor the latest capabilities, check the",
"title": "Support queries related playbook"
},
{
"id": "ART-1985_KNOWLEDGE_NODE-29",
"text": "a new article using the rich-text editor.\\n * Add a link to an existing article hosted on a website. When selected, this link should redirect to the source in a new browser tab, ensuring view access to the document link.\\n * Upload a file (PDF or MS Word document). Selecting a PDF should open the source in a new browser tab, while selecting a Word file should download the source, requiring the user to open it in the MS Word application.\\n3. If you are writing a new article, specify",
"title": "Articles | Knowledge Base | Computer for Support Teams | DevRev"
},
{
"id": "ART-1978_KNOWLEDGE_NODE-36",
"text": "base** > **Articles** and click **+Articles**. From there, you can either add a link to your article or upload articles directly from your device. Once you have added the articles, you can specify their status as either *Draft* or *Published*.\\nOnce the articles are published, your customers are able to search for them on the customer portal by entering their queries in the search bar.\\n\\nTo know more, refer to [articles](./articles)\\n\\nCustomize the customer",
"title": "Customer portal | Computer for Support Teams | DevRev"
},
{
"id": "ART-1978_KNOWLEDGE_NODE-35",
"text": "existing identity system. If the organization does not use a centralized identity provider, SSO can be setup using the JWT-based method.\\n3. Federated: Users log in through an identity provider such as Okta.\\n\\n### Integrating your knowledge base articles\\n\\nYou have the option to upload your articles or provide us with links to those articles, which can be hosted on your website or any other publicly accessible platform.\\nTo upload articles, go to **Settings** > **Support** > **Knowledge",
"title": "Customer portal | Computer for Support Teams | DevRev"
}
] |
8e5c3ef8-f15b-4ddd-a9e8-603cc287a6d8
|
DevRev Service Level Agreement uptime turnaround time service quality mean time to recovery backlog
|
[
{
"id": "ART-4172_KNOWLEDGE_NODE-16",
"text": "March 31 | October 22 |\\n| April 14 | December 25 |\\n| April 18 | |\\n\\n**ARGENTINA(US) Holiday Schedule**\\n\\n| Dates | Dates cont. |\\n| --- | --- |\\n| January 1 | June 20 |\\n| March 3 | July 9 |\\n| March 4 | August 15 |\\n| March 24 | August 18 |\\n| April 2 | October 13 |\\n| April 18 | November 21 |\\n| May 1 | November 24 |\\n| May 2 | December 8 |\\n\\n### 8. DevRev Uptime Commitment\\n\\nDevRev aims to achieve a quarterly uptime of 99.9% for the services provided under this agreement. Uptime is",
"title": "DevRev Service Level Agreement"
},
{
"id": "ART-13039_KNOWLEDGE_NODE-15",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "List Surveys (POST) — DevRev | Docs"
},
{
"id": "ART-4088_KNOWLEDGE_NODE-6",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "Authorize Keyrings — DevRev | Docs"
},
{
"id": "ART-4083_KNOWLEDGE_NODE-8",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "Add Groups Members — DevRev | Docs"
},
{
"id": "ART-1373_KNOWLEDGE_NODE-12",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "Get Artifact — DevRev | Docs"
},
{
"id": "ART-2818_KNOWLEDGE_NODE-25",
"text": "legally-binding\\ncommitments, but metrics for tracking team performance.\\n\\n![]()\\n\\nFor more information, refer to the\\n[Operational SLA Metrics snap-in](/marketplace/operational-sla-metrics)\\non the DevRev marketplace.\\n\\nInstallation\\n------------\\n\\n1. In DevRev, go to **Settings** > **Snap-ins** and click **Explore\\n Marketplace** in the top-right corner.\\n2. In the DevRev marketplace, find **Operational SLA Metrics** and click\\n **Install**.\\n3. Click **Save** > **Install",
"title": "Operational SLA Metrics | Automate | Snap-ins | DevRev"
},
{
"id": "ART-1473_KNOWLEDGE_NODE-33",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "Snap-in triggered by an external source — DevRev | Docs"
},
{
"id": "ART-2897_KNOWLEDGE_NODE-29",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "Methods — DevRev | Docs"
},
{
"id": "ART-13043_KNOWLEDGE_NODE-8",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "Submit Surveys — DevRev | Docs"
},
{
"id": "ART-4073_KNOWLEDGE_NODE-26",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "Get Conversation — DevRev | Docs"
},
{
"id": "ART-4094_KNOWLEDGE_NODE-14",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "List Links — DevRev | Docs"
},
{
"id": "ART-3192_KNOWLEDGE_NODE-8",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "January 8, 2025 — DevRev | Docs"
},
{
"id": "ART-2715_KNOWLEDGE_NODE-14",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "List SLAs (POST) — DevRev | Docs"
},
{
"id": "ART-1418_KNOWLEDGE_NODE-11",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "Get Rev Org (POST) — DevRev | Docs"
},
{
"id": "ART-13032_KNOWLEDGE_NODE-14",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "Scan Rev Users (POST) — DevRev | Docs"
},
{
"id": "ART-4070_KNOWLEDGE_NODE-19",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "Update Article — DevRev | Docs"
},
{
"id": "ART-1471_KNOWLEDGE_NODE-14",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "Restricted messages on a timeline — DevRev | Docs"
},
{
"id": "ART-4092_KNOWLEDGE_NODE-12",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "Get Link — DevRev | Docs"
},
{
"id": "ART-1379_KNOWLEDGE_NODE-9",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "Prepare Artifacts — DevRev | Docs"
},
{
"id": "ART-12966_KNOWLEDGE_NODE-9",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "Get Metric Definition — DevRev | Docs"
},
{
"id": "ART-1395_KNOWLEDGE_NODE-18",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "List Dev Users (POST) — DevRev | Docs"
},
{
"id": "ART-1377_KNOWLEDGE_NODE-8",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "Locate Artifacts — DevRev | Docs"
},
{
"id": "ART-1365_KNOWLEDGE_NODE-6",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "Attachments — DevRev | Docs"
},
{
"id": "ART-1475_KNOWLEDGE_NODE-29",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "DevRev CLI reference — DevRev | Docs"
},
{
"id": "ART-4106_KNOWLEDGE_NODE-15",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "List Sys Users (POST) — DevRev | Docs"
},
{
"id": "ART-4103_KNOWLEDGE_NODE-11",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "Get Service Account — DevRev | Docs"
},
{
"id": "ART-4102_KNOWLEDGE_NODE-15",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "Update Rev User — DevRev | Docs"
},
{
"id": "ART-4062_KNOWLEDGE_NODE-16",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "Update Dev User — DevRev | Docs"
},
{
"id": "ART-4253_KNOWLEDGE_NODE-5",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "April 2, 2025 — DevRev | Docs"
},
{
"id": "ART-12979_KNOWLEDGE_NODE-12",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "List Code Changes — DevRev | Docs"
},
{
"id": "ART-1396_KNOWLEDGE_NODE-11",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "List Auth Tokens (POST) — DevRev | Docs"
},
{
"id": "ART-1397_KNOWLEDGE_NODE-14",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "Self Dev User (POST) — DevRev | Docs"
},
{
"id": "ART-4226_KNOWLEDGE_NODE-8",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "Deferred Snap Kit Action Execute — DevRev | Docs"
},
{
"id": "ART-12446_KNOWLEDGE_NODE-10",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "May 19, 2025 — DevRev | Docs"
},
{
"id": "ART-4228_KNOWLEDGE_NODE-17",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "List Surveys Responses (POST) — DevRev | Docs"
},
{
"id": "ART-2814_KNOWLEDGE_NODE-15",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "Snap Components — DevRev | Docs"
},
{
"id": "ART-13046_KNOWLEDGE_NODE-15",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "Create Web Crawler Job — DevRev | Docs"
},
{
"id": "ART-1438_KNOWLEDGE_NODE-22",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "Create Work — DevRev | Docs"
},
{
"id": "ART-13005_KNOWLEDGE_NODE-9",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "Count Meetings — DevRev | Docs"
},
{
"id": "ART-13021_KNOWLEDGE_NODE-13",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "List Org Schedules — DevRev | Docs"
},
{
"id": "ART-3894_KNOWLEDGE_NODE-12",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "List Stage Diagrams (Beta) — DevRev | Docs"
},
{
"id": "ART-1678_KNOWLEDGE_NODE-9",
"text": "[SLA](https://devrev.ai/legal/sla)\\n * [DPA](https://devrev.ai/legal/dpa)\\n * [Subprocessors](https://devrev.ai/security/sub-processors)\\n * [Cookie Policy](https://devrev.ai/legal/cookie-policy)\\n * [Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise",
"title": "Get States Custom (Beta) — DevRev | Docs"
}
] |
dd923851-ecc0-4abc-b4ff-665cf49b99bd
|
Incident Ticket not setting back to Open when customer replied
|
[
{
"id": "ART-2012_KNOWLEDGE_NODE-26",
"text": "customer knows why a new ticket was created. The following fields are automatically set on the follow-up ticket based on the archived ticket:\\n\\n * **Title**\\n * **Customer**\\n * **Reported By**\\n * **Tag** is_followup In addition, the tag has_followup is added to the archived ticket.\\n\\nIf the customer responds to a ticket in the terminal stage for the second time, their message will be added to that ticket and the **Needs response** toggle will be enabled. However, no follow-up tickets",
"title": "Follow-up ticket | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2012_KNOWLEDGE_NODE-25",
"text": "following stages under the _Closed_ state: _Resolved_ , _Archived_ , _Accepted_ , _Canceled_. _Archived_ is the terminal stage. Now if a customer sends a new email or adds a new comment on the archived ticket from the customer portal, the archived ticket remains archived and a follow-up ticket is created. A message is added to the archived ticket automatically based on your configuration. The follow-up ticket will have the reference of the archived ticket in the first message so that your",
"title": "Follow-up ticket | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2012_KNOWLEDGE_NODE-28",
"text": "say \\xe2\\x80\\x9cI would like to add a terminal stage on my tickets\\xe2\\x80\\x9d and we will get it done.\\n\\n * If no terminal stage is set, tickets will reopen on new comments from customers if **Reopen Closed Tickets on customer message** is enabled in the [convergence snap-in](./converge). The tickets move to the _In Progress_ state by default.\\n\\n * If you connected your support email address with DevRev, it is recommended that you enable the **Allow automations to send email** in your",
"title": "Follow-up ticket | Automate | Snap-ins | DevRev"
},
{
"id": "ART-1979_KNOWLEDGE_NODE-61",
"text": "following scenarios can lead to the creation of follow up ticket:\\n\\n* Customers communicated on an archived/immutable ticket from any channel such as email.\\n* Customer communicated on a merged ticket and the primary ticket is also archived.\\n\\nAfter creation of a follow up ticket the customer messages will reflect only on the new followup ticket and the customer will continue to see response on the same thread in channels like email & slack. The user can continue responding on the new follow",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-2009_KNOWLEDGE_NODE-28",
"text": "ticket's stage when linked issue is linked or unlinked.\\n* Close pending tickets if they have remained in the *Awaiting customer response* stage for longer than x days.\\n* Update ticket's stage to waiting on user when user reverts on new conversation.\\n* Update ticket's stage to *Accepted* and notify owner and customers when an enhancement in ideation stage is linked.\\n* Update a spam conversation's stage to *Suspended*.\\n* Update a spam ticket's stage to",
"title": "Convergence | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2012_KNOWLEDGE_NODE-24",
"text": "customer comments on permanently closed tickets. It allows you to configure the time after which a ticket stage should be marked as closed and creates a new follow-up ticket along with all the attachments and a custom message to let the customers know that the ticket is permanently closed automatically if required.\\n\\nFor more information, refer to the [Follow-up ticket snap-in](https://marketplace.devrev.ai/followup?) on the DevRev marketplace.\\n\\nLet\\xe2\\x80\\x99s say your ticket has the",
"title": "Follow-up ticket | Automate | Snap-ins | DevRev"
},
{
"id": "ART-1974_KNOWLEDGE_NODE-28",
"text": "transitions from *new* to *waiting on user*. When a customer responds back to support, the stage transitions to *needs response*.\\n\\n Towards the end of the conversation when the resolution is expected to be valid, the customer experience engineer asks the customer to acknowledge their concerns have been resolved. When the customer experience engineer asks this question the stage transitions to *waiting on user*, and if they validate it moves to *needs response* for the customer experience",
"title": "Conversations | Computer for Support Teams | DevRev"
},
{
"id": "ART-1979_KNOWLEDGE_NODE-60",
"text": "tickets\\n-----------------\\n\\nFollow up tickets allow support teams to seamlessly address unresolved issues, recurring problems, or additional concerns without losing context. By linking follow-up tickets to the original ticket(archived/immutable), teams can track ongoing issues more effectively, minimize duplicate work and enhance customer experience. A follow-up ticket is a new ticket that is created and linked when a customer responds in reference to an archived/immutable ticket. The",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-13189_KNOWLEDGE_NODE-37",
"text": "Experience\\n\\n We have improved our follow-up ticket experience & enhancing the way immutable tickets handle new customer messages. This update focuses on reducing duplicated efforts and streamlining communication across different channels.\\n\\n New Features:\\n\\n + Unified Follow-Up Ticket Creation: Introduces the ability to automatically create and link follow-up tickets when a customer responds to an archived ticket across various communication channels.\\n + Configurable Follow-Up",
"title": "March and April 2025 | Changelog | DevRev"
},
{
"id": "ART-1979_KNOWLEDGE_NODE-43",
"text": "*awaiting customer response* until the customer responds.\\n\\n In certain scenarios, the customer experience engineer may be able to resolve the customer's concern. If that's the case, they would ask the customer if their resolution has resolved their concern and the stage would move to the *awaiting customer response*. Once the concern is resolved and the customer acknowledges the resolution, the stage may move to *resolved*. If the concern isn't resolved, the stage may change back to *work in",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-2027_KNOWLEDGE_NODE-43",
"text": "recipients in the **To** or **Cc**\\n\\nThreading\\n---------\\n\\nEmail integration preserves threading by using the **References** and **In-Reply-To** email headers and by correlating the email **Subject** field and the ticket title. If either the ticket title or the email subject is changed at any point after ticket creation, follow up emails may cause a new ticket to be created.\\n\\n![]()\\n\\nOnce a ticket is created from an email, it is recommended to avoid changing the email subject or the",
"title": "Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2012_KNOWLEDGE_NODE-27",
"text": "will be created, and the previous ticket stage will remain unchanged.\\n\\n## Prerequisities\\n\\n * Before you install this snap-in, you need to set the **Stage** in closed state as a terminal stage or permanently closed stage. That is, once the ticket is moved to this stage, it cannot be reopened.\\n\\nNone of the default stages are terminal stages.\\n\\n * To create a new terminal stage, contact DevRev via the PLuG widget (chat bubble) on the bottom left of your home screen of the DevRev app. Just",
"title": "Follow-up ticket | Automate | Snap-ins | DevRev"
},
{
"id": "ART-4965_KNOWLEDGE_NODE-24",
"text": "[Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Ticket Immutability](/docs/automations/ticket-immutability)\\n\\nTicket Immutability\\n===================\\n\\nThe [ticket immutability](https://marketplace.devrev.ai/followup) snap-in enables automatic enforcement of immutability on tickets. Once activated, tickets are marked as immutable after a defined number of days in a closed state\\xe2\\x80\\x94excluding those in the \"Accepted\" stage. After this period, no further modifications are",
"title": "Ticket Immutability | Automate | Snap-ins | DevRev"
}
] |
cc721d56-48f9-44a8-96c7-3e8dd22db74c
|
change specific ticket field with reminder
|
[
{
"id": "ART-2874_KNOWLEDGE_NODE-25",
"text": "mappings specified in the configuration input. The process features robust error handling, detailed logging, and appends a summary comment to the timeline for easy update tracking.\\n\\nInstallation\\n------------\\n\\n1. Install the **Ticket Issue Field Migrator** snap-in from the DevRev marketplace.\\n2. Select the workspace where you want to install the snap-in, confirm your selection, and click **Deploy snap-in**.\\n\\nConfiguration\\n-------------\\n\\n1. In DevRev, go to **Settings** > **Snap-ins**",
"title": "Ticket issue field migrator | Automate | Snap-ins | DevRev"
}
] |
dd892583-2efe-4c2a-972e-3759fe2470e5
|
create knowledge graph in DevRev
|
[
{
"id": "ART-1822_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1649_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-4090_KNOWLEDGE_NODE-1",
"text": "__\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[API Reference](/public/api-reference/getting-started)[Links](/public/api-reference/links/create)\\n\\n# Create Link\\n\\nPOST\\n\\nhttps://api.devrev.ai/links.create\\n\\nTry it\\n\\nCreates a link between two objects to indicate a relationship.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\nlink_typeenumRequired\\n\\nType of link used to define the",
"title": "Create Link — DevRev | Docs"
},
{
"id": "ART-1787_KNOWLEDGE_NODE-242",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1826_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1605_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1823_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1577_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1654_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1609_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1607_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1838_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1833_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1639_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "Export Post — DevRev | Docs"
},
{
"id": "ART-1831_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1593_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1588_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1579_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1637_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1837_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1652_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1653_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1821_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1825_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1836_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1651_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1590_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1819_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "Sla Trackers Get — DevRev | Docs"
},
{
"id": "ART-1592_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1509_KNOWLEDGE_NODE-240",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "Prepare — DevRev | Docs"
},
{
"id": "ART-1824_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1575_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1636_KNOWLEDGE_NODE-238",
"text": "https:// api.devrev.ai / links.create\\nCreates a link between two objects to indicate a relationship.\\nRequest.\\n\\nThis endpoint expects an object.\\nlink_type enum Required\\nType of link used to define the relationship.\\nShow 12 enum values\\nsource string Required\\nThe ID of the source object.\\ntarget string Required\\nThe ID of the target object.\\nResponse.\\n\\nThis endpoint returns an object.\\nlink object\\nShow 9 properties\\nAPI Reference links Delete.\\n\\nPOST https:// api.devrev.ai /",
"title": "Update — DevRev | Docs"
}
] |
613f8af0-2919-434e-866e-12570a0ab0e7
|
create workflow to convert WhatsApp messages to tickets
|
[
{
"id": "ART-6174_KNOWLEDGE_NODE-28",
"text": "tickets\\n--------------------------------\\n\\n**Manual conversion**\\n\\nGo to the conversation record pane and select **Convert to Ticket** to create a new ticket from the conversation.\\n\\n![]()\\n\\n**Automated conversion via workflows**\\n\\nSet up automated [workflows](./workflow-engine) to convert conversations to tickets based on specific triggers:\\n\\n* When a conversation meets defined criteria\\n* When the AI agent identifies an issue requiring escalation\\n* According to custom business",
"title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev"
},
{
"id": "ART-6174_KNOWLEDGE_NODE-26",
"text": "functionality is replaced with a new **Convert to Ticket** feature. Currently, the conversion feature is available only for Plug and Slack conversations. Other channels still use the traditional **Link Ticket** functionality.\\n\\nConversion cannot be undone. Once a conversation is converted to a ticket, this action is permanent and the conversation remains archived.\\n\\nConversation conversion process\\n-------------------------------\\n\\nWhen you convert a conversation to a ticket, the following",
"title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev"
},
{
"id": "ART-4271_KNOWLEDGE_NODE-31",
"text": "AI-handled conversation reaches its capability limits and needs human expertise.\\n * **Extended troubleshooting** : Issues requiring multiple steps or follow-ups over time.\\n\\n## Key information\\n\\n * **Channel support** : Currently, the conversion feature is only available for PLuG and Slack conversations. Other channels still use the traditional **Link Ticket** functionality.\\n\\n * **CSAT surveys** : CSAT surveys are not sent when a conversation is converted to a ticket. Surveys are only",
"title": "Convert Conversations to Tickets | Conversations | Support | DevRev"
},
{
"id": "ART-12390_KNOWLEDGE_NODE-29",
"text": "Ticket | Creates a new ticket in DevRev. | * Ticket details like title, body, applies\\\\_to\\\\_part, etc. * subtype: (Optional) Ticket subtype * apps: (Optional) Related apps * app\\\\_custom\\\\_fields: (Optional) Custom fields | Created ticket object |\\n| Convert Conversation To Ticket | Converts a conversation to a ticket. | * conversation\\\\_id: ID of the conversation to convert | ticket\\\\_id: ID of the created ticket |\\n\\nObject retrieval\\n----------------\\n\\n| Operation | Description | Input",
"title": "Workflow action library | Workflows | Computer by DevRev | DevRev"
}
] |
2f249eb8-7b5a-4013-9449-f9d82147266f
|
reopen ticket rules disallow reopening
|
[
{
"id": "ART-2012_KNOWLEDGE_NODE-28",
"text": "say \\xe2\\x80\\x9cI would like to add a terminal stage on my tickets\\xe2\\x80\\x9d and we will get it done.\\n\\n * If no terminal stage is set, tickets will reopen on new comments from customers if **Reopen Closed Tickets on customer message** is enabled in the [convergence snap-in](./converge). The tickets move to the _In Progress_ state by default.\\n\\n * If you connected your support email address with DevRev, it is recommended that you enable the **Allow automations to send email** in your",
"title": "Follow-up ticket | Automate | Snap-ins | DevRev"
},
{
"id": "ART-4965_KNOWLEDGE_NODE-26",
"text": "snap-in.\\n\\nConfiguration\\n-------------\\n\\nIn the **Configuration Settings**, select the number of days (0 < x < 365) after which a closed ticket becomes immutable.\\n\\n[PreviousTicket issue field migrator](/docs/automations/ticket-issue-field-migrator)[NextTicket email notifier](/docs/automations/ticket-email-notifier)\\n\\n#### On this page\\n\\n* [Installation](#installation)\\n* [Configuration](#configuration)\\n\\n[Enterprise grade security to protect customer data\\n\\nLearn more about",
"title": "Ticket Immutability | Automate | Snap-ins | DevRev"
},
{
"id": "ART-4965_KNOWLEDGE_NODE-24",
"text": "[Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Ticket Immutability](/docs/automations/ticket-immutability)\\n\\nTicket Immutability\\n===================\\n\\nThe [ticket immutability](https://marketplace.devrev.ai/followup) snap-in enables automatic enforcement of immutability on tickets. Once activated, tickets are marked as immutable after a defined number of days in a closed state\\xe2\\x80\\x94excluding those in the \"Accepted\" stage. After this period, no further modifications are",
"title": "Ticket Immutability | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2012_KNOWLEDGE_NODE-24",
"text": "customer comments on permanently closed tickets. It allows you to configure the time after which a ticket stage should be marked as closed and creates a new follow-up ticket along with all the attachments and a custom message to let the customers know that the ticket is permanently closed automatically if required.\\n\\nFor more information, refer to the [Follow-up ticket snap-in](https://marketplace.devrev.ai/followup?) on the DevRev marketplace.\\n\\nLet\\xe2\\x80\\x99s say your ticket has the",
"title": "Follow-up ticket | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2012_KNOWLEDGE_NODE-25",
"text": "following stages under the _Closed_ state: _Resolved_ , _Archived_ , _Accepted_ , _Canceled_. _Archived_ is the terminal stage. Now if a customer sends a new email or adds a new comment on the archived ticket from the customer portal, the archived ticket remains archived and a follow-up ticket is created. A message is added to the archived ticket automatically based on your configuration. The follow-up ticket will have the reference of the archived ticket in the first message so that your",
"title": "Follow-up ticket | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2012_KNOWLEDGE_NODE-27",
"text": "will be created, and the previous ticket stage will remain unchanged.\\n\\n## Prerequisities\\n\\n * Before you install this snap-in, you need to set the **Stage** in closed state as a terminal stage or permanently closed stage. That is, once the ticket is moved to this stage, it cannot be reopened.\\n\\nNone of the default stages are terminal stages.\\n\\n * To create a new terminal stage, contact DevRev via the PLuG widget (chat bubble) on the bottom left of your home screen of the DevRev app. Just",
"title": "Follow-up ticket | Automate | Snap-ins | DevRev"
},
{
"id": "ART-1979_KNOWLEDGE_NODE-60",
"text": "tickets\\n-----------------\\n\\nFollow up tickets allow support teams to seamlessly address unresolved issues, recurring problems, or additional concerns without losing context. By linking follow-up tickets to the original ticket(archived/immutable), teams can track ongoing issues more effectively, minimize duplicate work and enhance customer experience. A follow-up ticket is a new ticket that is created and linked when a customer responds in reference to an archived/immutable ticket. The",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-2012_KNOWLEDGE_NODE-26",
"text": "customer knows why a new ticket was created. The following fields are automatically set on the follow-up ticket based on the archived ticket:\\n\\n * **Title**\\n * **Customer**\\n * **Reported By**\\n * **Tag** is_followup In addition, the tag has_followup is added to the archived ticket.\\n\\nIf the customer responds to a ticket in the terminal stage for the second time, their message will be added to that ticket and the **Needs response** toggle will be enabled. However, no follow-up tickets",
"title": "Follow-up ticket | Automate | Snap-ins | DevRev"
},
{
"id": "ART-13189_KNOWLEDGE_NODE-37",
"text": "Experience\\n\\n We have improved our follow-up ticket experience & enhancing the way immutable tickets handle new customer messages. This update focuses on reducing duplicated efforts and streamlining communication across different channels.\\n\\n New Features:\\n\\n + Unified Follow-Up Ticket Creation: Introduces the ability to automatically create and link follow-up tickets when a customer responds to an archived ticket across various communication channels.\\n + Configurable Follow-Up",
"title": "March and April 2025 | Changelog | DevRev"
},
{
"id": "ART-1979_KNOWLEDGE_NODE-61",
"text": "following scenarios can lead to the creation of follow up ticket:\\n\\n* Customers communicated on an archived/immutable ticket from any channel such as email.\\n* Customer communicated on a merged ticket and the primary ticket is also archived.\\n\\nAfter creation of a follow up ticket the customer messages will reflect only on the new followup ticket and the customer will continue to see response on the same thread in channels like email & slack. The user can continue responding on the new follow",
"title": "Tickets | Computer for Support Teams | DevRev"
}
] |
0952227d-de01-4623-8671-e8a0533d9cd9
|
automatic linking of follow-up tickets
|
[
{
"id": "ART-1979_KNOWLEDGE_NODE-60",
"text": "tickets\\n-----------------\\n\\nFollow up tickets allow support teams to seamlessly address unresolved issues, recurring problems, or additional concerns without losing context. By linking follow-up tickets to the original ticket(archived/immutable), teams can track ongoing issues more effectively, minimize duplicate work and enhance customer experience. A follow-up ticket is a new ticket that is created and linked when a customer responds in reference to an archived/immutable ticket. The",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-2012_KNOWLEDGE_NODE-26",
"text": "customer knows why a new ticket was created. The following fields are automatically set on the follow-up ticket based on the archived ticket:\\n\\n * **Title**\\n * **Customer**\\n * **Reported By**\\n * **Tag** is_followup In addition, the tag has_followup is added to the archived ticket.\\n\\nIf the customer responds to a ticket in the terminal stage for the second time, their message will be added to that ticket and the **Needs response** toggle will be enabled. However, no follow-up tickets",
"title": "Follow-up ticket | Automate | Snap-ins | DevRev"
},
{
"id": "ART-13189_KNOWLEDGE_NODE-37",
"text": "Experience\\n\\n We have improved our follow-up ticket experience & enhancing the way immutable tickets handle new customer messages. This update focuses on reducing duplicated efforts and streamlining communication across different channels.\\n\\n New Features:\\n\\n + Unified Follow-Up Ticket Creation: Introduces the ability to automatically create and link follow-up tickets when a customer responds to an archived ticket across various communication channels.\\n + Configurable Follow-Up",
"title": "March and April 2025 | Changelog | DevRev"
},
{
"id": "ART-1979_KNOWLEDGE_NODE-61",
"text": "following scenarios can lead to the creation of follow up ticket:\\n\\n* Customers communicated on an archived/immutable ticket from any channel such as email.\\n* Customer communicated on a merged ticket and the primary ticket is also archived.\\n\\nAfter creation of a follow up ticket the customer messages will reflect only on the new followup ticket and the customer will continue to see response on the same thread in channels like email & slack. The user can continue responding on the new follow",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-13189_KNOWLEDGE_NODE-38",
"text": "Behavior: Provides options to configure the behavior of follow-up tickets in workflows, ensuring that notifications and updates are managed according to user preferences.\\n + Customers continue to see the new follow up ticket in the same thread for channels like email\\n* The Real-Time Sentiment Analysis snap-in enables seamless sentiment detection and real-time updates within the ticketing system. With each customer message, sentiment is automatically analyzed and categorized into five levels:",
"title": "March and April 2025 | Changelog | DevRev"
},
{
"id": "ART-2012_KNOWLEDGE_NODE-25",
"text": "following stages under the _Closed_ state: _Resolved_ , _Archived_ , _Accepted_ , _Canceled_. _Archived_ is the terminal stage. Now if a customer sends a new email or adds a new comment on the archived ticket from the customer portal, the archived ticket remains archived and a follow-up ticket is created. A message is added to the archived ticket automatically based on your configuration. The follow-up ticket will have the reference of the archived ticket in the first message so that your",
"title": "Follow-up ticket | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2027_KNOWLEDGE_NODE-43",
"text": "recipients in the **To** or **Cc**\\n\\nThreading\\n---------\\n\\nEmail integration preserves threading by using the **References** and **In-Reply-To** email headers and by correlating the email **Subject** field and the ticket title. If either the ticket title or the email subject is changed at any point after ticket creation, follow up emails may cause a new ticket to be created.\\n\\n![]()\\n\\nOnce a ticket is created from an email, it is recommended to avoid changing the email subject or the",
"title": "Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2027_KNOWLEDGE_NODE-44",
"text": "ticket title.\\n\\nSpecifically, threading breaks when the order of words in the subject is changed, when words are replaced, or when words or symbols are inserted in the middle or appended. Threading is maintained if the subject change is limited to the addition of words before :, words between [], words between ##, or common prefixes, such as Re or Fwd.\\n\\nRate limiting\\n-------------\\n\\nTo ensure that your support system is protected from potential spam attacks as well as from issues arising",
"title": "Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-40",
"text": "channel determines the sync location in DevRev:\\n\\n* **External/Connect channels:** Syncs with the **Customer Messages** panel.\\n* **Internal channels:** Syncs with the **Internal Discussions** panel.\\n\\nSyncing different panels to separate Slack threads is not supported.\\n\\n![]()\\n\\nOnly shared tickets are synchronized between DevRev and Slack.\\n\\n### Follow-up and merged Tickets\\n\\nThe Slack snap-in supports follow-up and merged tickets.\\n\\n* When two tickets merge, and both have syncing",
"title": "Slack | Integrate | Snap-ins | DevRev"
}
] |
f3ac30fb-0973-44f0-a003-6d2838cdda4b
|
create multiple workspaces for an account
|
[
{
"id": "ART-2000_KNOWLEDGE_NODE-25",
"text": "address.\\n\\nAccounts are associated with a workspace. An account can be a part of multiple workspaces at the same time. An account can also be linked to multiple opportunities. Accounts help you keep track of your customer contacts. Contacts are always linked to a workspace or an account.\\n\\nCreate an account\\n-----------------\\n\\nYou can create accounts in the following ways:\\n\\n### Using the DevRev app\\n\\n1. Go to **Accounts** > **+ Account**.\\n2. Fill in the details like account name,",
"title": "Accounts | Computer for Growth Teams | DevRev"
},
{
"id": "ART-2000_KNOWLEDGE_NODE-32",
"text": "an account, go to **Account** > **Workspace** and select **New workspace**.\\n\\n[PreviousComputer for Growth Teams](/docs/product/grow)[NextOpportunities](/docs/product/opportunity)\\n\\n#### On this page\\n\\n* [Create an account](#create-an-account)\\n* [Using the DevRev app](#using-the-devrev-app)\\n* [Bulk import accounts](#bulk-import-accounts)\\n* [Using DevRev APIs](#using-devrev-apis)\\n* [Account attributes](#account-attributes)\\n* [External reference](#external-reference)\\n* [Add a",
"title": "Accounts | Computer for Growth Teams | DevRev"
},
{
"id": "ART-1997_KNOWLEDGE_NODE-27",
"text": "timeline.\\n\\nYou can use a customizable set of states and stages to manage the lifecycle of an account, from prospect to customer to churned.\\n\\n\\xf0\\x9f\\x96\\xa5\\xef\\xb8\\x8f Workspace\\n------------\\n\\nA [workspace](https://docs.devrev.ai/product/glossary) represents an instance of a signed-up organization on your application. A workspace is also known as rev-org in the DevRev API. Customers can create multiple workspaces on your application. Therefore, you can link multiple workspaces to a",
"title": "Computer for Growth Teams | DevRev"
},
{
"id": "ART-15506_KNOWLEDGE_NODE-19",
"text": "\\xe2\\x9c\\x85 | If neither exists: System creates the account first, then creates the workspace. User is linked to both. If account exists but workspace doesn\\xe2\\x80\\x99t: System creates the workspace under the existing account. User is linked to both. If workspace exists under different account: System returns an error, as workspaces cannot be a part of 2 accounts. |\\n| \\xe2\\x9c\\x85 | \\xe2\\x9d\\x8c | If workspace doesn\\xe2\\x80\\x99t exist: System creates a new account and workspace (if needed).",
"title": "Identify your users with Plug | DevRev | Docs"
},
{
"id": "ART-1407_KNOWLEDGE_NODE-4",
"text": "Error\\n\\n403\\n\\nForbidden Error\\n\\n409\\n\\nConflict Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nPOST\\n\\n/rev-orgs.create\\n\\n[code]\\n\\n $| curl -X POST https://api.devrev.ai/rev-orgs.create \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer <token>\" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"account\": \"ACC-12345\", \\n >| \"display_name\": \"foo\" \\n >| }\\'\\n[/code]",
"title": "Create Rev Org — DevRev | Docs"
}
] |
7b180589-34fa-427c-adfe-aa93a6dd15c1
|
how to open resolved case in devrev
|
[
{
"id": "ART-2012_KNOWLEDGE_NODE-28",
"text": "say \\xe2\\x80\\x9cI would like to add a terminal stage on my tickets\\xe2\\x80\\x9d and we will get it done.\\n\\n * If no terminal stage is set, tickets will reopen on new comments from customers if **Reopen Closed Tickets on customer message** is enabled in the [convergence snap-in](./converge). The tickets move to the _In Progress_ state by default.\\n\\n * If you connected your support email address with DevRev, it is recommended that you enable the **Allow automations to send email** in your",
"title": "Follow-up ticket | Automate | Snap-ins | DevRev"
}
] |
b339421e-2166-41ca-a6bf-4b035f885136
|
issue adding recipients to tickets after ticket creation
|
[
{
"id": "ART-2027_KNOWLEDGE_NODE-31",
"text": "to the ticket via email. They cannot view the ticket on the portal, as they are added to the **Email members** field but not to the **Reported by** field.\\n\\nEmployees\\n\\n* With DevRev account (added to email thread)\\n\\n *Added to:* **To**, **CC**, or **Email members** field.\\n\\n *Is able to:* View the ticket on DevRev, reply via email, and receive in-app notifications. If they make changes to ticket attributes, they remain subscribers.\\n* Manually added subscribers\\n\\n *Added to:*",
"title": "Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2027_KNOWLEDGE_NODE-29",
"text": "your communication requirements.\\n\\nThe visibility and interaction capabilities with a ticket in DevRev are determined by the user's role and how they were added to the email thread.\\n\\nEnd users\\n\\n* Original sender\\n\\n *Added to:* **Reported by** or **Email members** field.\\n\\n *Is able to:* View the ticket on the portal and reply via email.\\n* An end user in the same organization\\n\\n *Added to:* **To** or **CC** fields in the email thread; **Reported by** field, **Email members** field,",
"title": "Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2027_KNOWLEDGE_NODE-30",
"text": "or @mentioned in the DevRev app.\\n\\n *Is able to:* View the ticket on the portal and reply via email as an email member.\\n* A customer admin for the same workspace\\n\\n *Added to:* **Customer Admins** group.\\n\\n *Is able to:* View the ticket on the portal once their workspace is updated on the ticket.\\n* An end user outside original sender's organization\\n\\n *Added to:* **To** or **CC** fields in the email thread, or mentioned in the DevRev app (adds them to **CC**).\\n\\n *Is able to:* Reply",
"title": "Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-1979_KNOWLEDGE_NODE-36",
"text": "contact](https://docs.devrev.ai/product/plug) must be created first for any emails to be added as subscribers.\\n* **Needs response**: Set to true whenever a new customer message is received on the ticket to ensure that no customer messages are missed. If a particular customer message does not need a response, the **Needs response** toggle can be turned off by the user. Turning off the **Needs response** toggle does not affect the SLA metrics.\\n\\nThese attributes can be effectively used in",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-1979_KNOWLEDGE_NODE-31",
"text": "from an email thread containing multiple customer email IDs, multiple reporters may be added. If a DevRev user adds a new customer while responding from DevRev, or if a new customer responds to the email thread, these new customers are added to the **Reported by** field. In the case of the Portal, there is only one **Reported by**, representing the person who has logged in to the portal to report the issue. Additional reporters can be added from the DevRev app. To select a contact in the",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-1979_KNOWLEDGE_NODE-35",
"text": "docs](https://docs.devrev.ai/import).\\n* **Close date**: The date the ticket was closed.\\n* **Source channel**: The channel through which the ticket was created. Customers can create tickets via email, the portal, and various other channels.\\n* **Channel**: Indicates the medium used for customer communication.\\n* **Subscribers**: Indicates the group of users who will receive updates about the tickets.External contacts cannot be added as subscribers, so a [DevRev",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-1979_KNOWLEDGE_NODE-32",
"text": "**Reported by** field, first choose the corresponding account and workspace in the **Customer** attribute. After this selection, the contact's name will appear in the **Reported by** list.\\n* **Email members**: Participants in the ongoing email thread, dependent on the last email. This attribute automatically updates based on the last email sent from or received on DevRev.\\n\\n![]()\\n\\nAdding members to **Email members** also adds them to the **Reported by** field. Removing members from **Email",
"title": "Tickets | Computer for Support Teams | DevRev"
}
] |
1ba2acc9-1733-49f6-a726-35cec8961a3c
|
create list views for custom objects in DevRev
|
[
{
"id": "ART-1949_KNOWLEDGE_NODE-25",
"text": "**Tickets**; **Build > Issues** and **Now, Next, Later**; and **Product > Parts**. Depending on the type of object there are different options for querying, sorting, customizing, and grouping.\\n\\n\\xf0\\x9f\\x8e\\xa5 Video: Applying filters to Vistas\\n\\nCreate a vista\\n--------------\\n\\n1. Select the object you want to make a list of, for example, tickets.\\n2. Make a change to the default view of the object by applying a filter, sorting, grouping, or customizing. A **Save as** button appears in the",
"title": "Vistas | Computer by DevRev | DevRev"
}
] |
e7d71ff0-679d-4e3b-9b7e-14e5867e60cf
|
Case creation and updates via Slack commands
|
[
{
"id": "ART-2035_KNOWLEDGE_NODE-37",
"text": "synchronized between DevRev and Slack.\\n\\nWork management using Slack\\n---------------------------\\n\\n### DevRev Tickets and Slack\\n\\nThe Slack snap-in allows users to create tickets directly from Slack. There are multiple ways to initiate ticket creation from any channel:\\n\\n* **Use the command:** Run /devrev create-ticket.\\n* **Message action:** Select **Create a new ticket** from the message actions.\\n* **Convert a Conversation:** Transform an ongoing conversation into a ticket. This is",
"title": "Slack | Integrate | Snap-ins | DevRev"
}
] |
17b4e4f7-6971-4bb9-bf26-99413fa4bd15
|
how to export a devrev dashboard
|
[
{
"id": "ART-4186_KNOWLEDGE_NODE-44",
"text": "the following dashboard widgets and tabs.\\n\\n### Tabs\\n\\n1. **Sessions**\\n\\n Widgets and visualizations for all the mobile sessions.\\n2. **Screens**\\n\\n Top screens and screens with crashes, errors, rage taps, and ANR.\\n3. **Events**\\n\\n Most frequently emitted custom events across screens.\\n4. **APIs**\\n\\n APIs that frequently error out, respond slowly, and are most popular.\\n\\n### Dashboard widgets\\n\\nEach tile in the Dashboard has a download icon. Click this icon to download the",
"title": "Computer for User Insights | Session analytics | Computer for Your Customers | DevRev"
}
] |
0172010c-2217-496f-86ef-3df49e35c02e
|
how to set up feedback after ticket closure
|
[
{
"id": "ART-2011_KNOWLEDGE_NODE-25",
"text": "be customized to align with their requirements.\\n\\nTo manually request CSAT feedback without having to wait until the ticket is resolved, use the /survey command in **Tickets** > **Customer messages**.\\n\\nInstallation\\n------------\\n\\n1. Install the [CSAT on ticket](/marketplace/csat_on_ticket_dwx7b2bp) from the DevRev marketplace.\\n2. Select the workspace to install the snap-in, confirm installation, and click **Deploy snap-in**.\\n\\nConfiguration\\n-------------\\n\\n1. Go to **Snap-ins** >",
"title": "CSAT on ticket | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2011_KNOWLEDGE_NODE-28",
"text": "only once per ticket** toggle.\\n10. If you want to automatically send CSAT surveys when tickets reach the *Resolved* stage, keep the **Trigger the CSAT survey based on configured rules** toggle turned off.\\n11. If you want to send CSAT at a specific ticket stage, turn the **Trigger the CSAT survey based on configured rules** toggle on and set up a custom workflow with the following configuration:\\n\\n| **Component** | **Details** |\\n| --- | --- |\\n| Trigger | Update Ticket |\\n| Stage Control |",
"title": "CSAT on ticket | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2011_KNOWLEDGE_NODE-26",
"text": "**CSAT on ticket** > **Configure**.\\n2. Select the channel you want to send the survey on in **Survey channel**.\\n3. Write introductory text for the survey in **Survey introductory text**.\\n\\n ![]()\\n\\n To include the customer's name in the CSAT survey emails, add a key {{customer\\\\_name}} to the introductory text configuration of the CSAT.\\n4. Customize your survey response scale which is shown to the customers to select from in **Survey response scale**.\\n5. To collect additional feedback",
"title": "CSAT on ticket | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2011_KNOWLEDGE_NODE-29",
"text": "If Else |\\n| Condition | When: Ticket Updated / Output > Stage > Name (Make sure that the stage name is in snake case.) |\\n| Action | Update Ticket |\\n| ID | Ticket Updated > Output > Id |\\n| List of Integrations | CSAT |\\n| Integrations | App CSAT Send Survey > Yes |\\n\\n1. Click **Save** > **Next** and deploy the snap-in.\\n\\n[PreviousCSAT on conversation](/docs/automations/csat-conv)[NextCSV work item uploader](/docs/automations/csv-work-item-uploader)\\n\\n#### On this page\\n\\n*",
"title": "CSAT on ticket | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2013_KNOWLEDGE_NODE-25",
"text": "after their conversation gets resolved. The questions can be customized to align with their requirements.\\n\\nTo manually request CSAT feedback without having to wait until the conversation is resolved, use the /survey command in **Inbox** > **Customer messages**.\\n\\n\\xf0\\x9f\\x8e\\xa5 Video: DevRev Plug surveys\\n\\nInstallation\\n------------\\n\\n\\xf0\\x9f\\x8e\\xa5 Video: DevRev Plug survey installation\\n\\n1. Install the [CSAT on",
"title": "CSAT on conversation | Automate | Snap-ins | DevRev"
},
{
"id": "ART-1953_KNOWLEDGE_NODE-32",
"text": "\\xe2\\x80\\x9cUpdate on your Conversation with {Company\\\\_Name}\"\\n\\n![]()\\n\\nThis email is only sent to organizations that have installed [Convergence snap-in](https://docs.devrev.ai/automations/converge).\\n\\nCSAT survey for conversation/ticket\\n-----------------------------------\\n\\n* **Trigger**: A CSAT survey is sent for a conversation or ticket.\\n* **Action**: The system sends out a notification with the ticket/conversation number and CSAT form.\\n* **Sender**: DevRev",
"title": "Customer email notifications | Computer by DevRev | DevRev"
}
] |
e344e12b-0ec3-49b7-b6c5-934f7fc84ae2
|
export entire conversation in TKT external only
|
[
{
"id": "ART-1827_KNOWLEDGE_NODE-87",
"text": "conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for conversations belonging to any of the provided parts.\\nfirst integer Optional\\nThe number of conversation items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\ngroup list of strings Optional\\nFilters for conversation that belong to the given groups.\\nis_creator_verified boolean Optional\\nFilters for conversations that",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1805_KNOWLEDGE_NODE-87",
"text": "conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for conversations belonging to any of the provided parts.\\nfirst integer Optional\\nThe number of conversation items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\ngroup list of strings Optional\\nFilters for conversation that belong to the given groups.\\nis_creator_verified boolean Optional\\nFilters for conversations that",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1838_KNOWLEDGE_NODE-87",
"text": "conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for conversations belonging to any of the provided parts.\\nfirst integer Optional\\nThe number of conversation items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\ngroup list of strings Optional\\nFilters for conversation that belong to the given groups.\\nis_creator_verified boolean Optional\\nFilters for conversations that",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1637_KNOWLEDGE_NODE-87",
"text": "conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for conversations belonging to any of the provided parts.\\nfirst integer Optional\\nThe number of conversation items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\ngroup list of strings Optional\\nFilters for conversation that belong to the given groups.\\nis_creator_verified boolean Optional\\nFilters for conversations that",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1833_KNOWLEDGE_NODE-87",
"text": "conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for conversations belonging to any of the provided parts.\\nfirst integer Optional\\nThe number of conversation items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\ngroup list of strings Optional\\nFilters for conversation that belong to the given groups.\\nis_creator_verified boolean Optional\\nFilters for conversations that",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1782_KNOWLEDGE_NODE-89",
"text": "conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for conversations belonging to any of the provided parts.\\nfirst integer Optional\\nThe number of conversation items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\ngroup list of strings Optional\\nFilters for conversation that belong to the given groups.\\nis_creator_verified boolean Optional\\nFilters for conversations that",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1806_KNOWLEDGE_NODE-87",
"text": "conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for conversations belonging to any of the provided parts.\\nfirst integer Optional\\nThe number of conversation items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\ngroup list of strings Optional\\nFilters for conversation that belong to the given groups.\\nis_creator_verified boolean Optional\\nFilters for conversations that",
"title": "Self Post — DevRev | Docs"
},
{
"id": "ART-1802_KNOWLEDGE_NODE-87",
"text": "conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for conversations belonging to any of the provided parts.\\nfirst integer Optional\\nThe number of conversation items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\ngroup list of strings Optional\\nFilters for conversation that belong to the given groups.\\nis_creator_verified boolean Optional\\nFilters for conversations that",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1818_KNOWLEDGE_NODE-87",
"text": "conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for conversations belonging to any of the provided parts.\\nfirst integer Optional\\nThe number of conversation items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\ngroup list of strings Optional\\nFilters for conversation that belong to the given groups.\\nis_creator_verified boolean Optional\\nFilters for conversations that",
"title": "Sla Trackers Get Post — DevRev | Docs"
},
{
"id": "ART-1607_KNOWLEDGE_NODE-87",
"text": "conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for conversations belonging to any of the provided parts.\\nfirst integer Optional\\nThe number of conversation items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\ngroup list of strings Optional\\nFilters for conversation that belong to the given groups.\\nis_creator_verified boolean Optional\\nFilters for conversations that",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1639_KNOWLEDGE_NODE-87",
"text": "conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for conversations belonging to any of the provided parts.\\nfirst integer Optional\\nThe number of conversation items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\ngroup list of strings Optional\\nFilters for conversation that belong to the given groups.\\nis_creator_verified boolean Optional\\nFilters for conversations that",
"title": "Export Post — DevRev | Docs"
},
{
"id": "ART-1655_KNOWLEDGE_NODE-87",
"text": "conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for conversations belonging to any of the provided parts.\\nfirst integer Optional\\nThe number of conversation items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\ngroup list of strings Optional\\nFilters for conversation that belong to the given groups.\\nis_creator_verified boolean Optional\\nFilters for conversations that",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1801_KNOWLEDGE_NODE-87",
"text": "conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for conversations belonging to any of the provided parts.\\nfirst integer Optional\\nThe number of conversation items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\ngroup list of strings Optional\\nFilters for conversation that belong to the given groups.\\nis_creator_verified boolean Optional\\nFilters for conversations that",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1832_KNOWLEDGE_NODE-87",
"text": "conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for conversations belonging to any of the provided parts.\\nfirst integer Optional\\nThe number of conversation items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\ngroup list of strings Optional\\nFilters for conversation that belong to the given groups.\\nis_creator_verified boolean Optional\\nFilters for conversations that",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1560_KNOWLEDGE_NODE-88",
"text": "conversations.export\\n\\nExports a collection of conversation items.\\n\\nQuery parameters.\\n\\napplies_to_parts string Optional\\n\\nFilters for conversations belonging to any of the provided parts.\\n\\nfirst integer Optional\\n\\nThe number of conversation items to return. The default is \\xe2\\x80\\x9850\\xe2\\x80\\x99, the maximum is \\xe2\\x80\\x985000\\xe2\\x80\\x99.\\n\\ngroup string Optional\\n\\nFilters for conversation that belong to the given groups.\\n\\nis_creator_verified boolean Optional\\n\\nFilters for",
"title": "Assign (Beta) — DevRev | Docs"
},
{
"id": "ART-1547_KNOWLEDGE_NODE-88",
"text": "conversations.export\\n\\nExports a collection of conversation items.\\n\\nQuery parameters.\\n\\napplies_to_parts string Optional\\n\\nFilters for conversations belonging to any of the provided parts.\\n\\nfirst integer Optional\\n\\nThe number of conversation items to return. The default is \\xe2\\x80\\x9850\\xe2\\x80\\x99, the maximum is \\xe2\\x80\\x985000\\xe2\\x80\\x99.\\n\\ngroup string Optional\\n\\nFilters for conversation that belong to the given groups.\\n\\nis_creator_verified boolean Optional\\n\\nFilters for",
"title": "Get Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1558_KNOWLEDGE_NODE-88",
"text": "conversations.export\\n\\nExports a collection of conversation items.\\n\\nQuery parameters.\\n\\napplies_to_parts string Optional\\n\\nFilters for conversations belonging to any of the provided parts.\\n\\nfirst integer Optional\\n\\nThe number of conversation items to return. The default is \\xe2\\x80\\x9850\\xe2\\x80\\x99, the maximum is \\xe2\\x80\\x985000\\xe2\\x80\\x99.\\n\\ngroup string Optional\\n\\nFilters for conversation that belong to the given groups.\\n\\nis_creator_verified boolean Optional\\n\\nFilters for",
"title": "Metric Definitions List (Beta) — DevRev | Docs"
},
{
"id": "ART-1836_KNOWLEDGE_NODE-87",
"text": "conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for conversations belonging to any of the provided parts.\\nfirst integer Optional\\nThe number of conversation items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\ngroup list of strings Optional\\nFilters for conversation that belong to the given groups.\\nis_creator_verified boolean Optional\\nFilters for conversations that",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-4271_KNOWLEDGE_NODE-25",
"text": "is being replaced with a new **Convert to Ticket** feature. This change provides a more seamless transition from conversation to ticket management.\\n\\n## How Conversation conversion works\\n\\nWhen you convert a conversation to a ticket, the following happens automatically:\\n\\n * The original conversation is moved to _Archived_ stage and cannot be reopened.\\n * A new ticket is created with: \\n * All internal discussions and customer messages copied from the conversation.\\n * Preserved",
"title": "Convert Conversations to Tickets | Conversations | Support | DevRev"
},
{
"id": "ART-1593_KNOWLEDGE_NODE-87",
"text": "conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for conversations belonging to any of the provided parts.\\nfirst integer Optional\\nThe number of conversation items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\ngroup list of strings Optional\\nFilters for conversation that belong to the given groups.\\nis_creator_verified boolean Optional\\nFilters for conversations that",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1609_KNOWLEDGE_NODE-87",
"text": "conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for conversations belonging to any of the provided parts.\\nfirst integer Optional\\nThe number of conversation items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\ngroup list of strings Optional\\nFilters for conversation that belong to the given groups.\\nis_creator_verified boolean Optional\\nFilters for conversations that",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1819_KNOWLEDGE_NODE-87",
"text": "conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for conversations belonging to any of the provided parts.\\nfirst integer Optional\\nThe number of conversation items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\ngroup list of strings Optional\\nFilters for conversation that belong to the given groups.\\nis_creator_verified boolean Optional\\nFilters for conversations that",
"title": "Sla Trackers Get — DevRev | Docs"
},
{
"id": "ART-1830_KNOWLEDGE_NODE-87",
"text": "conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for conversations belonging to any of the provided parts.\\nfirst integer Optional\\nThe number of conversation items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\ngroup list of strings Optional\\nFilters for conversation that belong to the given groups.\\nis_creator_verified boolean Optional\\nFilters for conversations that",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1650_KNOWLEDGE_NODE-87",
"text": "conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for conversations belonging to any of the provided parts.\\nfirst integer Optional\\nThe number of conversation items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\ngroup list of strings Optional\\nFilters for conversation that belong to the given groups.\\nis_creator_verified boolean Optional\\nFilters for conversations that",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1301_KNOWLEDGE_NODE-94",
"text": "the value must be one that\\'s specified in the tag\\'s allowed values.\\nResponse.\\n\\nThis endpoint returns an object.\\nconversations list of objects\\nThe resulting collection of conversation items.\\nShow 16 properties\\nAPI Reference conversations Export Post.\\n\\nPOST https:// api.devrev.ai / conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for conversations belonging to any of the",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1302_KNOWLEDGE_NODE-94",
"text": "the value must be one that\\'s specified in the tag\\'s allowed values.\\nResponse.\\n\\nThis endpoint returns an object.\\nconversations list of objects\\nThe resulting collection of conversation items.\\nShow 16 properties\\nAPI Reference conversations Export Post.\\n\\nPOST https:// api.devrev.ai / conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for conversations belonging to any of the",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1780_KNOWLEDGE_NODE-89",
"text": "the value must be one that\\'s specified in the tag\\'s allowed values.\\nResponse.\\n\\nThis endpoint returns an object.\\nconversations list of objects\\nThe resulting collection of conversation items.\\nShow 16 properties\\nAPI Reference conversations Export Post.\\n\\nPOST https:// api.devrev.ai / conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for conversations belonging to any of the",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1308_KNOWLEDGE_NODE-91",
"text": "the value must be one that\\'s specified in the tag\\'s allowed values.\\nResponse.\\n\\nThis endpoint returns an object.\\nconversations list of objects\\nThe resulting collection of conversation items.\\nShow 16 properties\\nAPI Reference conversations Export Post.\\n\\nPOST https:// api.devrev.ai / conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for conversations belonging to any of the",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1785_KNOWLEDGE_NODE-88",
"text": "the value must be one that\\'s specified in the tag\\'s allowed values.\\nResponse.\\n\\nThis endpoint returns an object.\\nconversations list of objects\\nThe resulting collection of conversation items.\\nShow 16 properties\\nAPI Reference conversations Export Post.\\n\\nPOST https:// api.devrev.ai / conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for conversations belonging to any of the",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1781_KNOWLEDGE_NODE-89",
"text": "list of objects\\nThe resulting collection of conversation items.\\nShow 16 properties\\nAPI Reference conversations Export Post.\\n\\nPOST https:// api.devrev.ai / conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for conversations belonging to any of the provided parts.\\nfirst integer Optional\\nThe number of conversation items to return. The default is \\'50\\', the maximum is",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1562_KNOWLEDGE_NODE-91",
"text": "the tag. If specified, the value must be one that\\xe2\\x80\\x99s specified in the tag\\xe2\\x80\\x99s allowed values.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nconversations list of objects\\n\\nThe resulting collection of conversation items.\\n\\nShow 16 properties\\nAPI Reference conversations Export Post.\\n\\nPOST https://api.devrev.ai / conversations.export\\n\\nExports a collection of conversation items.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings",
"title": "Get (Beta) — DevRev | Docs"
},
{
"id": "ART-1543_KNOWLEDGE_NODE-91",
"text": "the tag. If specified, the value must be one that\\xe2\\x80\\x99s specified in the tag\\xe2\\x80\\x99s allowed values.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nconversations list of objects\\n\\nThe resulting collection of conversation items.\\n\\nShow 16 properties\\nAPI Reference conversations Export Post.\\n\\nPOST https://api.devrev.ai / conversations.export\\n\\nExports a collection of conversation items.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings",
"title": "Metric Definitions List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1558_KNOWLEDGE_NODE-91",
"text": "the tag. If specified, the value must be one that\\xe2\\x80\\x99s specified in the tag\\xe2\\x80\\x99s allowed values.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nconversations list of objects\\n\\nThe resulting collection of conversation items.\\n\\nShow 16 properties\\nAPI Reference conversations Export Post.\\n\\nPOST https://api.devrev.ai / conversations.export\\n\\nExports a collection of conversation items.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings",
"title": "Metric Definitions List (Beta) — DevRev | Docs"
},
{
"id": "ART-1566_KNOWLEDGE_NODE-91",
"text": "the tag. If specified, the value must be one that\\xe2\\x80\\x99s specified in the tag\\xe2\\x80\\x99s allowed values.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nconversations list of objects\\n\\nThe resulting collection of conversation items.\\n\\nShow 16 properties\\nAPI Reference conversations Export Post.\\n\\nPOST https://api.devrev.ai / conversations.export\\n\\nExports a collection of conversation items.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings",
"title": "Transition (Beta) — DevRev | Docs"
},
{
"id": "ART-1305_KNOWLEDGE_NODE-94",
"text": "api.devrev.ai / conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for conversations belonging to any of the provided parts.\\nfirst integer Optional\\nThe number of conversation items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\ngroup list of strings Optional\\nFilters for conversation that belong to the given groups.\\nis_creator_verified boolean Optional\\nFilters for",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1509_KNOWLEDGE_NODE-89",
"text": "api.devrev.ai / conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for conversations belonging to any of the provided parts.\\nfirst integer Optional\\nThe number of conversation items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\ngroup list of strings Optional\\nFilters for conversation that belong to the given groups.\\nis_creator_verified boolean Optional\\nFilters for",
"title": "Prepare — DevRev | Docs"
},
{
"id": "ART-1547_KNOWLEDGE_NODE-91",
"text": "the tag. If specified, the value must be one that\\xe2\\x80\\x99s specified in the tag\\xe2\\x80\\x99s allowed values.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nconversations list of objects\\n\\nThe resulting collection of conversation items.\\n\\nShow 16 properties\\nAPI Reference conversations Export Post.\\n\\nPOST https://api.devrev.ai / conversations.export\\n\\nExports a collection of conversation items.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings",
"title": "Get Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1545_KNOWLEDGE_NODE-91",
"text": "the tag. If specified, the value must be one that\\xe2\\x80\\x99s specified in the tag\\xe2\\x80\\x99s allowed values.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nconversations list of objects\\n\\nThe resulting collection of conversation items.\\n\\nShow 16 properties\\nAPI Reference conversations Export Post.\\n\\nPOST https://api.devrev.ai / conversations.export\\n\\nExports a collection of conversation items.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings",
"title": "Create (Beta) — DevRev | Docs"
},
{
"id": "ART-1549_KNOWLEDGE_NODE-91",
"text": "the tag. If specified, the value must be one that\\xe2\\x80\\x99s specified in the tag\\xe2\\x80\\x99s allowed values.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nconversations list of objects\\n\\nThe resulting collection of conversation items.\\n\\nShow 16 properties\\nAPI Reference conversations Export Post.\\n\\nPOST https://api.devrev.ai / conversations.export\\n\\nExports a collection of conversation items.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings",
"title": "List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1560_KNOWLEDGE_NODE-91",
"text": "the tag. If specified, the value must be one that\\xe2\\x80\\x99s specified in the tag\\xe2\\x80\\x99s allowed values.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nconversations list of objects\\n\\nThe resulting collection of conversation items.\\n\\nShow 16 properties\\nAPI Reference conversations Export Post.\\n\\nPOST https://api.devrev.ai / conversations.export\\n\\nExports a collection of conversation items.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings",
"title": "Assign (Beta) — DevRev | Docs"
},
{
"id": "ART-1300_KNOWLEDGE_NODE-91",
"text": "collection of conversation items.\\nShow 16 properties\\nAPI Reference conversations Export Post.\\n\\nPOST https:// api.devrev.ai / conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for conversations belonging to any of the provided parts.\\nfirst integer Optional\\nThe number of conversation items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\ngroup list of strings",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1304_KNOWLEDGE_NODE-93",
"text": "Optional\\nThe value for the object\\'s association with the tag. If specified, the value must be one that\\'s specified in the tag\\'s allowed values.\\nResponse.\\n\\nThis endpoint returns an object.\\nconversations list of objects\\nThe resulting collection of conversation items.\\nShow 16 properties\\nAPI Reference conversations Export Post.\\n\\nPOST https:// api.devrev.ai / conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1783_KNOWLEDGE_NODE-88",
"text": "Optional\\nThe value for the object\\'s association with the tag. If specified, the value must be one that\\'s specified in the tag\\'s allowed values.\\nResponse.\\n\\nThis endpoint returns an object.\\nconversations list of objects\\nThe resulting collection of conversation items.\\nShow 16 properties\\nAPI Reference conversations Export Post.\\n\\nPOST https:// api.devrev.ai / conversations.export\\nExports a collection of conversation items.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts",
"title": "Locate — DevRev | Docs"
}
] |
e8ea62f6-b883-4b5f-819b-ed5df7a26f4e
|
make chat bot active on url
|
[
{
"id": "ART-15716_KNOWLEDGE_NODE-10",
"text": "work perfectly in a mobile WebView\\n\\nSetting Up the PluG Widget on a Website\\n\\nGo to your DevRev workspace, open PluG settings, configure the widget, and copy the provided JavaScript snippet. Paste it before the closing tag in your website\\xe2\\x80\\x99s HTML. Deploy your site and the widget should appear.\\n\\n[PLuG installation steps](https://developer.devrev.ai/public/sdks/web/installation)\\n\\nRenaming the \\'DevRev Turing\\' Chatbot - asked in slack channel\\n\\nTroubleshooting PluG AI",
"title": "Support queries related playbook"
},
{
"id": "ART-2059_KNOWLEDGE_NODE-6",
"text": "to the Customize documentation.\\n\\nAlternatively, for the most comprehensive customizations, refer to our SDK functions here.\\n\\nIntegration code.\\n\\nTo get the PLuG chat widget to appear on your website and web app, copy and paste the snippet below on every page where you want the widget to appear for website visitors.\\n\\nUnique app ID.\\n\\nMake sure to replace the app ID with your app ID which identifies your PLuG chat widget. You can access your app ID from your DevRev account by following",
"title": "Install PLuG chat on your website"
},
{
"id": "ART-1466_KNOWLEDGE_NODE-23",
"text": "} ) ; 7 } , []) ; Check widget status.\\n\\nUse isWidgetOpen to determine whether your chat widget is currently open or closed.\\n\\n1 window. plugSDK. isWidgetOpen\\n\\nThis returns true if the chat widget is open and false if it is closed.\\n\\nStart conversation.\\n\\nThe startConversationContent method opens the PLuG widget directly to the conversation creation view. It replicates the action of clicking the Send us a message. button, launching the widget to the conversation initiation screen.\\n\\nThis",
"title": "Methods — DevRev | Docs"
},
{
"id": "ART-2059_KNOWLEDGE_NODE-8",
"text": "window.plugSDK.init({\\n3 // Please ensure you replace the app_id with your unique app id\\n4 app_id: \"<your_unique_app_id>\",\\n5 });\\n6 </ script >\\nSetup for React.\\n\\nPlace this in public/index.html file, inside the body tag of your HTML page.\\n\\n1 <script\\n2 type= \"text/javascript\"\\n3 src= \"https://plug-platform.devrev.ai/static/plug.js\"\\n4 ></script>;\\n\\nPlace this code inside the react component where you want to render the chat widget. Typically you should do it as top level component like",
"title": "Install PLuG chat on your website"
},
{
"id": "ART-15504_KNOWLEDGE_NODE-1",
"text": "is installed, the chat widget appears by default.\\n\\nGetting your unique app ID\\n--------------------------\\n\\nYou can access your app ID from your DevRev account by following these steps:\\n\\n1. In DevRev, go to **Settings > Support > Plug Settings** via the settings icon in the top-left corner.\\n2. If the Plug feature is not already enabled, click **Enable Plug**.\\n3. Under the **Configuration** tab, copy the **Unique App ID**.\\n\\n###### Setup\\n\\n###### Setup for React\\n\\nPlace the following",
"title": "Install the Web SDK | DevRev | Docs"
},
{
"id": "ART-2059_KNOWLEDGE_NODE-9",
"text": "App.js.\\n\\n1 useEffect ( () => {\\n2 window. plugSDK. init ({\\n3 // Please ensure you replace the app_id with your unique app id\\n4 app_id : \"<your_unique_app_id>\" ,\\n5 });\\n6 }, []);\\n\\nYou should now have PLuG chat widget installed on your website. Facing some issues? Reach out to us through our own PLuG chat widget from the bottom right of your screen.\\n\\nOnce the widget is installed on your website, every user who visits your website is considered an anonymous user. Anonymous users are the",
"title": "Install PLuG chat on your website"
},
{
"id": "ART-15509_KNOWLEDGE_NODE-11",
"text": "widget.\\n\\nPassing `true` opens the chat widget.\\n\\nPassing `false` closes the chat widget.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | window.plugSDK.toggleWidget(true); |\\n```\\n\\nCheck widget status\\n-------------------\\n\\nUse `isWidgetOpen` to determine whether your chat widget is currently open or closed.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | window.plugSDK.isWidgetOpen |\\n```\\n\\nThis returns `true` if the chat widget is open and `false` if it is closed.\\n\\nTake action from Plug chat",
"title": "Methods | DevRev | Docs"
},
{
"id": "ART-2897_KNOWLEDGE_NODE-15",
"text": "here \\n 5| } \\n 6| }); \\n 7| }, []);\\n[/code] \\n \\n## Start conversation\\n\\nThe `startConversationContent` method opens the PLuG widget directly to the conversation creation view. It replicates the action of clicking the **Send us a message** button, launching the widget to the conversation initiation screen.\\n\\nThis method also accepts an optional input parameter to pre-fill a message on the conversation creation screen, providing your users with a prompt to start a",
"title": "Methods — DevRev | Docs"
},
{
"id": "ART-1270_KNOWLEDGE_NODE-2",
"text": "{startConversationContent: \\'Hi\\',}); Start a conversation.\\n\\nplugSDK.prefillSearchQuery(query:\"string\") Prefill the search input of the search agent.\\n\\nInitialize chat.\\n\\nCalling the init() method initializes the PLuG chat widget on your website. Initializing the PLuG widget is necessary for you to perform any other actions on the PLuG widget SDK.\\n\\n1 useEffect ( () => { 2 window. plugSDK. init ( { 3 app_id : < your_unique_app_id > , 4 }); 5 }, []);\\n\\nWhen React is using Strict mode, you",
"title": "Methods — DevRev | Docs"
},
{
"id": "ART-1270_KNOWLEDGE_NODE-9",
"text": "utilized to open the PLuG widget with the conversation creation view activated. It essentially replicates the action of clicking the Send us a message. button, launching the widget directly to the conversation initiation screen.\\n\\nThe method also accepts an optional input parameter, allowing you to pre-fill a message in the conversation creation screen. This provides your users with a prompt to initiate a conversation with your team.\\n\\n1 plugSDK. toggleWidget ( true , \\' create_conversation",
"title": "Methods — DevRev | Docs"
},
{
"id": "ART-2059_KNOWLEDGE_NODE-5",
"text": "Jul 06 to Jul 19, 2023 Jun 20 to Jul 05, 2023 Jun 05 to Jun 19, 2023 May 22 to Jun 05, 2023 Apr 22 to May 22, 2023\\n\\nDeveloper DevRevU\\n\\nOn this page\\nIntegration code Unique app ID Setup for HTML Setup for React\\nInstall PLuG chat on your website.\\n\\nThere are two primary methods to customize PLuG chat. The easiest way is to do so through the app by navigating to Settings > Support > PLuG Settings > Configuration, Styling and Layout Tabs.. For detailed descriptions of the parameters, refer",
"title": "Install PLuG chat on your website"
},
{
"id": "ART-2897_KNOWLEDGE_NODE-12",
"text": "PLuG chat widget.\\n\\nPassing `true` opens the chat widget.\\n\\nPassing `false` closes the chat widget.\\n\\n[code]\\n\\n 1| window.plugSDK.toggleWidget(true); \\n ---|---\\n[/code] \\n \\n## Check widget status\\n\\nUse `isWidgetOpen` to determine whether your chat widget is currently open or closed.\\n\\n[code]\\n\\n 1| window.plugSDK.isWidgetOpen \\n ---|---\\n[/code] \\n \\nThis returns `true` if the chat widget is open and `false` if it is closed.\\n\\n## Take action from PLuG chat",
"title": "Methods — DevRev | Docs"
},
{
"id": "ART-2059_KNOWLEDGE_NODE-7",
"text": "these steps.\\n\\nIn DevRev, go to Settings. > Support. > PLuG Settings. through the settings icon in the top-left corner.\\nClick Enable PLuG Widget. if it isn\\'t already enabled.\\nCopy your Unique App ID. from the Configuration tab..\\nSetup for HTML.\\n\\nPlace this code in the head of your HTML page.\\n\\n1 //\\n2 < script\\n3 type = \"text/javascript\"\\n4 src = \"https://plug-platform.devrev.ai/static/plug.js\"\\n5 > </ script >\\n\\nPlace this code in the body of your HTML page.\\n\\n1 < script >\\n2",
"title": "Install PLuG chat on your website"
},
{
"id": "ART-2893_KNOWLEDGE_NODE-0",
"text": "b'[](/public/sdks/web/installation)\\n\\nPublic\\n\\nOn this page\\n\\n * [Getting your unique app ID](/public/sdks/web/installation#getting-your-unique-app-id)\\n\\n[SDKs](/public/sdks)[PLuG Web SDK](/public/sdks/web/installation)\\n\\n#\\n\\nInstall the Web SDK\\n\\nTo install the PLuG SDK on your website or web application, insert the code snippet provided below on every page where you want the SDK to be active. Once the SDK is installed, the chat widget appears by default.\\n\\n## Getting your unique app",
"title": "Install the Web SDK — DevRev | Docs"
},
{
"id": "ART-1270_KNOWLEDGE_NODE-1",
"text": "widget.\\n\\nplugSDK.initSearchAgent() Initialize PLuG search agent.\\n\\nplugSDK.shutdown() End the user session which is currently initialized in PLuG widget.\\n\\nplugSDK.toggleWidget() Open/close the chat widget.\\n\\nplugSDK.toggleSearchAgent() Open/close the search agent.\\n\\nplugSDK.onEvent() Perform specific actions based on the payload type received from the PLuG widget.\\n\\nplugSDK.toggleTheme(\\'light/dark\\') Toggle PLuG widget theme.\\n\\nplugSDK.toggleWidget(true, \\'create_conversation\\',",
"title": "Methods — DevRev | Docs"
},
{
"id": "ART-2893_KNOWLEDGE_NODE-4",
"text": "update their information.\\n\\n#####\\n\\nOnce the SDK is installed, the chat widget appears by default. If you are not using the PLuG SDK for support or chat-related flows, you can disable the chat widget by setting the `disable_plug_chat_window` input to `true`.\\n\\n[code]\\n\\n <script> \\n --- \\n window.plugSDK.init({ \\n app_id: \\'<your_unique_app_id>\\', \\n disable_plug_chat_window: true, \\n }); \\n </script>\\n[/code] \\n \\nTo ensure seamless",
"title": "Install the Web SDK — DevRev | Docs"
},
{
"id": "ART-15504_KNOWLEDGE_NODE-4",
"text": "[identify your customers](/sdks/web/user-identity) and update their information.\\n\\n##### \\n\\nOnce the SDK is installed, the chat widget appears by default. If you are not using the Plug SDK for support or chat-related flows, you can disable the chat widget by setting the `disable_plug_chat_window` input to `true`.\\n\\n```\\n| |\\n| --- |\\n| <script> |\\n| window.plugSDK.init({ |\\n| app_id: \\'<your_unique_app_id>\\', |\\n| disable_plug_chat_window: true, |\\n| }); |\\n| </script> |\\n```\\n\\nTo ensure",
"title": "Install the Web SDK | DevRev | Docs"
},
{
"id": "ART-1270_KNOWLEDGE_NODE-0",
"text": "b'Public\\nOn this page\\n\\nMethods Initialize chat Initialize search Shutdown the widget Open or close the widget Take actions from events Toggle theme Start conversation\\n\\nSDKs PLuG SDK Methods.\\n\\nOur PLuG widget SDK is a powerful tool to further enhance our widget on your website or application. With our SDK, you are empowered to create a dynamic and personalized user experience. Let\\xe2\\x80\\x99s get started.\\n\\nMethods.\\n\\nplugSDK.init() Initialize the PLuG chat",
"title": "Methods — DevRev | Docs"
},
{
"id": "ART-1466_KNOWLEDGE_NODE-21",
"text": "widget.\\n\\n1 window. plugSDK. toggleWidget ( true ) ; Take action from PLuG chat events.\\n\\nThis method allows you to listen for events from the PLuG widget. Below are the available values for PAYLOAD_TYPE.\\n\\nON_PLUG_WIDGET_CLOSED : Triggered when the PLuG widget is closed.\\nON_PLUG_WIDGET_OPENED : Triggered when the PLuG widget is opened.\\nON_PLUG_WIDGET_READY : Triggered when the PLuG widget is ready.\\nON_PLUG_WIDGET_UNREAD_COUNT_CHANGE : Triggered when the user receives a new message. You",
"title": "Methods — DevRev | Docs"
},
{
"id": "ART-10697_KNOWLEDGE_NODE-31",
"text": "boosting engagement and reducing repetitive inquiries. To enable Plug, go to **Settings > Portal Settings**, activate Plug widget, and **Save** and **Publish**.\\n\\n![]()\\xc2\\xa0For more information about *Support App*, refer to the following articles: \\xe2\\x80\\xa3 [Support snap-ins | Support](/docs/product/snapins-support) \\xe2\\x80\\xa3 [Support best practices | Support](/docs/product/support-bp) \\xe2\\x80\\xa3 [Support](/docs/product/support) \\xe2\\x80\\xa3",
"title": "February 2025 | Changelog | DevRev"
},
{
"id": "ART-15509_KNOWLEDGE_NODE-4",
"text": "5 | }, []); |\\n```\\n\\nThe `init()` method can accept multiple inputs, which are explained below:\\n\\n| Input parameter | Description | Values |\\n| --- | --- | --- |\\n| `app_id` | The unique identifier for your Plug SDK. This parameter is required. | String |\\n| `disable_plug_chat_window` | The chat widget is enabled by default. Use this option if you want to disable the chat widget. | Boolean (True or False) |\\n| `enable_default_launcher` | Show/hide the default Plug widget launcher. | Boolean",
"title": "Methods | DevRev | Docs"
},
{
"id": "ART-15509_KNOWLEDGE_NODE-14",
"text": "//Your logic goes here |\\n| 5 | } |\\n| 6 | }); |\\n| 7 | }, []); |\\n```\\n\\nStart conversation\\n------------------\\n\\nThe `startConversationContent` method opens the Plug widget directly to the conversation creation view. It replicates the action of clicking the **Send us a message** button, launching the widget to the conversation initiation screen.\\n\\nThis method also accepts an optional input parameter to pre-fill a message on the conversation creation screen, providing your users with a",
"title": "Methods | DevRev | Docs"
}
] |
0a3421b6-d6cb-443e-8039-34f5e0295281
|
feature request for deleting all or some part of a group of tickets
|
[
{
"id": "ART-2873_KNOWLEDGE_NODE-24",
"text": "[Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Bulk delete data](/docs/automations/bulk-delete)\\n\\nBulk delete data\\n================\\n\\nThe bulk delete data snap-in allows users to quickly delete multiple tickets, issues, accounts, or contacts in DevRev. By using a command-based approach and tag-based filtering, it ensures efficient data cleanup while maintaining reliability. Furthermore, access control options are included to prevent the feature from being misused.\\n\\nThe following",
"title": "Bulk delete data | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2873_KNOWLEDGE_NODE-28",
"text": "following command:\\n\\n```\\n```\\n1 /bulk_delete\\n```\\n```\\n\\nSelect the <data\\\\_type> among one of the following:\\n\\n* Tickets\\n* Issues\\n* Accounts\\n* Contacts\\n* Opportunities\\n* Articles\\n\\n1. After entering the command, select the object type you want to delete from the list. Tags linked to these objects will be displayed for confirmation.\\n2. The repurcussions of deletion will be informed to the user before they are allowed to confirm whether they wish to proceed with the deletion.\\n3. The",
"title": "Bulk delete data | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2873_KNOWLEDGE_NODE-27",
"text": "are displayed in the timeline, including successful and failed operations.\\n\\nHow to use bulk delete data\\n---------------------------\\n\\n![]()\\n\\nAccounts cannot be deleted unless all linked tickets are unlinked first.\\n\\n1. Add the **Bulk Delete Data** snap-in from the DevRev Marketplace to your environment.\\n2. Select the tags you want to use as filters for the data deletion. These tags will determine which items are eligible for deletion.\\n3. In the timeline of any object, type the",
"title": "Bulk delete data | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2873_KNOWLEDGE_NODE-25",
"text": "fields are mandatory:\\n\\n* **Tags**\\n* **Object Type**\\n\\n![]()\\n\\nDeleted data cannot be recovered.\\n\\n![]()\\n\\nIf items were imported via an active AirSync, the deletion will cause the sync to fail.\\n\\nFeatures\\n--------\\n\\n* **Command-based workflow:** Initiate deletions by using the /bulk\\\\_delete command in the timeline.\\n* **Tag-based filtering**: Only items matching the selected tags are deleted, providing precise control over the process.\\n* **Access Control**: Ensures only authorized",
"title": "Bulk delete data | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2873_KNOWLEDGE_NODE-26",
"text": "users can perform deletions, this can be defined in the configuration.\\n* **Confirmation prompts**: Ensures users explicitly confirm whether they want to proceed with deletions, minimizing accidental actions.\\n* **Parallel execution**: Deletions are performed concurrently, ensuring fast and efficient data processing.\\n* **Error handling**: Failed deletions are logged, and feedback is provided directly in the timeline for review.\\n* **User feedback**: Detailed summaries of the deletion process",
"title": "Bulk delete data | Automate | Snap-ins | DevRev"
},
{
"id": "ART-1824_KNOWLEDGE_NODE-446",
"text": "with any of the provided channels.\\nAllowed values: email plug slack twilio twilio_sms\\nticket.group string Optional\\nFilters for tickets belonging to specific groups.\\nticket.is_spam boolean Optional\\nFilters for tickets that are spam.\\nticket.needs_response boolean Optional\\nFilters for tickets that need response.\\nticket.rev_org string Optional\\nFilters for tickets that are associated with any of the provided Rev organizations.\\nticket.severity enum Optional\\nFilters for tickets with any of",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1981_KNOWLEDGE_NODE-10",
"text": "- [Bulk delete data](/docs/automations/bulk-delete)\\n - [Bulk work item uploader](/docs/automations/bulk-upload)\\n - [Commands surface expander](/docs/automations/commands-surface-expander)\\n - [Convergence](/docs/automations/converge)\\n - [Conversation reminder](/docs/automations/conversation-reminder)\\n - [CSAT on conversation](/docs/automations/csat-conv)\\n - [CSAT on ticket](/docs/automations/csat-tickets)\\n - [CSV work item",
"title": "Support best practices | Computer for Support Teams | DevRev"
}
] |
f8e4c82d-215a-48a5-b9b0-c0d2b2a201b6
|
email notification trigger when viewed
|
[
{
"id": "ART-1954_KNOWLEDGE_NODE-31",
"text": "Trigger a badge and bell sound on the **Updates** page.\\n* Show a toast notification in the app.\\n\\n**Other notifications**:\\n\\n* Sent only in-app to reduce noise.\\n\\n### Email and push notifications\\n\\n* Email notifications: Sent after a five-minute delay if the notification is unread.\\n* Push notifications: Sent immediately and marked as stale if read on the web.\\n\\nBy using these features, DevRev helps you efficiently manage updates, focus on critical tasks, and maintain a streamlined",
"title": "Updates | Computer by DevRev | DevRev"
}
] |
923f14c3-417e-414d-9cc1-bae37d9290fe
|
Fix Versions variable in workflow steps Ask AI or regexp search
|
[
{
"id": "ART-17231_KNOWLEDGE_NODE-100",
"text": "(collection)\\xe2\\x86\\x92[#category:user] | \\xe2\\x9c\\x94\\xef\\xb8\\x8e | User IDs of the users that own the work |\\n| `priority` | enum | \\xe2\\x9c\\x94\\xef\\xb8\\x8e | Priority of the work based upon impact and criticality |\\n| `release_version_ids` | reference (collection)\\xe2\\x86\\x92[#record:version] | | Versions that will contain the resolving commit IDs |\\n| `reported_by_ids` | reference (collection)\\xe2\\x86\\x92[#category:user] | | User IDs of the users that reported the work |\\n| `rev_org_ids`",
"title": "Supported DevRev object types | DevRev | Docs"
}
] |
9922c4f8-6283-492d-b41a-b250e24e3014
|
reported by field multiple values retrieved
|
[
{
"id": "ART-16264_KNOWLEDGE_NODE-29",
"text": "account.\\n + If both **Reported By** and **Account** fields are initially empty, you can search for and add any contact to the **Reported By** field, which will auto-fill the **Account** and **Workspace** (if applicable).\\n* **Handling multiple users:**\\n\\n + If all selected users within the **Reported By** field belong to the same workspace, the **Workspace** field remains unchanged.\\n + If users are from different workspaces, the **Workspace** field is emptied, while the **Account** field",
"title": "June 2025 | Changelog | DevRev"
},
{
"id": "ART-1979_KNOWLEDGE_NODE-31",
"text": "from an email thread containing multiple customer email IDs, multiple reporters may be added. If a DevRev user adds a new customer while responding from DevRev, or if a new customer responds to the email thread, these new customers are added to the **Reported by** field. In the case of the Portal, there is only one **Reported by**, representing the person who has logged in to the portal to report the issue. Additional reporters can be added from the DevRev app. To select a contact in the",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-1979_KNOWLEDGE_NODE-32",
"text": "**Reported by** field, first choose the corresponding account and workspace in the **Customer** attribute. After this selection, the contact's name will appear in the **Reported by** list.\\n* **Email members**: Participants in the ongoing email thread, dependent on the last email. This attribute automatically updates based on the last email sent from or received on DevRev.\\n\\n![]()\\n\\nAdding members to **Email members** also adds them to the **Reported by** field. Removing members from **Email",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-1330_KNOWLEDGE_NODE-0",
"text": "b\"The Airdrop algorithm for populating reported_by field on tickets:\\n\\nCheck the reported by list:\\n\\nRemember if there are any revusers. If there are, remember the first revorg encountered (let's call it revOrgA).\\n\\nRemember if there are any devusers.\\n\\nCheck the revorg specified in the ticket, let's call it revOrgB.\\n\\nDo one of the following:\\n\\nIf there is a revOrgA then set it in the ticket (overwriting revOrgB) and remove any user that does not belong to it (i.e. revusers from",
"title": "How Airdrop populates reported_by on tickets"
},
{
"id": "ART-1438_KNOWLEDGE_NODE-7",
"text": "74| } \\n 75| ], \\n 76| \"reported_by\": [ \\n 77| { \\n 78| \"display_id\": \"foo\", \\n 79| \"id\": \"foo\", \\n 80| \"display_name\": \"foo\", \\n 81| \"display_picture\": { \\n 82| \"display_id\": \"foo\", \\n 83| \"id\": \"foo\", \\n 84| \"file\": {} \\n 85| }, \\n 86| \"email\": \"foo\", \\n 87| \"full_name\": \"foo\", \\n 88| \"state\": \"active\" \\n 89| }",
"title": "Create Work — DevRev | Docs"
},
{
"id": "ART-1446_KNOWLEDGE_NODE-8",
"text": "], \\n 76| \"reported_by\": [ \\n 77| { \\n 78| \"display_id\": \"foo\", \\n 79| \"id\": \"foo\", \\n 80| \"display_name\": \"foo\", \\n 81| \"display_picture\": { \\n 82| \"display_id\": \"foo\", \\n 83| \"id\": \"foo\", \\n 84| \"file\": {} \\n 85| }, \\n 86| \"email\": \"foo\", \\n 87| \"full_name\": \"foo\", \\n 88| \"state\": \"active\" \\n 89| } \\n 90| ], \\n 91|",
"title": "Update Work — DevRev | Docs"
},
{
"id": "ART-1641_KNOWLEDGE_NODE-454",
"text": "display_picture \" : { 82 \" display_id \" : \" string \" , 83 \" id \" : \" string \" 84 } , 85 \" email \" : \" string \" , 86 \" full_name \" : \" string \" , 87 \" state \" : \" active \" , 88 \" display_id \" : \" string \" , 89 \" id \" : \" string \" 90 } 91 ] , 92 \" reported_by \" : [ 93 { 94 \" type \" : \" dev_user \" , 95 \" display_name \" : \" string \" , 96 \" display_picture \" : { 97 \" display_id \" : \" string \" , 98 \" id \" : \" string \" 99 } , 100 \" email \" : \" string \" , 101 \" full_name \" : \" string \" , 102 \" state \"",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1456_KNOWLEDGE_NODE-12",
"text": "\"display_picture\": {}, \\n 60| \"email\": \"foo\", \\n 61| \"full_name\": \"foo\", \\n 62| \"state\": \"active\" \\n 63| } \\n 64| ], \\n 65| \"reported_by\": [ \\n 66| { \\n 67| \"display_id\": \"foo\", \\n 68| \"id\": \"foo\", \\n 69| \"display_name\": \"foo\", \\n 70| \"display_picture\": {}, \\n 71| \"email\": \"foo\", \\n 72| \"full_name\": \"foo\", \\n 73|",
"title": "List Works (POST) — DevRev | Docs"
},
{
"id": "ART-1655_KNOWLEDGE_NODE-470",
"text": "custom_fields \" : { 72 \" string \" : {} 73 } , 74 \" custom_schema_fragments \" : [ 75 \" string \" 76 ] , 77 \" owned_by \" : [ 78 { 79 \" type \" : \" dev_user \" , 80 \" display_name \" : \" string \" , 81 \" display_picture \" : { 82 \" display_id \" : \" string \" , 83 \" id \" : \" string \" 84 } , 85 \" email \" : \" string \" , 86 \" full_name \" : \" string \" , 87 \" state \" : \" active \" , 88 \" display_id \" : \" string \" , 89 \" id \" : \" string \" 90 } 91 ] , 92 \" reported_by \" : [ 93 { 94 \" type \" : \" dev_user \" , 95 \"",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-17228_KNOWLEDGE_NODE-6",
"text": "be a collection instead.\\nThe natural format of a collection is a JSON array (or `null`), containing the natural format of its elements.\\nFor example:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"reporter_ids\": [ |\\n| 3 | { |\\n| 4 | \"ref_type\": \"user\", |\\n| 5 | \"id\": \"2103232131\", |\\n| 6 | \"fallback_record_name\": \"John Doe\" |\\n| 7 | }, |\\n| 8 | { |\\n| 9 | \"ref_type\": \"contact\", |\\n| 10 | \"id\": \"2103232144\", |\\n| 11 | \"fallback_record_name\": \"Jane Doe\" |\\n| 12 | } |\\n| 13 | ], |\\n| 14 |",
"title": "Common issues | DevRev | Docs"
},
{
"id": "ART-1653_KNOWLEDGE_NODE-454",
"text": "\" : \" string \" , 71 \" custom_fields \" : { 72 \" string \" : {} 73 } , 74 \" custom_schema_fragments \" : [ 75 \" string \" 76 ] , 77 \" owned_by \" : [ 78 { 79 \" type \" : \" dev_user \" , 80 \" display_name \" : \" string \" , 81 \" display_picture \" : { 82 \" display_id \" : \" string \" , 83 \" id \" : \" string \" 84 } , 85 \" email \" : \" string \" , 86 \" full_name \" : \" string \" , 87 \" state \" : \" active \" , 88 \" display_id \" : \" string \" , 89 \" id \" : \" string \" 90 } 91 ] , 92 \" reported_by \" : [ 93 { 94 \" type \"",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1641_KNOWLEDGE_NODE-463",
"text": "string \" 84 } , 85 \" email \" : \" string \" , 86 \" full_name \" : \" string \" , 87 \" state \" : \" active \" , 88 \" display_id \" : \" string \" , 89 \" id \" : \" string \" 90 } 91 ] , 92 \" reported_by \" : [ 93 { 94 \" type \" : \" dev_user \" , 95 \" display_name \" : \" string \" , 96 \" display_picture \" : { 97 \" display_id \" : \" string \" , 98 \" id \" : \" string \" 99 } , 100 \" email \" : \" string \" , 101 \" full_name \" : \" string \" , 102 \" state \" : \" active \" , 103 \" display_id \" : \" string \" , 104 \" id \" : \"",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1440_KNOWLEDGE_NODE-15",
"text": "\\n 58| \"display_name\": \"foo\", \\n 59| \"display_picture\": {}, \\n 60| \"email\": \"foo\", \\n 61| \"full_name\": \"foo\", \\n 62| \"state\": \"active\" \\n 63| } \\n 64| ], \\n 65| \"reported_by\": [ \\n 66| { \\n 67| \"display_id\": \"foo\", \\n 68| \"id\": \"foo\", \\n 69| \"display_name\": \"foo\", \\n 70| \"display_picture\": {}, \\n 71| \"email\":",
"title": "Export Works — DevRev | Docs"
},
{
"id": "ART-1452_KNOWLEDGE_NODE-10",
"text": "\"id\": \"foo\", \\n 58| \"display_name\": \"foo\", \\n 59| \"display_picture\": {}, \\n 60| \"email\": \"foo\", \\n 61| \"full_name\": \"foo\", \\n 62| \"state\": \"active\" \\n 63| } \\n 64| ], \\n 65| \"reported_by\": [ \\n 66| { \\n 67| \"display_id\": \"foo\", \\n 68| \"id\": \"foo\", \\n 69| \"display_name\": \"foo\", \\n 70| \"display_picture\": {}, \\n 71|",
"title": "Export Works (POST) — DevRev | Docs"
},
{
"id": "ART-4132_KNOWLEDGE_NODE-10",
"text": "170 | \"origin_system\": \"string\" |\\n| 171 | }, |\\n| 172 | \"title\": \"string\" |\\n| 173 | } |\\n| 174 | ], |\\n| 175 | \"reported_by\": { |\\n| 176 | \"id\": 1, |\\n| 177 | \"label\": \"string\", |\\n| 178 | \"ordinal\": 1, |\\n| 179 | \"value\": null |\\n| 180 | }, |\\n| 181 | \"severity\": { |\\n| 182 | \"id\": 1, |\\n| 183 | \"label\": \"string\", |\\n| 184 | \"ordinal\": 1, |\\n| 185 | \"value\": null |\\n| 186 | }, |\\n| 187 | \"source\": { |\\n| 188 | \"id\": 1, |\\n| 189 | \"label\": \"string\", |\\n| 190 | \"ordinal\": 1, |\\n| 191 |",
"title": "List Incidents | DevRev | Docs"
},
{
"id": "ART-1361_KNOWLEDGE_NODE-5",
"text": "\"display_picture\": { |\\n| 75 | \"display_id\": \"string\", |\\n| 76 | \"id\": \"string\", |\\n| 77 | \"file\": { |\\n| 78 | \"type\": \"string\", |\\n| 79 | \"name\": \"string\", |\\n| 80 | \"size\": 1 |\\n| 81 | } |\\n| 82 | }, |\\n| 83 | \"email\": \"string\", |\\n| 84 | \"full_name\": \"string\", |\\n| 85 | \"state\": \"active\" |\\n| 86 | } |\\n| 87 | ], |\\n| 88 | \"reported_by\": [ |\\n| 89 | { |\\n| 90 | \"display_id\": \"string\", |\\n| 91 | \"id\": \"string\", |\\n| 92 | \"display_name\": \"string\", |\\n| 93 | \"display_picture\": { |\\n| 94 |",
"title": "Create Work | DevRev | Docs"
},
{
"id": "ART-1250_KNOWLEDGE_NODE-5",
"text": "\"display_picture\": { |\\n| 75 | \"display_id\": \"string\", |\\n| 76 | \"id\": \"string\", |\\n| 77 | \"file\": { |\\n| 78 | \"type\": \"string\", |\\n| 79 | \"name\": \"string\", |\\n| 80 | \"size\": 1 |\\n| 81 | } |\\n| 82 | }, |\\n| 83 | \"email\": \"string\", |\\n| 84 | \"full_name\": \"string\", |\\n| 85 | \"state\": \"active\" |\\n| 86 | } |\\n| 87 | ], |\\n| 88 | \"reported_by\": [ |\\n| 89 | { |\\n| 90 | \"display_id\": \"string\", |\\n| 91 | \"id\": \"string\", |\\n| 92 | \"display_name\": \"string\", |\\n| 93 | \"display_picture\": { |\\n| 94 |",
"title": "Update Work | DevRev | Docs"
},
{
"id": "ART-4129_KNOWLEDGE_NODE-21",
"text": "related docs.\\n\\nreported\\\\_bylist of longsOptional\\n\\nFilters for incidents with any of the provided reporters.\\n\\nseveritylist of longsOptional\\n\\nFilters for incidents containing any of the provided severities.\\n\\nsort\\\\_bylist of stringsOptional\\n\\nComma-separated fields to sort the incidents by.\\n\\nstagelist of stringsOptional\\n\\nFilters for incidents in any of the provided stages.\\n\\nstaged\\\\_infoobjectOptional\\n\\nShow 1 properties\\n\\nsubtypelist of stringsOptional\\n\\nFilters for",
"title": "Group Incidents (POST) | DevRev | Docs"
},
{
"id": "ART-1654_KNOWLEDGE_NODE-455",
"text": "87 \" state \" : \" active \" , 88 \" display_id \" : \" string \" , 89 \" id \" : \" string \" 90 } 91 ] , 92 \" reported_by \" : [ 93 { 94 \" type \" : \" dev_user \" , 95 \" display_name \" : \" string \" , 96 \" display_picture \" : { 97 \" display_id \" : \" string \" , 98 \" id \" : \" string \" 99 } , 100 \" email \" : \" string \" , 101 \" full_name \" : \" string \" , 102 \" state \" : \" active \" , 103 \" display_id \" : \" string \" , 104 \" id \" : \" string \" 105 } 106 ] , 107 \" stage \" : { 108 \" name \" : \" string \" , 109 \" notes",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1246_KNOWLEDGE_NODE-5",
"text": "| \"id\": \"string\", |\\n| 77 | \"file\": { |\\n| 78 | \"type\": \"string\", |\\n| 79 | \"name\": \"string\", |\\n| 80 | \"size\": 1 |\\n| 81 | } |\\n| 82 | }, |\\n| 83 | \"email\": \"string\", |\\n| 84 | \"full_name\": \"string\", |\\n| 85 | \"state\": \"active\" |\\n| 86 | } |\\n| 87 | ], |\\n| 88 | \"reported_by\": [ |\\n| 89 | { |\\n| 90 | \"display_id\": \"string\", |\\n| 91 | \"id\": \"string\", |\\n| 92 | \"display_name\": \"string\", |\\n| 93 | \"display_picture\": { |\\n| 94 | \"display_id\": \"string\", |\\n| 95 | \"id\": \"string\", |\\n| 96 | \"file\": {",
"title": "Get Work | DevRev | Docs"
},
{
"id": "ART-1442_KNOWLEDGE_NODE-7",
"text": "\"display_name\": \"foo\", \\n 66| \"display_picture\": { \\n 67| \"display_id\": \"foo\", \\n 68| \"id\": \"foo\", \\n 69| \"file\": {} \\n 70| }, \\n 71| \"email\": \"foo\", \\n 72| \"full_name\": \"foo\", \\n 73| \"state\": \"active\" \\n 74| } \\n 75| ], \\n 76| \"reported_by\": [ \\n 77| { \\n 78| \"display_id\": \"foo\", \\n 79| \"id\": \"foo\", \\n 80| \"display_name\":",
"title": "Get Work — DevRev | Docs"
},
{
"id": "ART-16355_KNOWLEDGE_NODE-26",
"text": "**Reported\\\\_by,** and **Contact** columns, provide the email of the person to be assigned as the owner or reporter of the work item. If the CSV lists multiple owners, only the first will be set as the owner.\\n* For the **Applies to Part**, **Stage**, **Account**, **Developed with Parts**, and **Tags** columns, provide the part name, stage name, account name, part name, and tag name respectively as it is present in the UI, ensuring case sensitivity.\\n* For **Date** and **Timestamp** related",
"title": "CSV commands uploader | Automate | Snap-ins | DevRev"
},
{
"id": "ART-17231_KNOWLEDGE_NODE-126",
"text": "deal, value lies between 0.0% and 100.0% |\\n| `reported_by_ids` | reference (collection)\\xe2\\x86\\x92[#category:user] | | User IDs of the users that reported the work |\\n| `stage` | enum | \\xe2\\x9c\\x94\\xef\\xb8\\x8e | Stage of the object |\\n| `tags` | reference (collection)\\xe2\\x86\\x92[#record:tag] | | Tags associated with the object |\\n| `target_close_date` | timestamp | | Timestamp when the work is expected to be complete |\\n| `title` | text | \\xe2\\x9c\\x94\\xef\\xb8\\x8e | Title of the work",
"title": "Supported DevRev object types | DevRev | Docs"
},
{
"id": "ART-1651_KNOWLEDGE_NODE-443",
"text": "76 ] , 77 \" owned_by \" : [ 78 { 79 \" type \" : \" dev_user \" , 80 \" display_name \" : \" string \" , 81 \" display_picture \" : { 82 \" display_id \" : \" string \" , 83 \" id \" : \" string \" 84 } , 85 \" email \" : \" string \" , 86 \" full_name \" : \" string \" , 87 \" state \" : \" active \" , 88 \" display_id \" : \" string \" , 89 \" id \" : \" string \" 90 } 91 ] , 92 \" reported_by \" : [ 93 { 94 \" type \" : \" dev_user \" , 95 \" display_name \" : \" string \" , 96 \" display_picture \" : { 97 \" display_id \" : \" string \" , 98 \"",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1454_KNOWLEDGE_NODE-6",
"text": "\"display_id\": \"foo\", \\n 64| \"id\": \"foo\", \\n 65| \"display_name\": \"foo\", \\n 66| \"display_picture\": { \\n 67| \"display_id\": \"foo\", \\n 68| \"id\": \"foo\", \\n 69| \"file\": {} \\n 70| }, \\n 71| \"email\": \"foo\", \\n 72| \"full_name\": \"foo\", \\n 73| \"state\": \"active\" \\n 74| } \\n 75| ], \\n 76| \"reported_by\": [ \\n 77| { \\n 78| \"display_id\":",
"title": "Get Work (POST) — DevRev | Docs"
},
{
"id": "ART-1835_KNOWLEDGE_NODE-451",
"text": "custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue object Optional\\nShow 9 properties\\nmodified_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\nopportunity object Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1836_KNOWLEDGE_NODE-451",
"text": "custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue object Optional\\nShow 9 properties\\nmodified_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\nopportunity object Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1837_KNOWLEDGE_NODE-450",
"text": "custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue object Optional\\nShow 9 properties\\nmodified_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\nopportunity object Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1649_KNOWLEDGE_NODE-458",
"text": "custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue object Optional\\nShow 9 properties\\nmodified_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\nopportunity object Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1245_KNOWLEDGE_NODE-5",
"text": "\"display_name\": \"string\", |\\n| 75 | \"display_picture\": { |\\n| 76 | \"display_id\": \"string\", |\\n| 77 | \"id\": \"string\", |\\n| 78 | \"file\": { |\\n| 79 | \"type\": \"string\", |\\n| 80 | \"name\": \"string\", |\\n| 81 | \"size\": 1 |\\n| 82 | } |\\n| 83 | }, |\\n| 84 | \"email\": \"string\", |\\n| 85 | \"full_name\": \"string\", |\\n| 86 | \"state\": \"active\" |\\n| 87 | } |\\n| 88 | ], |\\n| 89 | \"reported_by\": [ |\\n| 90 | { |\\n| 91 | \"display_id\": \"string\", |\\n| 92 | \"id\": \"string\", |\\n| 93 | \"display_name\": \"string\", |\\n| 94 |",
"title": "Export Works (POST) | DevRev | Docs"
},
{
"id": "ART-1247_KNOWLEDGE_NODE-5",
"text": "\"display_name\": \"string\", |\\n| 74 | \"display_picture\": { |\\n| 75 | \"display_id\": \"string\", |\\n| 76 | \"id\": \"string\", |\\n| 77 | \"file\": { |\\n| 78 | \"type\": \"string\", |\\n| 79 | \"name\": \"string\", |\\n| 80 | \"size\": 1 |\\n| 81 | } |\\n| 82 | }, |\\n| 83 | \"email\": \"string\", |\\n| 84 | \"full_name\": \"string\", |\\n| 85 | \"state\": \"active\" |\\n| 86 | } |\\n| 87 | ], |\\n| 88 | \"reported_by\": [ |\\n| 89 | { |\\n| 90 | \"display_id\": \"string\", |\\n| 91 | \"id\": \"string\", |\\n| 92 | \"display_name\": \"string\", |\\n| 93 |",
"title": "Get Work (POST) | DevRev | Docs"
},
{
"id": "ART-1249_KNOWLEDGE_NODE-5",
"text": "\"display_name\": \"string\", |\\n| 75 | \"display_picture\": { |\\n| 76 | \"display_id\": \"string\", |\\n| 77 | \"id\": \"string\", |\\n| 78 | \"file\": { |\\n| 79 | \"type\": \"string\", |\\n| 80 | \"name\": \"string\", |\\n| 81 | \"size\": 1 |\\n| 82 | } |\\n| 83 | }, |\\n| 84 | \"email\": \"string\", |\\n| 85 | \"full_name\": \"string\", |\\n| 86 | \"state\": \"active\" |\\n| 87 | } |\\n| 88 | ], |\\n| 89 | \"reported_by\": [ |\\n| 90 | { |\\n| 91 | \"display_id\": \"string\", |\\n| 92 | \"id\": \"string\", |\\n| 93 | \"display_name\": \"string\", |\\n| 94 |",
"title": "List Works (POST) | DevRev | Docs"
},
{
"id": "ART-4126_KNOWLEDGE_NODE-10",
"text": "\"string\" |\\n| 166 | }, |\\n| 167 | \"sync_metadata\": { |\\n| 168 | \"external_reference\": \"string\", |\\n| 169 | \"origin_system\": \"string\" |\\n| 170 | }, |\\n| 171 | \"title\": \"string\" |\\n| 172 | } |\\n| 173 | ], |\\n| 174 | \"reported_by\": { |\\n| 175 | \"id\": 1, |\\n| 176 | \"label\": \"string\", |\\n| 177 | \"ordinal\": 1, |\\n| 178 | \"value\": null |\\n| 179 | }, |\\n| 180 | \"severity\": { |\\n| 181 | \"id\": 1, |\\n| 182 | \"label\": \"string\", |\\n| 183 | \"ordinal\": 1, |\\n| 184 | \"value\": null |\\n| 185 | }, |\\n| 186 |",
"title": "Get Incident (POST) | DevRev | Docs"
},
{
"id": "ART-1637_KNOWLEDGE_NODE-442",
"text": "87 \" state \" : \" active \" , 88 \" display_id \" : \" string \" , 89 \" id \" : \" string \" 90 } 91 ] , 92 \" reported_by \" : [ 93 { 94 \" type \" : \" dev_user \" , 95 \" display_name \" : \" string \" , 96 \" display_picture \" : { 97 \" display_id \" : \" string \" , 98 \" id \" : \" string \" 99 } , 100 \" email \" : \" string \" , 101 \" full_name \" : \" string \" , 102 \" state \" : \" active \" , 103 \" display_id \" : \" string \" , 104 \" id \" : \" string \" 105 } 106 ] , 107 \" stage \" : { 108 \" name \" : \" string \" , 109 \" notes",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1639_KNOWLEDGE_NODE-455",
"text": "reported by any of these users.\\nsort_by string Optional\\nFields to sort the works by and the direction to sort them.\\nstage.name string Optional\\nFilters for records in the provided stage(s) by name.\\nstaged_info.is_staged boolean Optional\\nFilters for issues that are staged.\\nsync_metadata.external_reference string Optional\\nFilters for issues with this specific external reference.\\nsync_metadata.last_sync_in.status enum Optional\\nFilters for works with selected sync statuses.\\nAllowed",
"title": "Export Post — DevRev | Docs"
},
{
"id": "ART-1779_KNOWLEDGE_NODE-451",
"text": "2 variants\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue object Optional\\nShow 9 properties\\nmodified_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\nopportunity object Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1248_KNOWLEDGE_NODE-5",
"text": "\"string\", |\\n| 77 | \"id\": \"string\", |\\n| 78 | \"file\": { |\\n| 79 | \"type\": \"string\", |\\n| 80 | \"name\": \"string\", |\\n| 81 | \"size\": 1 |\\n| 82 | } |\\n| 83 | }, |\\n| 84 | \"email\": \"string\", |\\n| 85 | \"full_name\": \"string\", |\\n| 86 | \"state\": \"active\" |\\n| 87 | } |\\n| 88 | ], |\\n| 89 | \"reported_by\": [ |\\n| 90 | { |\\n| 91 | \"display_id\": \"string\", |\\n| 92 | \"id\": \"string\", |\\n| 93 | \"display_name\": \"string\", |\\n| 94 | \"display_picture\": { |\\n| 95 | \"display_id\": \"string\", |\\n| 96 | \"id\": \"string\",",
"title": "List Works | DevRev | Docs"
},
{
"id": "ART-1244_KNOWLEDGE_NODE-5",
"text": "\"string\", |\\n| 77 | \"id\": \"string\", |\\n| 78 | \"file\": { |\\n| 79 | \"type\": \"string\", |\\n| 80 | \"name\": \"string\", |\\n| 81 | \"size\": 1 |\\n| 82 | } |\\n| 83 | }, |\\n| 84 | \"email\": \"string\", |\\n| 85 | \"full_name\": \"string\", |\\n| 86 | \"state\": \"active\" |\\n| 87 | } |\\n| 88 | ], |\\n| 89 | \"reported_by\": [ |\\n| 90 | { |\\n| 91 | \"display_id\": \"string\", |\\n| 92 | \"id\": \"string\", |\\n| 93 | \"display_name\": \"string\", |\\n| 94 | \"display_picture\": { |\\n| 95 | \"display_id\": \"string\", |\\n| 96 | \"id\": \"string\",",
"title": "Export Works | DevRev | Docs"
},
{
"id": "ART-1652_KNOWLEDGE_NODE-448",
"text": "any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue object Optional\\nShow 9 properties\\nmodified_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\nopportunity object Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-17228_KNOWLEDGE_NODE-7",
"text": "\"tags\": [\"bug\", \"good-first-issue\"] |\\n| 15 | } |\\n```\\n\\nSome systems provide collections as enum values or references in a string, separated by some separator (comma or semicolon):\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"reporter_ids\": \"2103232131,2103232144\", |\\n| 3 | \"tags\": \"bug;good-first-issue\" |\\n| 4 | } |\\n```\\n\\nThis format should be avoided, and the data normalized to the natural format in the extractor.\\n\\n###### Using struct fields\\n\\nStructs are embedded JSON objects",
"title": "Common issues | DevRev | Docs"
},
{
"id": "ART-1790_KNOWLEDGE_NODE-450",
"text": "2 variants\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue object Optional\\nShow 9 properties\\nmodified_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\nopportunity object Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1308_KNOWLEDGE_NODE-452",
"text": "2 variants\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue object Optional\\nShow 9 properties\\nmodified_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\nopportunity object Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1301_KNOWLEDGE_NODE-455",
"text": "2 variants\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue object Optional\\nShow 9 properties\\nmodified_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\nopportunity object Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1802_KNOWLEDGE_NODE-455",
"text": "2 variants\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue object Optional\\nShow 9 properties\\nmodified_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\nopportunity object Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1605_KNOWLEDGE_NODE-451",
"text": "2 variants\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue object Optional\\nShow 9 properties\\nmodified_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\nopportunity object Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1780_KNOWLEDGE_NODE-450",
"text": "2 variants\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue object Optional\\nShow 9 properties\\nmodified_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\nopportunity object Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1784_KNOWLEDGE_NODE-449",
"text": "2 variants\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue object Optional\\nShow 9 properties\\nmodified_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\nopportunity object Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings",
"title": "Locate Post — DevRev | Docs"
},
{
"id": "ART-1832_KNOWLEDGE_NODE-458",
"text": "2 variants\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue object Optional\\nShow 9 properties\\nmodified_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\nopportunity object Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1444_KNOWLEDGE_NODE-15",
"text": "\"body\": \"foo\", \\n 54| \"owned_by\": [ \\n 55| { \\n 56| \"display_id\": \"foo\", \\n 57| \"id\": \"foo\", \\n 58| \"display_name\": \"foo\", \\n 59| \"display_picture\": {}, \\n 60| \"email\": \"foo\", \\n 61| \"full_name\": \"foo\", \\n 62| \"state\": \"active\" \\n 63| } \\n 64| ], \\n 65| \"reported_by\": [ \\n 66| { \\n 67| \"display_id\": \"foo\", \\n 68|",
"title": "List Works — DevRev | Docs"
},
{
"id": "ART-1783_KNOWLEDGE_NODE-449",
"text": "2 variants\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue object Optional\\nShow 9 properties\\nmodified_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\nopportunity object Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings",
"title": "Locate — DevRev | Docs"
},
{
"id": "ART-1819_KNOWLEDGE_NODE-453",
"text": "2 variants\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue object Optional\\nShow 9 properties\\nmodified_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\nopportunity object Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings",
"title": "Sla Trackers Get — DevRev | Docs"
},
{
"id": "ART-1653_KNOWLEDGE_NODE-463",
"text": ": {} 73 } , 74 \" custom_schema_fragments \" : [ 75 \" string \" 76 ] , 77 \" owned_by \" : [ 78 { 79 \" type \" : \" dev_user \" , 80 \" display_name \" : \" string \" , 81 \" display_picture \" : { 82 \" display_id \" : \" string \" , 83 \" id \" : \" string \" 84 } , 85 \" email \" : \" string \" , 86 \" full_name \" : \" string \" , 87 \" state \" : \" active \" , 88 \" display_id \" : \" string \" , 89 \" id \" : \" string \" 90 } 91 ] , 92 \" reported_by \" : [ 93 { 94 \" type \" : \" dev_user \" , 95 \" display_name \" : \" string \" , 96 \"",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1804_KNOWLEDGE_NODE-455",
"text": "2 variants\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue object Optional\\nShow 9 properties\\nmodified_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\nopportunity object Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings",
"title": "Self — DevRev | Docs"
},
{
"id": "ART-1304_KNOWLEDGE_NODE-454",
"text": "2 variants\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue object Optional\\nShow 9 properties\\nmodified_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\nopportunity object Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1806_KNOWLEDGE_NODE-455",
"text": "2 variants\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue object Optional\\nShow 9 properties\\nmodified_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\nopportunity object Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings",
"title": "Self Post — DevRev | Docs"
},
{
"id": "ART-1590_KNOWLEDGE_NODE-468",
"text": "any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow property\\nstaged_info object Optional\\nShow property\\nsync_metadata object Optional\\nShow 4 properties\\ntags list of strings Optional\\nFilters for work with any of the provided tags.\\ntarget_close_date object Optional\\nProvides ways to specify",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1592_KNOWLEDGE_NODE-452",
"text": "2 variants\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue object Optional\\nShow 9 properties\\nmodified_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\nopportunity object Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1595_KNOWLEDGE_NODE-467",
"text": "any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow property\\nstaged_info object Optional\\nShow property\\nsync_metadata object Optional\\nShow 4 properties\\ntags list of strings Optional\\nFilters for work with any of the provided tags.\\ntarget_close_date object Optional\\nProvides ways to specify",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1302_KNOWLEDGE_NODE-455",
"text": "2 variants\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue object Optional\\nShow 9 properties\\nmodified_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\nopportunity object Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1959_KNOWLEDGE_NODE-31",
"text": "<field\\\\_name>:>=<v> | revenue:<100 revenue:500..2000 discount>=0.25 tickets=< 5 |\\n| String fields | <field\\\\_name>:<v> | Name:alice Name:Alice,bob,eve |\\n| Date fields | <field\\\\_name>:<v> <field\\\\_name>:<=<v> <field\\\\_name>:v1..v2 <field\\\\_name>:><v> <field\\\\_name>:>=<v> <field\\\\_name>:<<v> | target\\\\_release\\\\_date:<2020-10 target\\\\_release\\\\_date:<2020 |\\n| Array fields | <field\\\\_name>:<v> Here <v> is a CSV list of values where a match occurs if the array field",
"title": "Search | Computer by DevRev | DevRev"
},
{
"id": "ART-1788_KNOWLEDGE_NODE-467",
"text": "any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow property\\nstaged_info object Optional\\nShow property\\nsync_metadata object Optional\\nShow 4 properties\\ntags list of strings Optional\\nFilters for work with any of the provided tags.\\ntarget_close_date object Optional\\nProvides ways to specify",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1792_KNOWLEDGE_NODE-453",
"text": "2 variants\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue object Optional\\nShow 9 properties\\nmodified_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\nopportunity object Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1803_KNOWLEDGE_NODE-468",
"text": "any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow property\\nstaged_info object Optional\\nShow property\\nsync_metadata object Optional\\nShow 4 properties\\ntags list of strings Optional\\nFilters for work with any of the provided tags.\\ntarget_close_date object Optional\\nProvides ways to specify",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1801_KNOWLEDGE_NODE-469",
"text": "any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow property\\nstaged_info object Optional\\nShow property\\nsync_metadata object Optional\\nShow 4 properties\\ntags list of strings Optional\\nFilters for work with any of the provided tags.\\ntarget_close_date object Optional\\nProvides ways to specify",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1785_KNOWLEDGE_NODE-449",
"text": "2 variants\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue object Optional\\nShow 9 properties\\nmodified_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\nopportunity object Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1821_KNOWLEDGE_NODE-468",
"text": "any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow property\\nstaged_info object Optional\\nShow property\\nsync_metadata object Optional\\nShow 4 properties\\ntags list of strings Optional\\nFilters for work with any of the provided tags.\\ntarget_close_date object Optional\\nProvides ways to specify",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1786_KNOWLEDGE_NODE-450",
"text": "2 variants\\ncustom_fields map from strings to any Optional\\nFilters for custom fields.\\nfirst integer Optional\\nThe number of work items to return. The default is \\'50\\', the maximum is \\'5000\\'.\\nissue object Optional\\nShow 9 properties\\nmodified_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\nopportunity object Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1637_KNOWLEDGE_NODE-472",
"text": "any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow property\\nstaged_info object Optional\\nShow property\\nsync_metadata object Optional\\nShow 4 properties\\ntags list of strings Optional\\nFilters for work with any of the provided tags.\\ntarget_close_date object Optional\\nProvides ways to specify",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1805_KNOWLEDGE_NODE-468",
"text": "any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow property\\nstaged_info object Optional\\nShow property\\nsync_metadata object Optional\\nShow 4 properties\\ntags list of strings Optional\\nFilters for work with any of the provided tags.\\ntarget_close_date object Optional\\nProvides ways to specify",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1838_KNOWLEDGE_NODE-452",
"text": "reported by any of these users.\\nsort_by list of strings Optional\\nFields to sort the work items by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow property\\nstaged_info object Optional\\nShow property\\nsync_metadata object Optional\\nShow 4 properties\\ntags list of strings Optional\\nFilters for work with any of the provided tags.\\ntarget_close_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\nticket object Optional\\nShow",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1781_KNOWLEDGE_NODE-465",
"text": "any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow property\\nstaged_info object Optional\\nShow property\\nsync_metadata object Optional\\nShow 4 properties\\ntags list of strings Optional\\nFilters for work with any of the provided tags.\\ntarget_close_date object Optional\\nProvides ways to specify",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1650_KNOWLEDGE_NODE-464",
"text": "any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow property\\nstaged_info object Optional\\nShow property\\nsync_metadata object Optional\\nShow 4 properties\\ntags list of strings Optional\\nFilters for work with any of the provided tags.\\ntarget_close_date object Optional\\nProvides ways to specify",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1823_KNOWLEDGE_NODE-466",
"text": "Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow property\\nstaged_info object Optional\\nShow property\\nsync_metadata object Optional\\nShow 4 properties\\ntags list of strings Optional\\nFilters for work",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1789_KNOWLEDGE_NODE-467",
"text": "any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow property\\nstaged_info object Optional\\nShow property\\nsync_metadata object Optional\\nShow 4 properties\\ntags list of strings Optional\\nFilters for work with any of the provided tags.\\ntarget_close_date object Optional\\nProvides ways to specify",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1829_KNOWLEDGE_NODE-481",
"text": "Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow property\\nstaged_info object Optional\\nShow property\\nsync_metadata object Optional\\nShow 4 properties\\ntags list of strings Optional\\nFilters for work",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1575_KNOWLEDGE_NODE-471",
"text": "any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow property\\nstaged_info object Optional\\nShow property\\nsync_metadata object Optional\\nShow 4 properties\\ntags list of strings Optional\\nFilters for work with any of the provided tags.\\ntarget_close_date object Optional\\nProvides ways to specify",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1651_KNOWLEDGE_NODE-473",
"text": "Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow property\\nstaged_info object Optional\\nShow property\\nsync_metadata object Optional\\nShow 4 properties\\ntags list of strings Optional\\nFilters for work",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1633_KNOWLEDGE_NODE-472",
"text": "Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow property\\nstaged_info object Optional\\nShow property\\nsync_metadata object Optional\\nShow 4 properties\\ntags list of strings Optional\\nFilters for work",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1791_KNOWLEDGE_NODE-466",
"text": "any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow property\\nstaged_info object Optional\\nShow property\\nsync_metadata object Optional\\nShow 4 properties\\ntags list of strings Optional\\nFilters for work with any of the provided tags.\\ntarget_close_date object Optional\\nProvides ways to specify",
"title": "Self Delete — DevRev | Docs"
},
{
"id": "ART-1607_KNOWLEDGE_NODE-470",
"text": "Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow property\\nstaged_info object Optional\\nShow property\\nsync_metadata object Optional\\nShow 4 properties\\ntags list of strings Optional\\nFilters for work",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1830_KNOWLEDGE_NODE-481",
"text": "Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow property\\nstaged_info object Optional\\nShow property\\nsync_metadata object Optional\\nShow 4 properties\\ntags list of strings Optional\\nFilters for work",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1300_KNOWLEDGE_NODE-467",
"text": "any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow property\\nstaged_info object Optional\\nShow property\\nsync_metadata object Optional\\nShow 4 properties\\ntags list of strings Optional\\nFilters for work with any of the provided tags.\\ntarget_close_date object Optional\\nProvides ways to specify",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1824_KNOWLEDGE_NODE-465",
"text": "Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow property\\nstaged_info object Optional\\nShow property\\nsync_metadata object Optional\\nShow 4 properties\\ntags list of strings Optional\\nFilters for work",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1833_KNOWLEDGE_NODE-466",
"text": "any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow property\\nstaged_info object Optional\\nShow property\\nsync_metadata object Optional\\nShow 4 properties\\ntags list of strings Optional\\nFilters for work with any of the provided tags.\\ntarget_close_date object Optional\\nProvides ways to specify",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1831_KNOWLEDGE_NODE-481",
"text": "Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow property\\nstaged_info object Optional\\nShow property\\nsync_metadata object Optional\\nShow 4 properties\\ntags list of strings Optional\\nFilters for work",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1818_KNOWLEDGE_NODE-468",
"text": "any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow property\\nstaged_info object Optional\\nShow property\\nsync_metadata object Optional\\nShow 4 properties\\ntags list of strings Optional\\nFilters for work with any of the provided tags.\\ntarget_close_date object Optional\\nProvides ways to specify",
"title": "Sla Trackers Get Post — DevRev | Docs"
},
{
"id": "ART-1588_KNOWLEDGE_NODE-470",
"text": "Optional\\nShow 3 properties\\nowned_by list of strings Optional\\nFilters for work owned by any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow property\\nstaged_info object Optional\\nShow property\\nsync_metadata object Optional\\nShow 4 properties\\ntags list of strings Optional\\nFilters for work",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1591_KNOWLEDGE_NODE-469",
"text": "any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow property\\nstaged_info object Optional\\nShow property\\nsync_metadata object Optional\\nShow 4 properties\\ntags list of strings Optional\\nFilters for work with any of the provided tags.\\ntarget_close_date object Optional\\nProvides ways to specify",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1784_KNOWLEDGE_NODE-456",
"text": "users.\\nreported_by string Optional\\nFilters for work reported by any of these users.\\nsort_by string Optional\\nFields to sort the works by and the direction to sort them.\\nstage.name string Optional\\nFilters for records in the provided stage(s) by name.\\nstaged_info.is_staged boolean Optional\\nFilters for issues that are staged.\\nsync_metadata.external_reference string Optional\\nFilters for issues with this specific external reference.\\nsync_metadata.last_sync_in.status enum Optional\\nFilters",
"title": "Locate Post — DevRev | Docs"
},
{
"id": "ART-1307_KNOWLEDGE_NODE-468",
"text": "any of these users.\\nreported_by list of strings Optional\\nFilters for work reported by any of these users.\\nsort_by list of strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow property\\nstaged_info object Optional\\nShow property\\nsync_metadata object Optional\\nShow 4 properties\\ntags list of strings Optional\\nFilters for work with any of the provided tags.\\ntarget_close_date object Optional\\nProvides ways to specify",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1786_KNOWLEDGE_NODE-457",
"text": "users.\\nreported_by string Optional\\nFilters for work reported by any of these users.\\nsort_by string Optional\\nFields to sort the works by and the direction to sort them.\\nstage.name string Optional\\nFilters for records in the provided stage(s) by name.\\nstaged_info.is_staged boolean Optional\\nFilters for issues that are staged.\\nsync_metadata.external_reference string Optional\\nFilters for issues with this specific external reference.\\nsync_metadata.last_sync_in.status enum Optional\\nFilters",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-17231_KNOWLEDGE_NODE-100",
"text": "(collection)\\xe2\\x86\\x92[#category:user] | \\xe2\\x9c\\x94\\xef\\xb8\\x8e | User IDs of the users that own the work |\\n| `priority` | enum | \\xe2\\x9c\\x94\\xef\\xb8\\x8e | Priority of the work based upon impact and criticality |\\n| `release_version_ids` | reference (collection)\\xe2\\x86\\x92[#record:version] | | Versions that will contain the resolving commit IDs |\\n| `reported_by_ids` | reference (collection)\\xe2\\x86\\x92[#category:user] | | User IDs of the users that reported the work |\\n| `rev_org_ids`",
"title": "Supported DevRev object types | DevRev | Docs"
},
{
"id": "ART-1592_KNOWLEDGE_NODE-459",
"text": "users.\\nreported_by string Optional\\nFilters for work reported by any of these users.\\nsort_by string Optional\\nFields to sort the works by and the direction to sort them.\\nstage.name string Optional\\nFilters for records in the provided stage(s) by name.\\nstaged_info.is_staged boolean Optional\\nFilters for issues that are staged.\\nsync_metadata.external_reference string Optional\\nFilters for issues with this specific external reference.\\nsync_metadata.last_sync_in.status enum Optional\\nFilters",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1832_KNOWLEDGE_NODE-465",
"text": "users.\\nreported_by string Optional\\nFilters for work reported by any of these users.\\nsort_by string Optional\\nFields to sort the works by and the direction to sort them.\\nstage.name string Optional\\nFilters for records in the provided stage(s) by name.\\nstaged_info.is_staged boolean Optional\\nFilters for issues that are staged.\\nsync_metadata.external_reference string Optional\\nFilters for issues with this specific external reference.\\nsync_metadata.last_sync_in.status enum Optional\\nFilters",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1301_KNOWLEDGE_NODE-462",
"text": "users.\\nreported_by string Optional\\nFilters for work reported by any of these users.\\nsort_by string Optional\\nFields to sort the works by and the direction to sort them.\\nstage.name string Optional\\nFilters for records in the provided stage(s) by name.\\nstaged_info.is_staged boolean Optional\\nFilters for issues that are staged.\\nsync_metadata.external_reference string Optional\\nFilters for issues with this specific external reference.\\nsync_metadata.last_sync_in.status enum Optional\\nFilters",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1838_KNOWLEDGE_NODE-458",
"text": "users.\\nreported_by string Optional\\nFilters for work reported by any of these users.\\nsort_by string Optional\\nFields to sort the works by and the direction to sort them.\\nstage.name string Optional\\nFilters for records in the provided stage(s) by name.\\nstaged_info.is_staged boolean Optional\\nFilters for issues that are staged.\\nsync_metadata.external_reference string Optional\\nFilters for issues with this specific external reference.\\nsync_metadata.last_sync_in.status enum Optional\\nFilters",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1302_KNOWLEDGE_NODE-462",
"text": "users.\\nreported_by string Optional\\nFilters for work reported by any of these users.\\nsort_by string Optional\\nFields to sort the works by and the direction to sort them.\\nstage.name string Optional\\nFilters for records in the provided stage(s) by name.\\nstaged_info.is_staged boolean Optional\\nFilters for issues that are staged.\\nsync_metadata.external_reference string Optional\\nFilters for issues with this specific external reference.\\nsync_metadata.last_sync_in.status enum Optional\\nFilters",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1562_KNOWLEDGE_NODE-510",
"text": "Optional\\n\\nFilters for custom fields.\\n\\nfirst integer Optional\\n\\nThe number of work items to return. The default is \\xe2\\x80\\x9850\\xe2\\x80\\x99, the maximum is \\xe2\\x80\\x985000\\xe2\\x80\\x99.\\n\\nissue object Optional\\nShow 9 properties\\nmodified_date object Optional\\n\\nProvides ways to specify date ranges on objects.\\n\\nShow 2 variants\\nopportunity object Optional\\nShow 3 properties\\nowned_by list of strings Optional\\n\\nFilters for work owned by any of these users.\\n\\nreported_by list of",
"title": "Get (Beta) — DevRev | Docs"
},
{
"id": "ART-1806_KNOWLEDGE_NODE-462",
"text": "users.\\nreported_by string Optional\\nFilters for work reported by any of these users.\\nsort_by string Optional\\nFields to sort the works by and the direction to sort them.\\nstage.name string Optional\\nFilters for records in the provided stage(s) by name.\\nstaged_info.is_staged boolean Optional\\nFilters for issues that are staged.\\nsync_metadata.external_reference string Optional\\nFilters for issues with this specific external reference.\\nsync_metadata.last_sync_in.status enum Optional\\nFilters",
"title": "Self Post — DevRev | Docs"
},
{
"id": "ART-4131_KNOWLEDGE_NODE-10",
"text": "], |\\n| 166 | \"url\": \"string\" |\\n| 167 | }, |\\n| 168 | \"sync_metadata\": { |\\n| 169 | \"external_reference\": \"string\", |\\n| 170 | \"origin_system\": \"string\" |\\n| 171 | }, |\\n| 172 | \"title\": \"string\" |\\n| 173 | } |\\n| 174 | ], |\\n| 175 | \"reported_by\": { |\\n| 176 | \"id\": 1, |\\n| 177 | \"label\": \"string\", |\\n| 178 | \"ordinal\": 1, |\\n| 179 | \"value\": null |\\n| 180 | }, |\\n| 181 | \"severity\": { |\\n| 182 | \"id\": 1, |\\n| 183 | \"label\": \"string\", |\\n| 184 | \"ordinal\": 1, |\\n| 185 | \"value\": null |\\n| 186",
"title": "List Incidents (POST) | DevRev | Docs"
},
{
"id": "ART-1304_KNOWLEDGE_NODE-461",
"text": "users.\\nreported_by string Optional\\nFilters for work reported by any of these users.\\nsort_by string Optional\\nFields to sort the works by and the direction to sort them.\\nstage.name string Optional\\nFilters for records in the provided stage(s) by name.\\nstaged_info.is_staged boolean Optional\\nFilters for issues that are staged.\\nsync_metadata.external_reference string Optional\\nFilters for issues with this specific external reference.\\nsync_metadata.last_sync_in.status enum Optional\\nFilters",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1249_KNOWLEDGE_NODE-19",
"text": "of these users.\\n\\nreported\\\\_bylist of stringsOptional\\n\\nFilters for work reported by any of these users.\\n\\nsort\\\\_bylist of stringsOptional\\n\\nFields to sort the works by and the direction to sort them.\\n\\nstageobjectOptional\\n\\nThe filter for stages.\\n\\nShow 1 properties\\n\\nstaged\\\\_infoobjectOptional\\n\\nShow 1 properties\\n\\nstatelist of stringsOptional\\n\\nFilters for work with any of the provided states.\\n\\nsync\\\\_metadataobjectOptional\\n\\nShow 4 properties\\n\\ntagslist of",
"title": "List Works (POST) | DevRev | Docs"
},
{
"id": "ART-1783_KNOWLEDGE_NODE-456",
"text": "users.\\nreported_by string Optional\\nFilters for work reported by any of these users.\\nsort_by string Optional\\nFields to sort the works by and the direction to sort them.\\nstage.name string Optional\\nFilters for records in the provided stage(s) by name.\\nstaged_info.is_staged boolean Optional\\nFilters for issues that are staged.\\nsync_metadata.external_reference string Optional\\nFilters for issues with this specific external reference.\\nsync_metadata.last_sync_in.status enum Optional\\nFilters",
"title": "Locate — DevRev | Docs"
},
{
"id": "ART-1785_KNOWLEDGE_NODE-456",
"text": "users.\\nreported_by string Optional\\nFilters for work reported by any of these users.\\nsort_by string Optional\\nFields to sort the works by and the direction to sort them.\\nstage.name string Optional\\nFilters for records in the provided stage(s) by name.\\nstaged_info.is_staged boolean Optional\\nFilters for issues that are staged.\\nsync_metadata.external_reference string Optional\\nFilters for issues with this specific external reference.\\nsync_metadata.last_sync_in.status enum Optional\\nFilters",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1819_KNOWLEDGE_NODE-460",
"text": "users.\\nreported_by string Optional\\nFilters for work reported by any of these users.\\nsort_by string Optional\\nFields to sort the works by and the direction to sort them.\\nstage.name string Optional\\nFilters for records in the provided stage(s) by name.\\nstaged_info.is_staged boolean Optional\\nFilters for issues that are staged.\\nsync_metadata.external_reference string Optional\\nFilters for issues with this specific external reference.\\nsync_metadata.last_sync_in.status enum Optional\\nFilters",
"title": "Sla Trackers Get — DevRev | Docs"
},
{
"id": "ART-1652_KNOWLEDGE_NODE-455",
"text": "users.\\nreported_by string Optional\\nFilters for work reported by any of these users.\\nsort_by string Optional\\nFields to sort the works by and the direction to sort them.\\nstage.name string Optional\\nFilters for records in the provided stage(s) by name.\\nstaged_info.is_staged boolean Optional\\nFilters for issues that are staged.\\nsync_metadata.external_reference string Optional\\nFilters for issues with this specific external reference.\\nsync_metadata.last_sync_in.status enum Optional\\nFilters",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1566_KNOWLEDGE_NODE-504",
"text": "users.\\n\\nreported_by string Optional\\n\\nFilters for work reported by any of these users.\\n\\nsort_by string Optional\\n\\nFields to sort the work items by and the direction to sort them.\\n\\nstage.name string Optional\\n\\nFilters for records in the provided stage(s) by name.\\n\\nstaged_info.is_staged boolean Optional\\n\\nFilters for issues that are staged.\\n\\nsync_metadata.external_reference string Optional\\n\\nFilters for issues with this specific external",
"title": "Transition (Beta) — DevRev | Docs"
},
{
"id": "ART-1802_KNOWLEDGE_NODE-462",
"text": "users.\\nreported_by string Optional\\nFilters for work reported by any of these users.\\nsort_by string Optional\\nFields to sort the works by and the direction to sort them.\\nstage.name string Optional\\nFilters for records in the provided stage(s) by name.\\nstaged_info.is_staged boolean Optional\\nFilters for issues that are staged.\\nsync_metadata.external_reference string Optional\\nFilters for issues with this specific external reference.\\nsync_metadata.last_sync_in.status enum Optional\\nFilters",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1545_KNOWLEDGE_NODE-502",
"text": "users.\\n\\nreported_by string Optional\\n\\nFilters for work reported by any of these users.\\n\\nsort_by string Optional\\n\\nFields to sort the work items by and the direction to sort them.\\n\\nstage.name string Optional\\n\\nFilters for records in the provided stage(s) by name.\\n\\nstaged_info.is_staged boolean Optional\\n\\nFilters for issues that are staged.\\n\\nsync_metadata.external_reference string Optional\\n\\nFilters for issues with this specific external",
"title": "Create (Beta) — DevRev | Docs"
},
{
"id": "ART-1779_KNOWLEDGE_NODE-458",
"text": "users.\\nreported_by string Optional\\nFilters for work reported by any of these users.\\nsort_by string Optional\\nFields to sort the works by and the direction to sort them.\\nstage.name string Optional\\nFilters for records in the provided stage(s) by name.\\nstaged_info.is_staged boolean Optional\\nFilters for issues that are staged.\\nsync_metadata.external_reference string Optional\\nFilters for issues with this specific external reference.\\nsync_metadata.last_sync_in.status enum Optional\\nFilters",
"title": "Get — DevRev | Docs"
}
] |
18318774-e8d3-4bd8-84d2-15bdd14dabee
|
start a conversation with a contact
|
[
{
"id": "ART-15509_KNOWLEDGE_NODE-14",
"text": "//Your logic goes here |\\n| 5 | } |\\n| 6 | }); |\\n| 7 | }, []); |\\n```\\n\\nStart conversation\\n------------------\\n\\nThe `startConversationContent` method opens the Plug widget directly to the conversation creation view. It replicates the action of clicking the **Send us a message** button, launching the widget to the conversation initiation screen.\\n\\nThis method also accepts an optional input parameter to pre-fill a message on the conversation creation screen, providing your users with a",
"title": "Methods | DevRev | Docs"
},
{
"id": "ART-1788_KNOWLEDGE_NODE-85",
"text": "conversation.\\nRequest.\\n\\nThis endpoint expects an object.\\ntype \"support\" Required\\ndescription string Optional\\nDescription for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmembers list of strings Optional\\nThe users in the conversation.\\nmessages list of objects Optional\\nInitial messages on the conversation.\\nShow 2 properties\\nmetadata object Optional\\nShow",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1789_KNOWLEDGE_NODE-85",
"text": "https:// api.devrev.ai / conversations.create\\nCreates a conversation.\\nRequest.\\n\\nThis endpoint expects an object.\\ntype \"support\" Required\\ndescription string Optional\\nDescription for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmembers list of strings Optional\\nThe users in the conversation.\\nmessages list of objects Optional\\nInitial messages on the conversation.\\nShow 2",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1300_KNOWLEDGE_NODE-85",
"text": "https:// api.devrev.ai / conversations.create\\nCreates a conversation.\\nRequest.\\n\\nThis endpoint expects an object.\\ntype \"support\" Required\\ndescription string Optional\\nDescription for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmembers list of strings Optional\\nThe users in the conversation.\\nmessages list of objects Optional\\nInitial messages on the conversation.\\nShow 2",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1781_KNOWLEDGE_NODE-83",
"text": "Create.\\n\\nPOST https:// api.devrev.ai / conversations.create\\nCreates a conversation.\\nRequest.\\n\\nThis endpoint expects an object.\\ntype \"support\" Required\\ndescription string Optional\\nDescription for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmembers list of strings Optional\\nThe users in the conversation.\\nmessages list of objects Optional\\nInitial messages on the",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1791_KNOWLEDGE_NODE-84",
"text": "Create.\\n\\nPOST https:// api.devrev.ai / conversations.create\\nCreates a conversation.\\nRequest.\\n\\nThis endpoint expects an object.\\ntype \"support\" Required\\ndescription string Optional\\nDescription for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmembers list of strings Optional\\nThe users in the conversation.\\nmessages list of objects Optional\\nInitial messages on the",
"title": "Self Delete — DevRev | Docs"
},
{
"id": "ART-4071_KNOWLEDGE_NODE-0",
"text": "b'[](/public/api-reference/conversations/create)\\n\\nPublic\\n\\n[API Reference](/public/api-reference/getting-started)[Conversations](/public/api-reference/conversations/create)\\n\\n# Create Conversation\\n\\nPOST\\n\\nhttps://api.devrev.ai/conversations.create\\n\\nTry it\\n\\nCreates a conversation.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\ntypeenumRequired\\n\\nAllowed values: support\\n\\nbrandstringOptional`format: \"id\"`\\n\\nThe brand associated with the conversation.\\n\\nchannelslist of",
"title": "Create Conversation — DevRev | Docs"
},
{
"id": "ART-1792_KNOWLEDGE_NODE-86",
"text": "send.\\nShow variant\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference conversations Create.\\n\\nPOST https:// api.devrev.ai / conversations.create\\nCreates a conversation.\\nRequest.\\n\\nThis endpoint expects an object.\\ntype \"support\" Required\\ndescription string Optional\\nDescription for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmembers list of strings",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1786_KNOWLEDGE_NODE-83",
"text": "send.\\nShow variant\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference conversations Create.\\n\\nPOST https:// api.devrev.ai / conversations.create\\nCreates a conversation.\\nRequest.\\n\\nThis endpoint expects an object.\\ntype \"support\" Required\\ndescription string Optional\\nDescription for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmembers list of strings",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1506_KNOWLEDGE_NODE-0",
"text": "b'[](/beta/api-reference/conversations/create)\\n\\nBeta\\n\\n[API Reference](/beta/api-reference/accounts/create)[conversations](/beta/api-reference/conversations/create)\\n\\n# Create Conversation\\n\\nPOST\\n\\nhttps://api.devrev.ai/conversations.create\\n\\nTry it\\n\\nCreates a conversation.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\ntype\"support\"Required\\n\\ncustom_fieldsmap from strings to anyOptional\\n\\nApplication-defined custom fields.\\n\\ncustom_schema_specobjectOptional\\n\\nRequested",
"title": "Create Conversation (Beta) — DevRev | Docs"
},
{
"id": "ART-2897_KNOWLEDGE_NODE-16",
"text": "conversation with your team.\\n\\n[code]\\n\\n 1| plugSDK.toggleWidget(true, \\'create_conversation\\', { \\n ---|--- \\n 2| \\tstartConversationContent: \\'Hi\\', \\n 3| });\\n[/code] \\n \\n## Shutdown\\n\\nThe `shutdown()` method is used to end the current user session in the PLuG widget. It allows you to clear users\\xe2\\x80\\x99 conversations and tickets when they log out of your application.\\n\\n[code]\\n\\n 1| await window.plugSDK.shutdown(); \\n ---|---\\n[/code] \\n \\nAfter calling",
"title": "Methods — DevRev | Docs"
},
{
"id": "ART-12460_KNOWLEDGE_NODE-11",
"text": "the SDK to be configured and the user to be identified, whether they are unverified or anonymous.\\n\\nTo show the support chat screen in your app, you can use the following method:\\n\\n[code]\\n\\n 1| DevRev.showSupport(successCallback, errorCallback) \\n ---|---\\n[/code] \\n \\n### Creating a new support conversation\\n\\nYou can initiate a new support conversation directly from your app. This method displays the support chat screen and simultaneously creates a new conversation.\\n\\n[code]\\n\\n",
"title": "Features — DevRev | Docs"
},
{
"id": "ART-1466_KNOWLEDGE_NODE-23",
"text": "} ) ; 7 } , []) ; Check widget status.\\n\\nUse isWidgetOpen to determine whether your chat widget is currently open or closed.\\n\\n1 window. plugSDK. isWidgetOpen\\n\\nThis returns true if the chat widget is open and false if it is closed.\\n\\nStart conversation.\\n\\nThe startConversationContent method opens the PLuG widget directly to the conversation creation view. It replicates the action of clicking the Send us a message. button, launching the widget to the conversation initiation screen.\\n\\nThis",
"title": "Methods — DevRev | Docs"
},
{
"id": "ART-15301_KNOWLEDGE_NODE-1",
"text": "> | -d \\'{ |\\n| > | \"users\": [ |\\n| > | \"DEVU-12345\" |\\n| > | ] |\\n| > | }\\' |\\n```\\n\\n[Try it](/api-reference/chats/create?explorer=true)\\n\\n201Created\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"chat\": { |\\n| 3 | \"type\": \"string\" |\\n| 4 | } |\\n| 5 | } |\\n```\\n\\nCreates a new chat, or optionally opens an existing one.\\n\\n### Headers\\n\\nAuthorizationstringRequired\\n\\nBearer authentication of the form `Bearer <token>`, where token is your auth token.\\n\\n### Request\\n\\nThis endpoint expects",
"title": "Create Chat | DevRev | Docs"
},
{
"id": "ART-4071_KNOWLEDGE_NODE-4",
"text": "\"text\"`\\n\\nThe title for the conversation.\\n\\nuser_sessionslist of stringsOptional\\n\\nThe IDs of user sessions associated with the conversation.\\n\\n### Response\\n\\nThe response to creating a new conversation.\\n\\nconversationobject\\n\\nShow 18 properties\\n\\n### Errors\\n\\n400\\n\\nBad Request Error\\n\\n401\\n\\nUnauthorized Error\\n\\n403\\n\\nForbidden Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nPOST\\n\\n/conversations.create\\n\\n[code]\\n\\n",
"title": "Create Conversation — DevRev | Docs"
}
] |
1b0f355e-29d3-48a8-a040-4de867fb674b
|
upload csv file utf8 encoding error missing field
|
[
{
"id": "ART-2575_KNOWLEDGE_NODE-31",
"text": "Pre-create the tag in the app before importing. |\\n| Account with external reference \\'non-existing-account\\' not found | Ensure the parent account exists in the app before importing. |\\n| Mandatory field \\'external\\\\_refs\\' is empty | Fill all mandatory fields in the CSV. |\\n| Found non utf-8 character | Export the CSV with UTF-8 encoding. |\\n| Input CSV has no rows | Ensure the CSV contains data rows. |\\n| No user found with email | Ensure the email is correct and not a name. |\\n| Missing",
"title": "Account and contact import | Computer for Growth Teams | DevRev"
},
{
"id": "ART-16355_KNOWLEDGE_NODE-30",
"text": "want to perform the operation on.\\n5. A sample CSV file is generated, with some mandatory fields specified.\\n6. Click **Upload**, browse and select the file, and then click **Submit**.\\n7. If all required headers exist in the CSV and the correct fields are provided as headers, a timeline comment is generated in the **Discussion** tab of the snap-in with the validation result of headers passed . Otherwise, it displays the invalid headers and any missing required headers.\\n8. After the operation",
"title": "CSV commands uploader | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2010_KNOWLEDGE_NODE-25",
"text": "from a CSV file. The CSV file supports the following columns:\\n\\n```\\n```\\n1 Title,Description,Owners,Part,Tags,Subtype,WorkType\\n\\n\\n\\n2 Front page not loading,\"This is a sample ticket body with \\xe2\\x80\\x9c\\xe2\\x80\\x9d quotes\",[email protected],PROD-1,frontend,subtype1,Ticket\\n\\n\\n\\n3 APIs returning errors,\"The user.get API is returning 500\",[email protected],PROD-2,backend,subtype2,Issue\\n```\\n```\\n\\nThe Title column is required, while the others are optional. If the WorkType column",
"title": "Bulk work item uploader | Automate | Snap-ins | DevRev"
},
{
"id": "ART-15689_KNOWLEDGE_NODE-28",
"text": "to give access to run the snap-in\\n3. In the **Discussion** tab of the snap-in, enter /upload\\\\_timelines.\\n4. A sample CSV file is generated, with display\\\\_id as a mandatory field.\\n5. Click **Upload**, browse and select the file, and then click **Submit**.\\n6. If all required headers exist in the CSV and the correct fields are provided as headers, a timeline comment is generated in the **Discussion** tab of the snap-in with the validation result of headers passed. Otherwise, it displays the",
"title": "CSV comments uploader | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2575_KNOWLEDGE_NODE-27",
"text": "initiate the process. Notifications about successful imports and any errors will appear in the form of toasts at the bottom left.\\n\\nCSV file requirements\\n---------------------\\n\\n### Mandatory fields\\n\\nTo ensure a successful import, certain fields are required.\\n\\n**Accounts**:\\n\\n* display\\\\_name\\n* external\\\\_refs (a unique identifier for the account, such as the company\\'s website domain.)\\n\\n**Contacts:**\\n\\n* display\\\\_name\\n* external\\\\_ref (a unique identifier for the contact, such as",
"title": "Account and contact import | Computer for Growth Teams | DevRev"
},
{
"id": "ART-15689_KNOWLEDGE_NODE-26",
"text": "and must contain a valid work item display ID.\\n2. For tagging users in the timeline entries, use the format <[email protected]>.\\n3. Timeline entries can be added to both internal discussions and customer messages.\\n4. The CSV should contain at least one of internal\\\\_discussion or external\\\\_discussion columns.\\n\\n![]()\\n\\nThe maximum row limit for the input CSV is 5,000.\\n\\nValidations for uploading CSV\\n-----------------------------\\n\\nThe following validations are done while creating timeline",
"title": "CSV comments uploader | Automate | Snap-ins | DevRev"
},
{
"id": "ART-16355_KNOWLEDGE_NODE-25",
"text": "handling and detailed tracking. With comprehensive status reporting, users receive a clear breakdown of successful and failed operations, including row numbers, error reasons, and the display name of command.\\n\\nFeature\\n-------\\n\\n* **Access Control**: Ensures only authorized users from the group selected in the snap-in configuration can run the snap-in.\\n\\nCSV requirements\\n----------------\\n\\n* The **Display\\\\_name** of the command is the only mandatory column.\\n* For the **Owned\\\\_by**,",
"title": "CSV commands uploader | Automate | Snap-ins | DevRev"
}
] |
cc5293e1-60d6-474d-90ed-dbb8b2d490be
|
slack integration native does not work
|
[
{
"id": "ART-2035_KNOWLEDGE_NODE-60",
"text": "hidden.\\n\\n![]()\\n\\nSlack currently does not support custom objects or related automations.\\n\\nSlack snap-in user resolution\\n-----------------------------\\n\\n* The Slack snap-in uses email for user resolution between platforms. If a user or organization hides their emails, the integration cannot resolve the user to a DevRev Contact and will act on behalf of itself instead. It's recommended to ask customers to share their emails with your organization so apps, including DevRev, can access",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-28",
"text": "maintain one public connection per DevRev organization. Within an organization, one Slack connection can be used across multiple snap-ins and workflows. Creating multiple connections may disrupt existing integrations.\\n* Connecting with Slack enterprise workspace is currently in limited availability. If you have a Slack Enterprise account, please contact DevRev Support to be whitelisted before attempting setup.\\n\\n1. Search and open [Slack](https://marketplace.devrev.ai/one-slack) in the DevRev",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-57",
"text": "**Slack snap-in event discussions panel** to automatically invite the DevRev app to all public channels.\\n + Private channels still require manual addition.\\n\\n### When sync is not possible\\n\\nIf sync isn\\xe2\\x80\\x99t possible, the form will display a clear warning. Possible reasons include:\\n\\n* The thread is already in sync with another DevRev object.\\n* Sync is not supported for the object in the given Slack channel.\\n* The DevRev app is not a member of the channel.\\n* The channel is",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-56",
"text": "accounts, or AI agents in DevRev aren\\xe2\\x80\\x99t synced to Slack. To change this, enable the **Sync bot messages from DevRev to Slack** option in snap-in configurations.\\n* The snap-in supports syncing of message edits and deletions between platforms.\\n* Message attachment sync is supported both ways, with a file size limit of 250MB.\\n\\n### Inviting DevRev app to channels\\n\\n* Adding the DevRev app to many Slack channels can be challenging at scale.\\n* Use the /SlackInviteBot command from the",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-55",
"text": "Set up 2 way message synchronization between a complete Slack channel and DevRev object discussion. | - Slack connection - DevRev object ID - Slack channel ID | N/A |\\n\\nAdditional capabilities and limitations\\n---------------------------------------\\n\\n### 2-way sync between DevRev and Slack\\n\\n* If two-way sync is enabled on an object, new messages received from non-Slack source channels will appear in DevRev but won't sync to the Slack thread.\\n* By default, messages from bots, service",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-15716_KNOWLEDGE_NODE-0",
"text": "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",
"title": "Support queries related playbook"
},
{
"id": "ART-15716_KNOWLEDGE_NODE-1",
"text": "read messages, post messages, and access user info in the selected channels.\\n\\n[Slack integration setup guide](https://devrev.ai/docs/integrations/slack)\\n\\n3. Jira Integration with Label-Based SyncYou can connect DevRev to Jira using the Jira snap-in. During setup, you can configure filters to sync only issues with a specific label by setting up the appropriate JQL (Jira Query Language) filter in the integration settings.\\n\\n[DevRev\\xe2\\x80\\x93Jira integration",
"title": "Support queries related playbook"
}
] |
d9d4102e-3b41-46ae-bda2-99cb52703413
|
where to find Rev organization ID
|
[
{
"id": "ART-1418_KNOWLEDGE_NODE-2",
"text": "default Rev organization is to be fetched.\\n\\nidstringOptional`format: \"id\"`\\n\\nThe ID of the required Rev organization.\\n\\n### Response\\n\\nThe response to getting a Rev organization\\xe2\\x80\\x99s information.\\n\\nrev_orgobject\\n\\nShow 11 properties\\n\\n### Errors\\n\\n400\\n\\nBad Request Error\\n\\n401\\n\\nUnauthorized Error\\n\\n403\\n\\nForbidden Error\\n\\n404\\n\\nNot Found Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable",
"title": "Get Rev Org (POST) — DevRev | Docs"
},
{
"id": "ART-1214_KNOWLEDGE_NODE-4",
"text": "|\\n| 49 | \"domain\": \"string\" |\\n| 50 | } |\\n| 51 | } |\\n```\\n\\nRetrieves the Rev organization\\'s information.\\n\\n### Headers\\n\\nAuthorizationstringRequired\\n\\nBearer authentication of the form `Bearer <token>`, where token is your auth token.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\naccountstringOptional`format: \"id\"`\\n\\nThe ID of account for which default Rev organization is to be\\nfetched.\\n\\nidstringOptional`format: \"id\"`\\n\\nThe ID of the required Rev organization.\\n\\n###",
"title": "Get Rev Org (POST) | DevRev | Docs"
},
{
"id": "ART-1566_KNOWLEDGE_NODE-395",
"text": "https://api.devrev.ai / rev-orgs.get\\n\\nRetrieves the Rev organization\\xe2\\x80\\x99s information.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\n\\nThe ID of account for which default Rev organization is to be fetched.\\n\\nid string Optional\\n\\nThe ID of the required Rev organization.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://api.devrev.ai / rev-orgs.list\\n\\nGets the list of Rev",
"title": "Transition (Beta) — DevRev | Docs"
},
{
"id": "ART-1545_KNOWLEDGE_NODE-393",
"text": "https://api.devrev.ai / rev-orgs.get\\n\\nRetrieves the Rev organization\\xe2\\x80\\x99s information.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\n\\nThe ID of account for which default Rev organization is to be fetched.\\n\\nid string Optional\\n\\nThe ID of the required Rev organization.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://api.devrev.ai / rev-orgs.list\\n\\nGets the list of Rev",
"title": "Create (Beta) — DevRev | Docs"
},
{
"id": "ART-2933_KNOWLEDGE_NODE-16",
"text": "\"active\" |\\n | 30 | }, |\\n | 31 | \"modified_date\": \"2024-03-07T08:47:04.346Z\", |\\n | 32 | \"stock_schema_fragment\": \"don:core:dvrv-us-1:stock_sf/32027\" |\\n | 33 | } |\\n | 34 | ] |\\n | 35 | } |\\n ```\\n\\n Note the `display_id` (example: `REV-abcd`) of the rev org from the response.\\n\\n* If there is an existing account then you can get the default rev org using the `rev-orgs.get` API:\\n\\n + Make a GET request to \\xe2\\x80\\x9c<https://api.devrev.ai/rev-orgs.get>\\xe2\\x80\\x9d using",
"title": "Account creation | DevRev | Docs"
},
{
"id": "ART-1595_KNOWLEDGE_NODE-343",
"text": "to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1551_KNOWLEDGE_NODE-393",
"text": "Rev organization\\xe2\\x80\\x99s information.\\n\\nQuery parameters.\\n\\naccount string Optional\\n\\nThe ID of account for which default Rev organization is to be fetched.\\n\\nid string Optional\\n\\nThe ID of the required Rev organization.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https://api.devrev.ai / rev-orgs.get\\n\\nRetrieves the Rev organization\\xe2\\x80\\x99s information.\\n\\nRequest.\\n\\nThis endpoint expects an",
"title": "Update (Beta) — DevRev | Docs"
},
{
"id": "ART-1549_KNOWLEDGE_NODE-393",
"text": "Rev organization\\xe2\\x80\\x99s information.\\n\\nQuery parameters.\\n\\naccount string Optional\\n\\nThe ID of account for which default Rev organization is to be fetched.\\n\\nid string Optional\\n\\nThe ID of the required Rev organization.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https://api.devrev.ai / rev-orgs.get\\n\\nRetrieves the Rev organization\\xe2\\x80\\x99s information.\\n\\nRequest.\\n\\nThis endpoint expects an",
"title": "List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1547_KNOWLEDGE_NODE-394",
"text": "Rev organization\\xe2\\x80\\x99s information.\\n\\nQuery parameters.\\n\\naccount string Optional\\n\\nThe ID of account for which default Rev organization is to be fetched.\\n\\nid string Optional\\n\\nThe ID of the required Rev organization.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https://api.devrev.ai / rev-orgs.get\\n\\nRetrieves the Rev organization\\xe2\\x80\\x99s information.\\n\\nRequest.\\n\\nThis endpoint expects an",
"title": "Get Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1562_KNOWLEDGE_NODE-394",
"text": "Rev organization\\xe2\\x80\\x99s information.\\n\\nQuery parameters.\\n\\naccount string Optional\\n\\nThe ID of account for which default Rev organization is to be fetched.\\n\\nid string Optional\\n\\nThe ID of the required Rev organization.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https://api.devrev.ai / rev-orgs.get\\n\\nRetrieves the Rev organization\\xe2\\x80\\x99s information.\\n\\nRequest.\\n\\nThis endpoint expects an",
"title": "Get (Beta) — DevRev | Docs"
},
{
"id": "ART-1543_KNOWLEDGE_NODE-392",
"text": "Rev organization\\xe2\\x80\\x99s information.\\n\\nQuery parameters.\\n\\naccount string Optional\\n\\nThe ID of account for which default Rev organization is to be fetched.\\n\\nid string Optional\\n\\nThe ID of the required Rev organization.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https://api.devrev.ai / rev-orgs.get\\n\\nRetrieves the Rev organization\\xe2\\x80\\x99s information.\\n\\nRequest.\\n\\nThis endpoint expects an",
"title": "Metric Definitions List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1791_KNOWLEDGE_NODE-341",
"text": "the Rev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of Rev organization to delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev",
"title": "Self Delete — DevRev | Docs"
},
{
"id": "ART-1575_KNOWLEDGE_NODE-346",
"text": "the Rev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of Rev organization to delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1591_KNOWLEDGE_NODE-344",
"text": "the Rev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of Rev organization to delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1300_KNOWLEDGE_NODE-342",
"text": "the Rev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of Rev organization to delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1564_KNOWLEDGE_NODE-393",
"text": "Rev organization\\xe2\\x80\\x99s information.\\n\\nQuery parameters.\\n\\naccount string Optional\\n\\nThe ID of account for which default Rev organization is to be fetched.\\n\\nid string Optional\\n\\nThe ID of the required Rev organization.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https://api.devrev.ai / rev-orgs.get\\n\\nRetrieves the Rev organization\\xe2\\x80\\x99s information.\\n\\nRequest.\\n\\nThis endpoint expects an",
"title": "List (Beta) — DevRev | Docs"
},
{
"id": "ART-1788_KNOWLEDGE_NODE-342",
"text": "the Rev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of Rev organization to delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1409_KNOWLEDGE_NODE-3",
"text": "https://api.devrev.ai/rev-orgs.get \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer <token>\"\\n[/code] \\n \\nTry it\\n\\n200getExample\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"rev_org\": { \\n 3| \"id\": \"foo\", \\n 4| \"created_by\": { \\n 5| \"display_id\": \"foo\", \\n 6| \"id\": \"foo\", \\n 7| \"display_name\": \"foo\", \\n 8| \"display_picture\": { \\n 9| \"display_id\": \"foo\", \\n 10| \"id\": \"foo\", \\n 11|",
"title": "Get Rev Org — DevRev | Docs"
},
{
"id": "ART-1821_KNOWLEDGE_NODE-341",
"text": "application/json \" \\\\ > -d \\' { > \"id\": \"REV-AbCdEfGh\" > } \\'\\n200 Successful 1 { 2 \" key \" : \" value \" 3 }\\nAPI Reference rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nGET /",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1781_KNOWLEDGE_NODE-340",
"text": "the Rev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of Rev organization to delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1818_KNOWLEDGE_NODE-343",
"text": "the Rev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of Rev organization to delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev",
"title": "Sla Trackers Get Post — DevRev | Docs"
},
{
"id": "ART-1307_KNOWLEDGE_NODE-343",
"text": "the Rev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of Rev organization to delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1588_KNOWLEDGE_NODE-341",
"text": "application/json \" \\\\ > -d \\' { > \"id\": \"REV-AbCdEfGh\" > } \\'\\n200 Successful 1 { 2 \" key \" : \" value \" 3 }\\nAPI Reference rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nGET /",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1558_KNOWLEDGE_NODE-392",
"text": "organization.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https://api.devrev.ai / rev-orgs.get\\n\\nRetrieves the Rev organization\\xe2\\x80\\x99s information.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\n\\nThe ID of account for which default Rev organization is to be fetched.\\n\\nid string Optional\\n\\nThe ID of the required Rev organization.\\n\\nResponse.\\n\\nThis endpoint returns an",
"title": "Metric Definitions List (Beta) — DevRev | Docs"
},
{
"id": "ART-1560_KNOWLEDGE_NODE-395",
"text": "organization.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https://api.devrev.ai / rev-orgs.get\\n\\nRetrieves the Rev organization\\xe2\\x80\\x99s information.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\n\\nThe ID of account for which default Rev organization is to be fetched.\\n\\nid string Optional\\n\\nThe ID of the required Rev organization.\\n\\nResponse.\\n\\nThis endpoint returns an",
"title": "Assign (Beta) — DevRev | Docs"
},
{
"id": "ART-1214_KNOWLEDGE_NODE-1",
"text": "\"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{}\\' |\\n```\\n\\n[Try it](/api-reference/rev-orgs/get-post?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"rev_org\": { |\\n| 3 | \"id\": \"string\", |\\n| 4 | \"created_by\": { |\\n| 5 | \"display_id\": \"string\", |\\n| 6 | \"id\": \"string\", |\\n| 7 | \"display_name\": \"string\", |\\n| 8 | \"display_picture\": { |\\n| 9 | \"display_id\": \"string\", |\\n| 10 | \"id\": \"string\", |\\n| 11 | \"file\": { |\\n| 12 | \"type\": \"string\", |\\n| 13 | \"name\":",
"title": "Get Rev Org (POST) | DevRev | Docs"
},
{
"id": "ART-1605_KNOWLEDGE_NODE-343",
"text": "organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https:// api.devrev.ai / rev-orgs.list\\nGets the list of Rev organizations\\' information belonging to the authenticated user\\'s Dev Organization",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1821_KNOWLEDGE_NODE-342",
"text": "rev-orgs.get\\n$ curl -G https://api.devrev.ai/rev-orgs.get \\\\ > -H \" Authorization: Bearer <token> \" \\\\ > -d account=ACC-12345 \\\\ > -d id=REV-AbCdEfGh\\n200 Retrieved 1 { 2 \" rev_org \" : { 3 \" created_date \" : \" 2023-01-01T12:00:00Z \" , 4 \" display_id \" : \" display_id \" , 5 \" id \" : \" id \" , 6 \" modified_date \" : \" 2023-01-01T12:00:00Z \" , 7 \" display_name \" : \" display_name \" , 8 \" account \" : { 9 \" display_id \" : \" display_id \" , 10 \" id \" : \" id \" , 11 \" display_name \" : \" display_name \" 12 }",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1590_KNOWLEDGE_NODE-340",
"text": "https://api.devrev.ai/rev-orgs.get \\\\ > -H \" Authorization: Bearer <token> \" \\\\ > -H \" Content-Type: application/json \" \\\\ > -d \\' {} \\'\\n200 Successful 1 { 2 \" rev_org \" : { 3 \" created_date \" : \" 2023-01-01T12:00:00Z \" , 4 \" display_id \" : \" display_id \" , 5 \" id \" : \" id \" , 6 \" modified_date \" : \" 2023-01-01T12:00:00Z \" , 7 \" display_name \" : \" display_name \" , 8 \" account \" : { 9 \" display_id \" : \" display_id \" , 10 \" id \" : \" id \" , 11 \" display_name \" : \" display_name \" 12 } , 13 \"",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1588_KNOWLEDGE_NODE-342",
"text": "rev-orgs.get\\n$ curl -G https://api.devrev.ai/rev-orgs.get \\\\ > -H \" Authorization: Bearer <token> \" \\\\ > -d account=ACC-12345 \\\\ > -d id=REV-AbCdEfGh\\n200 Retrieved 1 { 2 \" rev_org \" : { 3 \" created_date \" : \" 2023-01-01T12:00:00Z \" , 4 \" display_id \" : \" display_id \" , 5 \" id \" : \" id \" , 6 \" modified_date \" : \" 2023-01-01T12:00:00Z \" , 7 \" display_name \" : \" display_name \" , 8 \" account \" : { 9 \" display_id \" : \" display_id \" , 10 \" id \" : \" id \" , 11 \" display_name \" : \" display_name \" 12 }",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1579_KNOWLEDGE_NODE-340",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1788_KNOWLEDGE_NODE-343",
"text": "organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-2933_KNOWLEDGE_NODE-12",
"text": "account you created, follow the steps listed below:\\n\\nGet the default rev org created along with the newly created account using the `rev-orgs.list` API:\\n\\n1. Make a GET/POST request to \\xe2\\x80\\x9c<https://api.devrev.ai/rev-orgs.list>\\xe2\\x80\\x9d using cURL with the `account` filter. Use the `external_ref` from the previous response as an `account` filter.\\n\\n ```\\n | | |\\n | --- | --- |\\n | $ | curl -X POST https://api.devrev.ai/rev-orgs.list \\\\ |\\n | > | -H \"Authorization:",
"title": "Account creation | DevRev | Docs"
},
{
"id": "ART-1818_KNOWLEDGE_NODE-344",
"text": "organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow",
"title": "Sla Trackers Get Post — DevRev | Docs"
},
{
"id": "ART-1300_KNOWLEDGE_NODE-343",
"text": "organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1543_KNOWLEDGE_NODE-393",
"text": "object.\\naccount string Optional\\n\\nThe ID of account for which default Rev organization is to be fetched.\\n\\nid string Optional\\n\\nThe ID of the required Rev organization.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://api.devrev.ai / rev-orgs.list\\n\\nGets the list of Rev organizations\\xe2\\x80\\x99 information belonging to the authenticated user\\xe2\\x80\\x99s Dev Organization which the user is also authorized to",
"title": "Metric Definitions List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1562_KNOWLEDGE_NODE-395",
"text": "object.\\naccount string Optional\\n\\nThe ID of account for which default Rev organization is to be fetched.\\n\\nid string Optional\\n\\nThe ID of the required Rev organization.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://api.devrev.ai / rev-orgs.list\\n\\nGets the list of Rev organizations\\xe2\\x80\\x99 information belonging to the authenticated user\\xe2\\x80\\x99s Dev Organization which the user is also authorized to",
"title": "Get (Beta) — DevRev | Docs"
},
{
"id": "ART-1564_KNOWLEDGE_NODE-394",
"text": "object.\\naccount string Optional\\n\\nThe ID of account for which default Rev organization is to be fetched.\\n\\nid string Optional\\n\\nThe ID of the required Rev organization.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://api.devrev.ai / rev-orgs.list\\n\\nGets the list of Rev organizations\\xe2\\x80\\x99 information belonging to the authenticated user\\xe2\\x80\\x99s Dev Organization which the user is also authorized to",
"title": "List (Beta) — DevRev | Docs"
},
{
"id": "ART-1215_KNOWLEDGE_NODE-4",
"text": "\"next_cursor\": \"string\", |\\n| 54 | \"prev_cursor\": \"string\" |\\n| 55 | } |\\n```\\n\\nGets the list of Rev organizations\\' information belonging to the\\nauthenticated user\\'s Dev Organization which the user is also authorized\\nto access.\\n\\n### Headers\\n\\nAuthorizationstringRequired\\n\\nBearer authentication of the form `Bearer <token>`, where token is your auth token.\\n\\n### Query parameters\\n\\ncreated\\\\_bylist of stringsOptional\\n\\nFilters by creator.\\n\\ncreated\\\\_date.afterstringOptional`format:",
"title": "List Rev Orgs | DevRev | Docs"
},
{
"id": "ART-1607_KNOWLEDGE_NODE-342",
"text": "fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nPOST / rev-orgs.get\\ncURL\\n$ curl -X POST https://api.devrev.ai/rev-orgs.get \\\\ > -H \" Authorization: Bearer <token> \" \\\\ > -H \" Content-Type: application/json \" \\\\ > -d \\' {} \\'\\n200 Successful 1 { 2 \" rev_org \" : { 3 \" created_date \" : \" 2023-01-01T12:00:00Z \" , 4 \" display_id \" : \" display_id \" , 5 \" id \" : \" id \" , 6 \" modified_date \" : \"",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1216_KNOWLEDGE_NODE-4",
"text": "|\\n| 50 | \"domain\": \"string\" |\\n| 51 | } |\\n| 52 | ], |\\n| 53 | \"next_cursor\": \"string\", |\\n| 54 | \"prev_cursor\": \"string\" |\\n| 55 | } |\\n```\\n\\nGets the list of Rev organizations\\' information belonging to the\\nauthenticated user\\'s Dev Organization which the user is also authorized\\nto access.\\n\\n### Headers\\n\\nAuthorizationstringRequired\\n\\nBearer authentication of the form `Bearer <token>`, where token is your auth token.\\n\\n### Request\\n\\nThis endpoint expects an",
"title": "List Rev Orgs (POST) | DevRev | Docs"
},
{
"id": "ART-1301_KNOWLEDGE_NODE-346",
"text": "rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1831_KNOWLEDGE_NODE-339",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1549_KNOWLEDGE_NODE-394",
"text": "object.\\naccount string Optional\\n\\nThe ID of account for which default Rev organization is to be fetched.\\n\\nid string Optional\\n\\nThe ID of the required Rev organization.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://api.devrev.ai / rev-orgs.list\\n\\nGets the list of Rev organizations\\xe2\\x80\\x99 information belonging to the authenticated user\\xe2\\x80\\x99s Dev Organization which the user is also authorized to",
"title": "List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1830_KNOWLEDGE_NODE-339",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1551_KNOWLEDGE_NODE-394",
"text": "object.\\naccount string Optional\\n\\nThe ID of account for which default Rev organization is to be fetched.\\n\\nid string Optional\\n\\nThe ID of the required Rev organization.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://api.devrev.ai / rev-orgs.list\\n\\nGets the list of Rev organizations\\xe2\\x80\\x99 information belonging to the authenticated user\\xe2\\x80\\x99s Dev Organization which the user is also authorized to",
"title": "Update (Beta) — DevRev | Docs"
},
{
"id": "ART-1792_KNOWLEDGE_NODE-344",
"text": "rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1547_KNOWLEDGE_NODE-395",
"text": "object.\\naccount string Optional\\n\\nThe ID of account for which default Rev organization is to be fetched.\\n\\nid string Optional\\n\\nThe ID of the required Rev organization.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://api.devrev.ai / rev-orgs.list\\n\\nGets the list of Rev organizations\\xe2\\x80\\x99 information belonging to the authenticated user\\xe2\\x80\\x99s Dev Organization which the user is also authorized to",
"title": "Get Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1786_KNOWLEDGE_NODE-341",
"text": "rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1780_KNOWLEDGE_NODE-341",
"text": "rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1785_KNOWLEDGE_NODE-340",
"text": "rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1823_KNOWLEDGE_NODE-339",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1804_KNOWLEDGE_NODE-346",
"text": "rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s",
"title": "Self — DevRev | Docs"
},
{
"id": "ART-1827_KNOWLEDGE_NODE-339",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1783_KNOWLEDGE_NODE-340",
"text": "rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s",
"title": "Locate — DevRev | Docs"
},
{
"id": "ART-1418_KNOWLEDGE_NODE-3",
"text": "Error\\n\\nPOST\\n\\n/rev-orgs.get\\n\\n[code]\\n\\n $| curl -X POST https://api.devrev.ai/rev-orgs.get \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer <token>\" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{}\\'\\n[/code] \\n \\nTry it\\n\\n200revOrgsGetPostExample\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"rev_org\": { \\n 3| \"id\": \"foo\", \\n 4| \"created_by\": { \\n 5| \"display_id\": \"foo\", \\n 6| \"id\": \"foo\", \\n 7|",
"title": "Get Rev Org (POST) — DevRev | Docs"
},
{
"id": "ART-1305_KNOWLEDGE_NODE-346",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1308_KNOWLEDGE_NODE-343",
"text": "rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1802_KNOWLEDGE_NODE-346",
"text": "rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1592_KNOWLEDGE_NODE-339",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1790_KNOWLEDGE_NODE-341",
"text": "rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1837_KNOWLEDGE_NODE-339",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1302_KNOWLEDGE_NODE-346",
"text": "rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1215_KNOWLEDGE_NODE-0",
"text": "b'List Rev Orgs | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[rev-orgs](/api-reference/rev-orgs/workspaces)\\n\\nList Rev Orgs\\n=============\\n\\nCopy page\\n\\nGET\\n\\nhttps://api.devrev.ai/rev-orgs.list\\n\\nGET\\n\\n/rev-orgs.list\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl https://api.devrev.ai/rev-orgs.list \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" |\\n```\\n\\n[Try",
"title": "List Rev Orgs | DevRev | Docs"
},
{
"id": "ART-1806_KNOWLEDGE_NODE-346",
"text": "rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s",
"title": "Self Post — DevRev | Docs"
},
{
"id": "ART-1409_KNOWLEDGE_NODE-6",
"text": "\"state\": \"active\" \\n 42| }, \\n 43| \"modified_date\": \"2023-01-01T12:00:00.000Z\", \\n 44| \"primary_rev_org\": { \\n 45| \"display_id\": \"foo\", \\n 46| \"id\": \"foo\", \\n 47| \"display_name\": \"foo\" \\n 48| }, \\n 49| \"domain\": \"foo\" \\n 50| } \\n 51| }\\n[/code] \\n \\n[Get Rev Org (POST)Up Next](/public/api-reference/rev-orgs/get-post)\\n\\n[Built",
"title": "Get Rev Org — DevRev | Docs"
},
{
"id": "ART-1835_KNOWLEDGE_NODE-339",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1779_KNOWLEDGE_NODE-342",
"text": "rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1215_KNOWLEDGE_NODE-1",
"text": "it](/api-reference/rev-orgs/list?explorer=true)\\n\\n200Retrieved\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"rev_orgs\": [ |\\n| 3 | { |\\n| 4 | \"id\": \"string\", |\\n| 5 | \"created_by\": { |\\n| 6 | \"display_id\": \"string\", |\\n| 7 | \"id\": \"string\", |\\n| 8 | \"display_name\": \"string\", |\\n| 9 | \"display_picture\": { |\\n| 10 | \"display_id\": \"string\", |\\n| 11 | \"id\": \"string\", |\\n| 12 | \"file\": { |\\n| 13 | \"type\": \"string\", |\\n| 14 | \"name\": \"string\", |\\n| 15 | \"size\": 1 |\\n| 16 | } |\\n| 17 | }, |\\n| 18",
"title": "List Rev Orgs | DevRev | Docs"
},
{
"id": "ART-1819_KNOWLEDGE_NODE-344",
"text": "rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s",
"title": "Sla Trackers Get — DevRev | Docs"
},
{
"id": "ART-1633_KNOWLEDGE_NODE-339",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1304_KNOWLEDGE_NODE-345",
"text": "rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1829_KNOWLEDGE_NODE-339",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1216_KNOWLEDGE_NODE-1",
"text": "\"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{}\\' |\\n```\\n\\n[Try it](/api-reference/rev-orgs/list-post?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"rev_orgs\": [ |\\n| 3 | { |\\n| 4 | \"id\": \"string\", |\\n| 5 | \"created_by\": { |\\n| 6 | \"display_id\": \"string\", |\\n| 7 | \"id\": \"string\", |\\n| 8 | \"display_name\": \"string\", |\\n| 9 | \"display_picture\": { |\\n| 10 | \"display_id\": \"string\", |\\n| 11 | \"id\": \"string\", |\\n| 12 | \"file\": { |\\n| 13 | \"type\": \"string\", |\\n|",
"title": "List Rev Orgs (POST) | DevRev | Docs"
},
{
"id": "ART-1833_KNOWLEDGE_NODE-339",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1216_KNOWLEDGE_NODE-0",
"text": "b'List Rev Orgs (POST) | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[rev-orgs](/api-reference/rev-orgs/workspaces)\\n\\nList Rev Orgs (POST)\\n====================\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/rev-orgs.list\\n\\nPOST\\n\\n/rev-orgs.list\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/rev-orgs.list \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -H",
"title": "List Rev Orgs (POST) | DevRev | Docs"
},
{
"id": "ART-1636_KNOWLEDGE_NODE-339",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1791_KNOWLEDGE_NODE-342",
"text": "organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow",
"title": "Self Delete — DevRev | Docs"
},
{
"id": "ART-1825_KNOWLEDGE_NODE-339",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1509_KNOWLEDGE_NODE-341",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "Prepare — DevRev | Docs"
},
{
"id": "ART-1789_KNOWLEDGE_NODE-343",
"text": "organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1595_KNOWLEDGE_NODE-342",
"text": "Reference rev-orgs Delete.\\n\\nPOST https:// api.devrev.ai / rev-orgs.delete\\nDeletes the Rev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of Rev organization to delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1781_KNOWLEDGE_NODE-341",
"text": "organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1832_KNOWLEDGE_NODE-339",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1834_KNOWLEDGE_NODE-339",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1575_KNOWLEDGE_NODE-347",
"text": "organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1213_KNOWLEDGE_NODE-1",
"text": "it](/api-reference/rev-orgs/get?explorer=true)\\n\\n200Retrieved\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"rev_org\": { |\\n| 3 | \"id\": \"string\", |\\n| 4 | \"created_by\": { |\\n| 5 | \"display_id\": \"string\", |\\n| 6 | \"id\": \"string\", |\\n| 7 | \"display_name\": \"string\", |\\n| 8 | \"display_picture\": { |\\n| 9 | \"display_id\": \"string\", |\\n| 10 | \"id\": \"string\", |\\n| 11 | \"file\": { |\\n| 12 | \"type\": \"string\", |\\n| 13 | \"name\": \"string\", |\\n| 14 | \"size\": 1 |\\n| 15 | } |\\n| 16 | }, |\\n| 17 | \"email\":",
"title": "Get Rev Org | DevRev | Docs"
},
{
"id": "ART-1803_KNOWLEDGE_NODE-344",
"text": "organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1824_KNOWLEDGE_NODE-339",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1591_KNOWLEDGE_NODE-345",
"text": "organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1213_KNOWLEDGE_NODE-0",
"text": "b'Get Rev Org | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[rev-orgs](/api-reference/rev-orgs/workspaces)\\n\\nGet Rev Org\\n===========\\n\\nCopy page\\n\\nGET\\n\\nhttps://api.devrev.ai/rev-orgs.get\\n\\nGET\\n\\n/rev-orgs.get\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl https://api.devrev.ai/rev-orgs.get \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" |\\n```\\n\\n[Try",
"title": "Get Rev Org | DevRev | Docs"
},
{
"id": "ART-1655_KNOWLEDGE_NODE-339",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1805_KNOWLEDGE_NODE-344",
"text": "organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1306_KNOWLEDGE_NODE-344",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1801_KNOWLEDGE_NODE-345",
"text": "organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1822_KNOWLEDGE_NODE-339",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1651_KNOWLEDGE_NODE-339",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1409_KNOWLEDGE_NODE-1",
"text": "__\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[API Reference](/public/api-reference/getting-started)[Rev Orgs](/public/api-reference/rev-orgs/create)\\n\\n# Get Rev Org\\n\\nGET\\n\\nhttps://api.devrev.ai/rev-orgs.get\\n\\nTry it\\n\\nRetrieves the Rev organization\\xe2\\x80\\x99s information.\\n\\n### Query parameters\\n\\naccountstringOptional`format: \"id\"`\\n\\nThe ID of account for which default Rev organization is to be",
"title": "Get Rev Org — DevRev | Docs"
},
{
"id": "ART-1593_KNOWLEDGE_NODE-347",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1420_KNOWLEDGE_NODE-5",
"text": "\\n ---|--- \\n >| -H \"Authorization: Bearer <token>\" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{}\\'\\n[/code] \\n \\nTry it\\n\\n200revOrgsListPostExample\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"rev_orgs\": [ \\n 3| { \\n 4| \"id\": \"foo\", \\n 5| \"created_by\": { \\n 6| \"display_id\": \"foo\", \\n 7| \"id\": \"foo\", \\n 8| \"display_name\": \"foo\", \\n 9| \"display_picture\": { \\n 10|",
"title": "List Rev Orgs (POST) — DevRev | Docs"
},
{
"id": "ART-1214_KNOWLEDGE_NODE-0",
"text": "b'Get Rev Org (POST) | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[rev-orgs](/api-reference/rev-orgs/workspaces)\\n\\nGet Rev Org (POST)\\n==================\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/rev-orgs.get\\n\\nPOST\\n\\n/rev-orgs.get\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/rev-orgs.get \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -H",
"title": "Get Rev Org (POST) | DevRev | Docs"
},
{
"id": "ART-1650_KNOWLEDGE_NODE-339",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1303_KNOWLEDGE_NODE-344",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "Export Post — DevRev | Docs"
},
{
"id": "ART-1590_KNOWLEDGE_NODE-338",
"text": "object.\\nid string Required\\nThe ID of Rev organization to delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1639_KNOWLEDGE_NODE-339",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "Export Post — DevRev | Docs"
},
{
"id": "ART-1213_KNOWLEDGE_NODE-3",
"text": "33 | \"file\": { |\\n| 34 | \"type\": \"string\", |\\n| 35 | \"name\": \"string\", |\\n| 36 | \"size\": 1 |\\n| 37 | } |\\n| 38 | }, |\\n| 39 | \"email\": \"string\", |\\n| 40 | \"full_name\": \"string\", |\\n| 41 | \"state\": \"active\" |\\n| 42 | }, |\\n| 43 | \"modified_date\": \"2023-01-01T12:00:00.000Z\", |\\n| 44 | \"primary_rev_org\": { |\\n| 45 | \"display_id\": \"string\", |\\n| 46 | \"id\": \"string\", |\\n| 47 | \"display_name\": \"string\" |\\n| 48 | }, |\\n| 49 | \"domain\": \"string\" |\\n| 50 | } |\\n| 51 | } |\\n```\\n\\nRetrieves the Rev",
"title": "Get Rev Org | DevRev | Docs"
},
{
"id": "ART-1655_KNOWLEDGE_NODE-338",
"text": "object.\\nid string Required\\nThe ID of Rev organization to delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1838_KNOWLEDGE_NODE-339",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1826_KNOWLEDGE_NODE-339",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1825_KNOWLEDGE_NODE-338",
"text": "object.\\nid string Required\\nThe ID of Rev organization to delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1833_KNOWLEDGE_NODE-338",
"text": "object.\\nid string Required\\nThe ID of Rev organization to delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1633_KNOWLEDGE_NODE-338",
"text": "object.\\nid string Required\\nThe ID of Rev organization to delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1651_KNOWLEDGE_NODE-338",
"text": "object.\\nid string Required\\nThe ID of Rev organization to delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1605_KNOWLEDGE_NODE-342",
"text": "to any.\\nAPI Reference rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1609_KNOWLEDGE_NODE-339",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1609_KNOWLEDGE_NODE-338",
"text": "object.\\nid string Required\\nThe ID of Rev organization to delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1643_KNOWLEDGE_NODE-339",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1782_KNOWLEDGE_NODE-340",
"text": "object.\\nid string Required\\nThe ID of Rev organization to delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1787_KNOWLEDGE_NODE-343",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1649_KNOWLEDGE_NODE-338",
"text": "object.\\nid string Required\\nThe ID of Rev organization to delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference rev-orgs Get.\\n\\nGET https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nQuery parameters.\\n\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1782_KNOWLEDGE_NODE-341",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1653_KNOWLEDGE_NODE-339",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1654_KNOWLEDGE_NODE-339",
"text": "object\\nShow 17 properties\\nAPI Reference rev-orgs Get Post.\\n\\nPOST https:// api.devrev.ai / rev-orgs.get\\nRetrieves the Rev organization\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of account for which default Rev organization is to be fetched.\\nid string Optional\\nThe ID of the required Rev organization.\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_org object\\nShow 17 properties\\nAPI Reference rev-orgs List.\\n\\nGET https://",
"title": "List — DevRev | Docs"
}
] |
45ae3491-e386-45de-9c7d-8c257b0b0236
|
see how many conversations are resolved in a day
|
[
{
"id": "ART-1968_KNOWLEDGE_NODE-26",
"text": "**Active conversations per customer**\\n\\n The number of conversations per customer that are Open or In Progress.\\n* **Active conversations per part**\\n\\n The number of conversations per part that are Open or In Progress.\\n\\nConversation distribution\\n-------------------------\\n\\n* **Conversations linked to tickets**\\n\\n The percentage of tickets linked to conversations against standalone tickets.\\n* **Conversations created vs. closed**\\n\\n The trend of conversations created against those",
"title": "Conversation insights | Support analytics | Computer for Support Teams | DevRev"
}
] |
4c0a9e54-762a-4139-a240-a7fd790dcfe0
|
add URL to display AI bot
|
[
{
"id": "ART-15716_KNOWLEDGE_NODE-10",
"text": "work perfectly in a mobile WebView\\n\\nSetting Up the PluG Widget on a Website\\n\\nGo to your DevRev workspace, open PluG settings, configure the widget, and copy the provided JavaScript snippet. Paste it before the closing tag in your website\\xe2\\x80\\x99s HTML. Deploy your site and the widget should appear.\\n\\n[PLuG installation steps](https://developer.devrev.ai/public/sdks/web/installation)\\n\\nRenaming the \\'DevRev Turing\\' Chatbot - asked in slack channel\\n\\nTroubleshooting PluG AI",
"title": "Support queries related playbook"
},
{
"id": "ART-4199_KNOWLEDGE_NODE-28",
"text": "**Trigger URL** that is displayed.\\n6. Paste the Trigger URL under **Enable Events** in the custom Slack bot.\\n\\n[PreviousTicket linked issues comment sync](/docs/automations/ticket-linked-issues-comment-sync)[NextIntegrate](/docs/integrate)\\n\\n#### On this page\\n\\n* [Install](#install)\\n* [Configure the custom Slack bot](#configure-the-custom-slack-bot)\\n* [Configure DevRev](#configure-devrev)\\n\\n[Enterprise grade security to protect customer data\\n\\nLearn more about",
"title": "Slack message agent | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2063_KNOWLEDGE_NODE-30",
"text": "there won't be any interaction.\\n9. Define rules as described in the [Create Rules](#create-rules) section.\\n\\nCreate rules\\n------------\\n\\nThe rules enable you to define when your customers should receive nudges.\\n\\n1. Click the **Rules** tab.\\n2. If you want to send the nudge to the customer only when they end up on a specific URL on your website, you can use this setting. To add a page rule, click **+ Page rule** and then add the URL. The URL can be an exact URL or a partial URL, depending",
"title": "Nudges | Computer for Your Customers | DevRev"
},
{
"id": "ART-2894_KNOWLEDGE_NODE-5",
"text": "window.plugSDK.toggleSearchAgent(); \\n ---\\n[/code] \\n \\nTo prefill search input from outside the window, call the following method:\\n\\n[code]\\n\\n window.plugSDK.prefillSearchQuery(query:\"string\") \\n ---\\n[/code] \\n \\nYou should now have the PLuG search widget installed on your website. Facing some issues? Reach out to us through our own PLuG chat widget from the bottom right of your screen.\\n\\nOnce the widget is installed on your website, every user who visits your website is",
"title": "Install PLuG search — DevRev | Docs"
},
{
"id": "ART-2893_KNOWLEDGE_NODE-2",
"text": "2| type=\"text/javascript\" \\n 3| src=\"https://plug-platform.devrev.ai/static/plug.js\" \\n 4| ></script>\\n[/code] \\n \\nPlace the following code in the `<body>` section of your HTML page:\\n\\n[code]\\n\\n 1| <script> \\n ---|--- \\n 2| window.plugSDK.init({ \\n 3| // Please ensure you replace the app_id with your unique app id \\n 4| app_id: \"<your_unique_app_id>\", \\n 5| }); \\n 6| </script>\\n[/code] \\n \\nThe PLuG widget should now be installed on",
"title": "Install the Web SDK — DevRev | Docs"
}
] |
09eb4797-a77e-4dee-acaf-32f4101f8490
|
difference between a ticket and an issue
|
[
{
"id": "ART-15716_KNOWLEDGE_NODE-8",
"text": "for TicketsWe have a summarize option (it would resemble sparkle symbol) in the top right corner of the ticket view, which uses the ticket content to summarize the ticket\\n\\n7. Difference between Issues and Tickets\\n\\nTickets\\xc2\\xa0are for customer support\\xe2\\x80\\x94tracking requests, problems, or questions from customers or prospects.\\n\\nIssues\\xc2\\xa0are internal work items for developers\\xe2\\x80\\x94used to improve the product, fix bugs, or implement features. Issues can be linked to",
"title": "Support queries related playbook"
},
{
"id": "ART-3905_KNOWLEDGE_NODE-27",
"text": "|\\n| --- | --- | --- |\\n| Issue | Ticket | \\xe2\\x9c\\x85 |\\n| Private Comment on Issue | Internal Comment on Ticket | \\xe2\\x9c\\x85 |\\n| Public Comment on Issue | Customer Comment on Ticket | \\xe2\\x9c\\x85 |\\n| Label on Issue | Tag on Ticket | \\xe2\\x9c\\x85 |\\n| Link between Issues | Link between Tickets | \\xe2\\x9c\\x85 |\\n| Attachment on Issue | Attachment on Ticket | \\xe2\\x9c\\x85 |\\n| Status Category/States of Issue | State/Stage of Ticket | \\xe2\\x9c\\x85 |\\n| Workflow of Issue | Stage Transition",
"title": "Jira Service Management AirSync | AirSync | Snap-ins | DevRev"
},
{
"id": "ART-1002_KNOWLEDGE_NODE-1",
"text": "\\xe2\\x86\\x92 Issues\\n Items to track customer requests/problems \\xe2\\x86\\x92 Tickets\\n\\n\\nGiven the converged nature of the DevRev platform, we have both Tickets, and Issues, so when do you use what? The answer is \\xe2\\x80\\x9cit depends\\xe2\\x80\\x9d on what your role is on the part you\\xe2\\x80\\x99re creating the work item on. In general, issues should be restricted to those individuals that either own or contribute to a part. Tickets should be used for all customer/consumer (internal or",
"title": "Tickets, Issues: When to Use Each"
},
{
"id": "ART-1946_KNOWLEDGE_NODE-27",
"text": "synchronous or near-synchronous discussion that may be escalated to a ticket. Conversations are part of [Computer for Support Teams](./support).\\n* A *ticket* is a work item created by the customer or consumer. Tickets are part of [Computer for Support Teams](./support).\\n* An *issue* is a work item created by the builder or maintainer. Issues are part of [Computer for Builders](./build).\\n* An *enhancement* is the parent of multiple issues that lead to a desired change to the product.",
"title": "Core concepts | Computer by DevRev | DevRev"
},
{
"id": "ART-1947_KNOWLEDGE_NODE-33",
"text": "language is reflected in issues.\\n\\nIssues\\n------\\n\\nLater on, a software engineer may start work on this ticket by creating an issue and breaking that issue into smaller pieces with tasks. An issue describes what the developer will work on and is created or accepted by someone who owns or works on the associated part of the product. This distinction allows developers to break up a ticket from an external user into issues as they see fit and delegate the work to other team members as",
"title": "Apps | Computer by DevRev | DevRev"
},
{
"id": "ART-1002_KNOWLEDGE_NODE-4",
"text": "hold value\\n reduces noise as only valid issues are created/tracked\\n unifies the triage process for escalations between tickets and issues\\n\\n\\nTL;DR\\n\\n\\n If you work on a part, you create issues\\n If you are a consumer/customer of a part, you create tickets\\n\\n'",
"title": "Tickets, Issues: When to Use Each"
},
{
"id": "ART-1947_KNOWLEDGE_NODE-34",
"text": "necessary.\\n\\n> Example: \"Feature A on product Y exhibited unexpected behavior. This is a defect and needs to be fixed.\"\\n\\nTickets and issues are linked in many-to-many relationships. It may require multiple issues to resolve a ticket, or one issue may resolve multiple tickets if different external users experience and describe the same behavior in different ways.\\n\\nWork/state relationships\\n------------------------\\n\\nThe following figure shows how the various work object types",
"title": "Apps | Computer by DevRev | DevRev"
},
{
"id": "ART-1242_KNOWLEDGE_NODE-0",
"text": "b'Tickets and issues | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[works](/api-reference/works/tickets-and-issues)\\n\\nTickets and issues\\n==================\\n\\nCopy page\\n\\n`works` endpoint\\n\\n\\xe2\\x84\\xb9\\xef\\xb8\\x8f A work item is a record of some work that has to be done for a customer (ticket) or for another builder or maintainer of a part (issue).\\n\\n\\xf0\\x9f\\x93\\x8c For more information",
"title": "Tickets and issues | DevRev | Docs"
},
{
"id": "ART-1002_KNOWLEDGE_NODE-2",
"text": "external) items.\\n\\nThe following figure shows a decision tree that will help you identify what work type you should be using (this is not global but part specific):\\n\\n\\n\\nFor example, if I work on part foo, I can create issues on it. However, if I am a consumer of part bar I would create tickets which would then be triaged and potentially escalated into an issue by that team.\\n\\nWhy\\n\\n\\n Noise and context switching kill productivity\\n\\n\\nHistorically, a huge pain point has been that any",
"title": "Tickets, Issues: When to Use Each"
},
{
"id": "ART-1979_KNOWLEDGE_NODE-37",
"text": "filters and **Group** conditions across various vistas in DevRev to track specific work, capacity, and more.\\n\\nYou can add custom attributes to tickets to track additional information. For more information on custom attributes, see [object customization](./object-customization).\\n\\nIssues are attached to tickets in order to track efforts with product priorities.\\n\\nCreate a ticket\\n---------------\\n\\n1. Go to **Support** > **Tickets** from the sidebar on the left.\\n2. Click **New Ticket** on",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-1447_KNOWLEDGE_NODE-0",
"text": "b'[](/public/api-reference/works/tickets-and-issues)\\n\\nPublic\\n\\n[API Reference](/public/api-reference/getting-started)[Works](/public/api-reference/works/tickets-and-issues)\\n\\n#\\n\\nTickets and issues\\n\\n`works` endpoint\\n\\n\\xe2\\x84\\xb9\\xef\\xb8\\x8f A work item is a record of some work that has to be done for a customer (ticket) or for another builder or maintainer of a part (issue).\\n\\n\\xf0\\x9f\\x93\\x8c For more information about work items, refer to",
"title": "Tickets and issues — DevRev | Docs"
},
{
"id": "ART-15716_KNOWLEDGE_NODE-9",
"text": "tickets for escalation or tracking.\\n\\nQuick summary: If you\\xe2\\x80\\x99re a customer, you create tickets. If you\\xe2\\x80\\x99re a developer, you create issues.PLuG widget and SDK\\n\\nIntegrating PluG in React Native Expo Apps\\n\\nPluG is designed for web, but you can embed it in a React Native Expo app using react-native-webview. Install the package with npx expo install react-native-webview, then use a WebView component to load your PluG widget\\xe2\\x80\\x99s URL. Some advanced features may not",
"title": "Support queries related playbook"
},
{
"id": "ART-2048_KNOWLEDGE_NODE-27",
"text": "allows you to create parent/child relationships between issues, you cannot do the same with tickets. If your workflow requires manual creation of parent/child relationships in DevRev work items, you should use issues. If that is not a requirement and tickets are preferred for another reason, you can specify tickets as the target for ClickUp tasks.\\n\\nImport from ClickUp\\n-------------------\\n\\nFollow the steps below to import from ClickUp:\\n\\n1. In **Marketplace**, search for **ClickUp** and",
"title": "ClickUp AirSync | AirSync | Snap-ins | DevRev"
},
{
"id": "ART-1981_KNOWLEDGE_NODE-34",
"text": "ticket.\\n* Make sure all tickets have the customer org field populated.\\n* Cancel any internal ticket without a customer org that has been created by a developer. Ask them to create an issue instead.\\n* If a customer raises a feature request that aligns with the product strategy, but needs significant development effort and will not be delivered in the near future, move it to the *accepted* stage, rather than keeping the ticket open. Inform the customer accordingly.\\n* If a customer reports a",
"title": "Support best practices | Computer for Support Teams | DevRev"
},
{
"id": "ART-1947_KNOWLEDGE_NODE-25",
"text": "systems, important details that help define the *why* behind work is lost.\\n\\n\\xf0\\x9f\\x8e\\xa5 Video: Convergence: Bringing work together\\n\\nBy linking work items\\xe2\\x80\\x94conversations and tickets for support, issues and enhancements for build\\xe2\\x80\\x94together, DevRev preserves context. That context defines the problem and requirements for anyone who works on this issue. Moreover, both tickets and issues are always associated with [parts](/docs/product/parts), tying them to the overall",
"title": "Apps | Computer by DevRev | DevRev"
}
] |
1cded992-0e4f-4eca-a709-3af948f6c996
|
how to create canned messages
|
[
{
"id": "ART-1874_KNOWLEDGE_NODE-1",
"text": "https://api.devrev.ai/content-template.create \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{ |\\n| > | \"body_translations\": {}, |\\n| > | \"title_translations\": {} |\\n| > | }\\' |\\n```\\n\\n[Try it](/beta/api-reference/notifications/content-template-create?explorer=true)\\n\\n201Created\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"content_template\": { |\\n| 3 | \"created_by\": { |\\n| 4 | \"display_id\": \"string\", |\\n| 5 | \"id\":",
"title": "Create Content Template | DevRev | Docs"
},
{
"id": "ART-1964_KNOWLEDGE_NODE-25",
"text": "articles at the workspace level.\\n\\nManage templates\\n----------------\\n\\nTo create, edit, use, and delete templates, go to [**Settings** > **Templates**](https://app.devrev.ai/devrev/settings/record-template).\\n\\nCreating templates\\n------------------\\n\\n1. Click **+ Templates**.\\n2. Enter a **Name** (required) and an optional **Description** for the template.\\n3. Select the **Object Type** (*Article*, *Issues*, *Tickets*) under which the template will be categorized.\\n4. Click **Next**.\\n5.",
"title": "Templates | Computer by DevRev | DevRev"
}
] |
06f139d9-5b22-42bb-b7f0-a6a21403522b
|
cannot update ticket title after multiple refreshes
|
[
{
"id": "ART-4965_KNOWLEDGE_NODE-25",
"text": "permitted. This includes restrictions on RTE access, field updates, object linking, and other changes, ensuring ticket integrity and compliance with data governance standards\\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 **Ticket Immutability** and click **Install**.\\n3. Set-up the snap-in\\'s configurations.\\n4. Click **Save > Install**",
"title": "Ticket Immutability | Automate | Snap-ins | DevRev"
}
] |
8a00ab3d-b690-43be-8bad-ea5ab98f96ae
|
private emails not showing in conversation, only business emails
|
[
{
"id": "ART-3207_KNOWLEDGE_NODE-44",
"text": "sharing settings:\\n\\n* **Signature**: Added to all personal emails sent via DevRev\\n* **Share files as links**: Ensures deliverability of attachments via secure links\\n\\n3. Configure email forwarding for your email provider\\n-----------------------------------------------------\\n\\nFor conversation or tickets to be created in DevRev, the emails must be forwarded from your email provider. The forwarding instructions are available **under the Installation section** of the Email Integration",
"title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-1478_KNOWLEDGE_NODE-47",
"text": "only, not as a direct mailbox to which anyone can send their emails. Emails received (either directly or by forwarding) from senders who aren\\xe2\\x80\\x99t in the allowlist are dropped. There are a few exceptions to this like Google\\xe2\\x80\\x99s forwarding confirmation emails.\\n\\nThe allowlist can either contain an email address or an entire domain. Strict matching is done for domains, meaning that subdomains are not included.\\n\\n#####\\n\\nThe email protocol regarding forwarding is not very well",
"title": "Event sources — DevRev | Docs"
},
{
"id": "ART-1265_KNOWLEDGE_NODE-8",
"text": "\"don:core:dvrv-us-1:devo/<dev-org-id>:conversation/172:comment/xqsvvdwvt6hjw\", |\\n| 17 | \"object\": \"don:core:dvrv-us-1:devo/<dev-org-id>:conversation/172\", |\\n| 18 | \"object_type\": \"conversation\", |\\n| 19 | \"visibility\": \"private\" |\\n| 20 | } |\\n| 21 | } |\\n```\\n\\nYou can check the object to which you sent a message in the UI. It\\xe2\\x80\\x99s visible to the creator and the users you added in `private_to`.\\n![]()\\n\\nSummary\\n-------\\n\\nIn this tutorial, you learned how to post a comment on the",
"title": "Restricted messages on a timeline | DevRev | Docs"
},
{
"id": "ART-1284_KNOWLEDGE_NODE-41",
"text": "forwarding address is `[email protected]`, you should set up email\\nforwarding from `[email protected]` to `[email protected]`.\\n\\n##### \\n\\nOnly emails forwarded from the allowlist of emails/domains are emitted as events. Hence, this event source should be used for email forwarding only, not as a direct mailbox to which anyone can send their emails. Emails received (either directly or by forwarding) from senders who aren\\xe2\\x80\\x99t in the allowlist are dropped. There are a",
"title": "Event sources | DevRev | Docs"
},
{
"id": "ART-1284_KNOWLEDGE_NODE-42",
"text": "few exceptions to this like Google\\xe2\\x80\\x99s forwarding confirmation emails.\\n\\nThe allowlist can either contain an email address or an entire domain. Strict matching is done for domains, meaning that subdomains are not included.\\n\\n##### \\n\\nThe email protocol regarding forwarding is not very well defined. We\\xe2\\x80\\x99ve tested forwarding from common sources like Gmail, Google Groups, and Outlook Inbox. However, if you\\xe2\\x80\\x99re having issues with email forwarding on other providers,",
"title": "Event sources | DevRev | Docs"
},
{
"id": "ART-15778_KNOWLEDGE_NODE-0",
"text": "b\"Users are not automatically merged if their emails were missing in the initial import due to the external system's security, visibility or permission restrictions. If a later sync to DevRev contains the email addresses for these shadow users, they will not be updated. This means that for such cases, manual merging will have to be done.\"",
"title": "Updating Emails of Shadow Users"
},
{
"id": "ART-1471_KNOWLEDGE_NODE-3",
"text": "[<list of user IDs>], \\n 6| \"type\": \"timeline_comment\" \\n 7| }\\n[/code] \\n \\n * `object` must be of type string and contains `<partition>`, `<dev-org-id>`, and `<object-id>`.\\n * `body` is of type string and contains the actual message to be posted.\\n * `visibility` is set to `private` in order for the message to be visible only to users, `internal` is visible with the Dev organization, `external` is visible to the Dev organzation and customers, and `public` is visible",
"title": "Restricted messages on a timeline — DevRev | Docs"
},
{
"id": "ART-1478_KNOWLEDGE_NODE-46",
"text": "event source is deployed, the instructions show a unique email address. You have to set up forwarding in your original email inbox or Google Group to this email address. In the example above, if the forwarding address is `[email protected]`, you should set up email forwarding from `[email protected]` to `[email protected]`.\\n\\n#####\\n\\nOnly emails forwarded from the allowlist of emails/domains are emitted as events. Hence, this event source should be used for email forwarding",
"title": "Event sources — DevRev | Docs"
}
] |
19809331-3253-41ce-91f6-2cac79212cc5
|
set Priority field to Priority 3 only for tickets created from portal
|
[
{
"id": "ART-17231_KNOWLEDGE_NODE-66",
"text": "`support` | Support | - |\\n\\n**priority**\\n\\n| Value | Name | Description |\\n| --- | --- | --- |\\n| `P0` | P0 | - |\\n| `P1` | P1 | - |\\n| `P2` | P2 | - |\\n\\n**stage**\\n\\n| Value | Name | Description |\\n| --- | --- | --- |\\n| `archived` | Archived | - |\\n| `hold` | Hold | - |\\n| `needs_response` | Needs Response | - |\\n| `new` | New | - |\\n| `resolved` | Resolved | - |\\n| `suspended` | Suspended | - |\\n| `waiting_on_user` | Waiting On User | - |\\n\\n[\\xe2\\x96\\xb2",
"title": "Supported DevRev object types | DevRev | Docs"
}
] |
0c76733a-1dd4-4ae9-865c-db9ad1f9cf55
|
how to create a vista
|
[
{
"id": "ART-16173_KNOWLEDGE_NODE-0",
"text": "b'Create Vista | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nBeta\\n\\nBeta\\n\\nBeta\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/beta/api-reference/accounts/create)[vistas](/beta/api-reference/vistas/create)\\n\\nCreate Vista\\n============\\n\\nBeta\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/vistas.create\\n\\nPOST\\n\\n/vistas.create\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/vistas.create \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -H",
"title": "Create Vista | DevRev | Docs"
},
{
"id": "ART-16173_KNOWLEDGE_NODE-1",
"text": "\"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{ |\\n| > | \"filter\": {} |\\n| > | }\\' |\\n```\\n\\n[Try it](/beta/api-reference/vistas/create?explorer=true)\\n\\n201Created\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"vista\": { |\\n| 3 | \"created_by\": { |\\n| 4 | \"display_id\": \"string\", |\\n| 5 | \"id\": \"string\", |\\n| 6 | \"display_name\": \"string\", |\\n| 7 | \"display_picture\": { |\\n| 8 | \"display_id\": \"string\", |\\n| 9 | \"id\": \"string\", |\\n| 10 | \"file\": { |\\n| 11 | \"type\": \"string\", |\\n| 12 |",
"title": "Create Vista | DevRev | Docs"
},
{
"id": "ART-16173_KNOWLEDGE_NODE-5",
"text": "69 | } |\\n| 70 | } |\\n| 71 | ], |\\n| 72 | \"items\": [ |\\n| 73 | { |\\n| 74 | \"display_id\": \"string\", |\\n| 75 | \"id\": \"string\", |\\n| 76 | \"display_name\": \"string\" |\\n| 77 | } |\\n| 78 | ] |\\n| 79 | } |\\n| 80 | } |\\n```\\n\\nCreates a vista.\\n\\n### Headers\\n\\nAuthorizationstringRequired\\n\\nBearer authentication of the form `Bearer <token>`, where token is your auth token.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\nvistas-create-request-dynamic-vistaobjectRequired\\n\\nShow 1 variants\\n\\n###",
"title": "Create Vista | DevRev | Docs"
},
{
"id": "ART-1949_KNOWLEDGE_NODE-25",
"text": "**Tickets**; **Build > Issues** and **Now, Next, Later**; and **Product > Parts**. Depending on the type of object there are different options for querying, sorting, customizing, and grouping.\\n\\n\\xf0\\x9f\\x8e\\xa5 Video: Applying filters to Vistas\\n\\nCreate a vista\\n--------------\\n\\n1. Select the object you want to make a list of, for example, tickets.\\n2. Make a change to the default view of the object by applying a filter, sorting, grouping, or customizing. A **Save as** button appears in the",
"title": "Vistas | Computer by DevRev | DevRev"
}
] |
dd017d44-f610-4049-b57c-576cb0841525
|
create ticket conversation for every new slack message
|
[
{
"id": "ART-2035_KNOWLEDGE_NODE-41",
"text": "Slack threads, all the messages from both Slack threads reach only the primary ticket in DevRev, while messages from DevRev only sync to the primary ticket\\xe2\\x80\\x99s Slack thread.\\n* If only one ticket has a syncing Slack thread, that thread syncs with the primary ticket.\\n* No messages from the duplicate ticket sync to Slack.\\n* If a ticket is immutable but receives a new customer message in its Slack thread, a follow-up ticket is automatically created for future discussions.\\n\\n### New",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-6174_KNOWLEDGE_NODE-28",
"text": "tickets\\n--------------------------------\\n\\n**Manual conversion**\\n\\nGo to the conversation record pane and select **Convert to Ticket** to create a new ticket from the conversation.\\n\\n![]()\\n\\n**Automated conversion via workflows**\\n\\nSet up automated [workflows](./workflow-engine) to convert conversations to tickets based on specific triggers:\\n\\n* When a conversation meets defined criteria\\n* When the AI agent identifies an issue requiring escalation\\n* According to custom business",
"title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev"
},
{
"id": "ART-12391_KNOWLEDGE_NODE-26",
"text": "with *Conversation created* or *Ticket\\n created*.\\n\\n This trigger is whenever a conversation or ticket gets created by your\\n customers from Portal or Plug, or any of your integration which supports\\n conversation syncing, like Slack, WhatsApp, or email. You can find the\\n integrations in our marketplace.\\n2. Add the *Talk to agent* step as the next action. Fill all the required values\\n of this step. The values needed to fill here are explained below.\\n3. Deploy the",
"title": "Conversational workflows | Workflows | Computer by DevRev | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-34",
"text": "minutes after a conversation is created.\\n* Any new message sent directly in the channel within this time frame is appended to the existing conversation.\\n* A new direct message from the customer resets the roll window timer.\\n* Any message sent from DevRev will be synced to the thread of the first message that initiated the conversation.\\n* Only messages within the thread of the originating message of the conversation are synced.\\n* Messages within Slack threads of follow-ups sent directly to",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-46",
"text": "**Auto-create incidents from Slack channels**, which automatically creates an incident for every direct message posted in specified Slack channels.\\n\\nThe first two options will open a pop-up modal with a new incident form, with some fields pre-populated based on the context.\\n\\n### Sync options\\n\\nIncidents support syncing messages both within a dedicated Slack thread and across an entire Slack channel, including all associated threads. The sync target is determined by the **Sync for new",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-4199_KNOWLEDGE_NODE-27",
"text": "message.channels.\\n7. Add this custom app and the **DevRev Slack Bot** into the Slack channel from which you want to create the DevRev object.\\n\\nConfigure DevRev\\n----------------\\n\\n1. Add the Slack Signing Secret and Slack Bot Token copied from the custom Slack bot app.\\n2. Add the channel IDs for either incidents, tickets or issues.\\n3. Click the respective buttons to enable the sync between threads.\\n4. Select the part ID to associate a particular part.\\n5. Click **Save** and copy the",
"title": "Slack message agent | Automate | Snap-ins | DevRev"
},
{
"id": "ART-4199_KNOWLEDGE_NODE-25",
"text": "DevRev.\\n\\n![]()\\n\\nFor more information, refer to the [Slack message agent](https://marketplace.devrev.ai/slack-message-agent) on the DevRev marketplace.\\n\\nInstall\\n-------\\n\\n1. Install the DevRev [Slack app](/docs/integrations/slack).\\n2. Install the Slack message agent in your org.\\n\\nConfigure the custom Slack bot\\n------------------------------\\n\\n1. Go to [Slack API](https://api.slack.com/apps) and create a new app **From scratch**.\\n2. Go to *Basic Information*\\\\* > **App Credentials**",
"title": "Slack message agent | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-31",
"text": "creating conversations from any Slack channel:\\n\\n1. Link the DevRev Customer workspace to the channel by running /devrev link in the channel.\\n2. In the pop-up modal, search for the DevRev Customer workspace. \\n 2a. Select the preferred workspace and click **Link**. \\n 2b. If your channel is already linked to a workspace, the modal will show the details of the workspace and an option to unlink.\\n3. Once linked, new contacts identified via Slack are automatically added to the associated",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-32",
"text": "workspace. When creating work items, the linked customer workspace is pre-selected for quick access.\\n4. Invite the DevRev app to a channel by running /invite @DevRev in the channel.\\n\\nOnce the above steps are completed:\\n\\n* Messages sent by customers directly to the channel will create new conversations.\\n* Any messages in thread, or channel messages by members from your own team won\\xe2\\x80\\x99t create new conversations.\\n* Created conversations can be located in the **Inbox vista** in your",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-45",
"text": "Creating issues with sync enabled from external channels is not supported.\\n\\nDevRev Incidents and Slack\\n--------------------------\\n\\n![]()\\n\\nIncident Management is available as a **beta feature**. Contact the support team to enable it before configuring incident settings.\\n\\nThe Slack snap-in allows incident creation directly from Slack using the following methods:\\n\\n* Use the /devrev create-incident command.\\n* Select **Create a new incident** from the message actions.\\n* Enable",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-1300_KNOWLEDGE_NODE-85",
"text": "https:// api.devrev.ai / conversations.create\\nCreates a conversation.\\nRequest.\\n\\nThis endpoint expects an object.\\ntype \"support\" Required\\ndescription string Optional\\nDescription for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmembers list of strings Optional\\nThe users in the conversation.\\nmessages list of objects Optional\\nInitial messages on the conversation.\\nShow 2",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1506_KNOWLEDGE_NODE-4",
"text": "https://api.devrev.ai/conversations.create \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer <token>\" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"type\": \"support\" \\n >| }\\'\\n[/code] \\n \\nTry it\\n\\n201Created\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"conversation\": { \\n 3| \"id\": \"id\", \\n 4| \"members\": [ \\n 5| { \\n 6| \"type\": \"sys_user\", \\n 7| \"id\": \"members\" \\n 8| }",
"title": "Create Conversation (Beta) — DevRev | Docs"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-30",
"text": "organization.\\n\\nList of available commands\\n--------------------------\\n\\nAfter installation, visit your Slack workspace and enter the command /devrev help. A pop-up modal will display all the available commands.\\n\\nCreate DevRev conversations from Slack\\n--------------------------------------\\n\\nThe snap-in enables support teams to manage customer interactions directly from DevRev. You can enable this feature by toggling the **Sync conversations from Slack to DevRev** setting.\\n\\nTo start",
"title": "Slack | Integrate | Snap-ins | DevRev"
}
] |
56d425fe-d10a-4111-a000-2ad2045e4f37
|
DevRev voice support with Amazon
|
[
{
"id": "ART-15701_KNOWLEDGE_NODE-21",
"text": "an agent is added in amazon connect, click on sync support agents from amazon connect button in the snap-in page which can be found when you click on configure. This will sync the relevant permissions to that agent in DevRev.Improving audio quality and call stability\\n\\nFor better audio quality, follow the instruction guides here:1. Network setup:",
"title": "Amazon Connect Telephony Integration Guide"
},
{
"id": "ART-15701_KNOWLEDGE_NODE-2",
"text": "[https://docs.aws.amazon.com/connect/latest/adminguide/country-code-allow-list.html#country-allow-list-us-canada-govcloud](https://docs.aws.amazon.com/connect/latest/adminguide/country-code-allow-list.html#country-allow-list-us-canada-govcloud)\\n\\nAmazon Connect <> DevRev Integration\\n\\nThere are two parts to the setup of Amazon Connect telephony integration with DevRev.\\n\\nSetting up Amazon Connect Instance on AWS - Skip directly to the next step if amazon connect instance already",
"title": "Amazon Connect Telephony Integration Guide"
},
{
"id": "ART-15701_KNOWLEDGE_NODE-3",
"text": "exists.\\n\\nSetup on DevRev (Installing the snap-in)Setting up Amazon Connect Instance\\n\\nLog in to an existing AWS account or create one by following the AWS Guide: [https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-creating.html](https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-creating.html)PS: AWS supports Amazon Connect feature in few regions. Check the available regions here:",
"title": "Amazon Connect Telephony Integration Guide"
},
{
"id": "ART-15701_KNOWLEDGE_NODE-10",
"text": "to the User Management Tab on the left nav bar\\n\\nClick Add New Users. Add the user information. In the Security Profile, select Admin for admin and Agent for support agents who are supposed to pick up the call. Select the routing profile to be Basic Routing Profile for all the agents. Add the ACW timeout to be 10 seconds or any desired value.Setup DevRev Integration with Amazon Connect\\n\\nSelect the instance created in AWS.\\n\\nGo to Approved Origins from the left Navigation. Click on Add",
"title": "Amazon Connect Telephony Integration Guide"
},
{
"id": "ART-15701_KNOWLEDGE_NODE-16",
"text": "created\\n\\nEnter the SSO URL in case you have configured SAML login as identity management in amazon connect instance.\\n\\nEnter the complete S3 Bucket names and path for call recording and transcript. The complete bucket names and path can be found here. Copy the complete path directly.\\n\\nSelect Invite All checkbox if you would like to invite all the support agents to DevRev workspace if not present.\\n\\nClick on install snap-in.\\n\\nAfter the snap-in status shows Active, go to the configured",
"title": "Amazon Connect Telephony Integration Guide"
},
{
"id": "ART-15701_KNOWLEDGE_NODE-28",
"text": "Amazon Connect.\\n\\nQ: Agent status not changing after logging-in Amazon connect If this issue is happening after the snap-in installation is done recently, check if [https://app.devrev.ai](https://app.devrev.ai) is added in the Approved Origins in amazon connect instance setup.Q: Agents not able to see outbound call button or Place a call button on DevRev 1. Check if agent is logged in 2. Check if agent has outbound call permission\\n\\nQ: How to port existing number to amazon connect?",
"title": "Amazon Connect Telephony Integration Guide"
},
{
"id": "ART-15701_KNOWLEDGE_NODE-27",
"text": "point 17 in Setup DevRev Integration with Amazon Connect.\\n\\nQ: Why are the recording and transcript not available in the meeting object?\\n\\nCheck if set recording and analytics behavior block is configured in IVR. For more information, check the 2nd point in Recommended way to setup Amazon Connect IVR.\\n\\nCheck if the snap-in has the bucket name mentioned for both recording and transcript.\\n\\nCheck if EventBridge rule is setup for S3 Events. Check point 18 in Setup DevRev Integration with",
"title": "Amazon Connect Telephony Integration Guide"
},
{
"id": "ART-15701_KNOWLEDGE_NODE-4",
"text": "[https://docs.aws.amazon.com/connect/latest/adminguide/regions.html](https://docs.aws.amazon.com/connect/latest/adminguide/regions.html)\\n\\nSelect the region in which the Amazon Connect Instance should be created.\\n\\nClick on Add Instance\\n\\nSelect the desired Identity Management and enter desired connect instance url and go to Next.Recommended Option: If you are using an IdP to login to DevRev, it is better to connect the same IdP with the Amazon Connect Instance for a seamless login",
"title": "Amazon Connect Telephony Integration Guide"
},
{
"id": "ART-15701_KNOWLEDGE_NODE-11",
"text": "Domain and add [https://app.devrev.ai](https://app.devrev.ai) as the approved domain.\\n\\nUpdate IVR Flow: (Not needed if already done before) If you are taking inputs from user in the IVR and you want that information to be visible to the agent/ captured in the call, use set contact attributes block. Store the keys in the User Defined Namespace and add the key which needs to be displayed/ captured. For eg: previous_ticket_id is being captured by the user input.\\n\\nGo to DevRev marketplace and",
"title": "Amazon Connect Telephony Integration Guide"
},
{
"id": "ART-15701_KNOWLEDGE_NODE-24",
"text": "[https://docs.aws.amazon.com/connect/latest/adminguide/amazon-connect-service-limits.html](https://docs.aws.amazon.com/connect/latest/adminguide/amazon-connect-service-limits.html)\\n\\nQ: Unable to login into Amazon Connect CCP via DevRev\\n\\nThere can be multiple reasons for login failure:\\n\\nCheck with the administrator if you are are added as an agent in amazon connect instance.\\n\\nIf you are recently added as an agent, click on sync amazon connect agents in the snap-in.\\n\\nIf you are getting",
"title": "Amazon Connect Telephony Integration Guide"
},
{
"id": "ART-15701_KNOWLEDGE_NODE-1",
"text": "[https://docs.aws.amazon.com/connect/latest/adminguide/country-code-allow-list.html](https://docs.aws.amazon.com/connect/latest/adminguide/country-code-allow-list.html)To enable outbound calling for all the supported regions, raise a support ticket with AWS.Currently, Amazon Connect doesn\\'t support claiming of Indian numbers (+91) as support phone numbers. For all the supported countries, check:",
"title": "Amazon Connect Telephony Integration Guide"
},
{
"id": "ART-15701_KNOWLEDGE_NODE-23",
"text": "and FAQs\\n\\nQ: Why is Amazon Connect Instance creation failing? There can be multiple reasons due to which Amazon Connect Instance creation might be failing:\\n\\n1. Check if the region is supported to create Amazon Connect Instance: [https://docs.aws.amazon.com/connect/latest/adminguide/regions.html](https://docs.aws.amazon.com/connect/latest/adminguide/regions.html)\\n\\n2. There might be issue with the service quota limits.",
"title": "Amazon Connect Telephony Integration Guide"
},
{
"id": "ART-15701_KNOWLEDGE_NODE-5",
"text": "experience. Select SAML 2.0 based authentication in this case. If not, it is recommended to go ahead with Store users in Amazon Connect as identity management.Note: The identity management cannot be changed after amazon connect instance creation. Thus select carefully.\\n\\nOptional: Specify an administrator. This step can be skipped as we can specify the admin later. Recommended Option: Select No administrator and go to Next.\\n\\nSelect the option that you want to allow for telephony. Recommended",
"title": "Amazon Connect Telephony Integration Guide"
},
{
"id": "ART-15701_KNOWLEDGE_NODE-20",
"text": "AWS Service, Amazon S3 Event Notification as the Event type, Object Created event and specify the recording and transcript bucket name. Rest all steps will remain the same. The connection created in previous step can be used for this event bridge rule as well.\\n\\nGo to Amazon S3 > Buckets. Go to the bucket where recording and transcript is being stored. Go to Properties and switch on Send notifications to Amazon EventBridge for all events in this bucket under Event notifications.\\n\\nWhenever",
"title": "Amazon Connect Telephony Integration Guide"
},
{
"id": "ART-15701_KNOWLEDGE_NODE-22",
"text": "[https://docs.aws.amazon.com/connect/latest/adminguide/ccp-networking.html](https://docs.aws.amazon.com/connect/latest/adminguide/ccp-networking.html)2. Agent Workstation setup: [https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/improve-call-quality-on-agent-workstations-in-amazon-connect-contact-centers.html](https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/improve-call-quality-on-agent-workstations-in-amazon-connect-contact-centers.html)Troubleshooting Guide",
"title": "Amazon Connect Telephony Integration Guide"
},
{
"id": "ART-15701_KNOWLEDGE_NODE-26",
"text": "to use telephony, follow this guide: [https://docs.aws.amazon.com/connect/latest/adminguide/port-phone-number.html](https://docs.aws.amazon.com/connect/latest/adminguide/port-phone-number.html)\\n\\nQ: Why are the IVR inputs not showing up in the meeting side panel?1. Check if set contact attributes is set in the configured IVR flow. For more information, check the 2nd point in Recommended way to setup Amazon Connect IVR.2. Check if EventBridge rule is configured Amazon Connect events. Check",
"title": "Amazon Connect Telephony Integration Guide"
},
{
"id": "ART-15701_KNOWLEDGE_NODE-15",
"text": "\"kms:DescribeKey\"\\n ],\\n \"Resource\": \"arn:aws:kms:REGION:ACCOUNT_ID:key/KEY_ID\"\\n }\\n ]\\n}\\n\\nAfter the IAM role is created, copy the ARN and paste it in the connection page. Save the connection and click on connect on the snap-in page.\\n\\nEnter the access URL of the amazon connect instance here.The access URL can be copied from here\\n\\nEnter the Instance ID which is the last part of the instance ARN after /\\n\\nSelect the region in which amazon connect instance was",
"title": "Amazon Connect Telephony Integration Guide"
},
{
"id": "ART-15701_KNOWLEDGE_NODE-18",
"text": "}\\n ]\\n}\\n\\nCreate an event bridge rule in AWS to configure Amazon Connect events. a. Go to EventBridge > Rules > Create Rule. Enter rule name and click Next.b. Select AWS events as the event source. Select Use pattern form as the event pattern creation method. Select Amazon Connect from the AWS service dropdown and All events in the event type. Click on Next.c. Select EventBridge API destination as the target type and click on create a new API destination. Enter the API destination",
"title": "Amazon Connect Telephony Integration Guide"
},
{
"id": "ART-15701_KNOWLEDGE_NODE-12",
"text": "install Amazon Connect Telephony snap-in.\\n\\nTo create a new connection, select the New AWS Connection.\\n\\nCreate a new IAM role in AWS:a. Click on Create Role in IAM > Rolesb. Select Custom trust policy as the trusted entity type.Enter the following custom policy.{\\n\\t\"Version\": \"2012-10-17\",\\n\\t\"Statement\": [\\n\\t\\t{\\n\\t\\t\\t\"Effect\": \"Allow\",\\n\\t\\t\\t\"Principal\": {\\n\\t\\t\\t \"AWS\": \"arn:aws:iam::087878894592:user/devrev-telephony-prod-useast1\"\\n\\t\\t\\t},\\n\\t\\t\\t\"Action\":",
"title": "Amazon Connect Telephony Integration Guide"
},
{
"id": "ART-15701_KNOWLEDGE_NODE-7",
"text": "page or you can follow the recommended guide below from claiming the phone number to setting up a basic IVR.\\n\\nRecommended Guide to setup basic functionality for inbound and outbound calling:\\n\\nIf you already have a phone number and want to port it to Amazon Connect to use telephony, follow this guide: [https://docs.aws.amazon.com/connect/latest/adminguide/port-phone-number.html](https://docs.aws.amazon.com/connect/latest/adminguide/port-phone-number.html)Claim a phone number: a. Click on",
"title": "Amazon Connect Telephony Integration Guide"
},
{
"id": "ART-15701_KNOWLEDGE_NODE-8",
"text": "View Phone numbersb. Click on Claim a numberc. Choose the channel as Voice and select the desired country code for the phone number. AWS will provide the list of available phone numbers. Select the desired one. d. Choose the Sample Inbound Flow (Default flow created by AWS) e. Click on Save\\n\\nIVR Setup: Navigate to flows from the left nav\\n\\nFor Recordings and Transcripts: The set recording and analytics behavior block in the start of the IVR Flow is necessary to record all the call",
"title": "Amazon Connect Telephony Integration Guide"
},
{
"id": "ART-15701_KNOWLEDGE_NODE-19",
"text": "provided for the Amazon Connect Events in the snap-in configuration page. The HTTP method should be POST.d. Select create a new connectione. Select the Authorization type to be API key. Enter the key name as DEVREV_TOKEN and enter the value which is present in snap-in page.\\n\\nf. Click on Create a new role for this specific resource and click on Next and create the role.\\n\\nSimilarly for S3 events, create a new event bridge rule. In the event pattern, select Simple Storage Service (S3) as the",
"title": "Amazon Connect Telephony Integration Guide"
},
{
"id": "ART-15701_KNOWLEDGE_NODE-17",
"text": "IAM role and configure the external ID provided in the snap-in page in the IAM trust relationship policy. The IAM trust relationship policy should look like:{\\n \"Version\": \"2012-10-17\",\\n \"Statement\": [\\n {\\n \"Effect\": \"Allow\",\\n \"Principal\": {\\n \"AWS\": \"arn:aws:iam::087878894592:user/devrev-telephony-prod-useast1\"\\n },\\n \"Action\": \"sts:AssumeRole\",\\n \"Condition\": {\\n \"StringEquals\": {\\n \"sts:ExternalId\": \"<external id>\"\\n }\\n }\\n",
"title": "Amazon Connect Telephony Integration Guide"
},
{
"id": "ART-15701_KNOWLEDGE_NODE-6",
"text": "Option: Keep it as default i.e. allow both incoming and outgoing calls to truly experience the features provided by DevRev integration.\\n\\nYou can customise data storage options here.Recommended Option: Keep this as default and click on Next.\\n\\nReview the details and click on Create Instance.\\n\\nUse the Emergency Access to login the first time to setup the instance. If you are an administrator, you can directly use the access URL to login.\\n\\nYou can directly follow the guide available at home",
"title": "Amazon Connect Telephony Integration Guide"
}
] |
b5384b73-6875-4d27-b7e4-f33b2ef5b1c9
|
handle scenario when an agent is on holiday
|
[
{
"id": "ART-1976_KNOWLEDGE_NODE-28",
"text": "scenarios\\n----------------------------\\n\\n* Ticket routing based on customer inquiry keywords.\\n* Group-specific routing based on customer account assignments.\\n* Assignment routing based on severity and subtype.\\n* Custom field and tag-based routing.\\n* First responder ticket assignment.\\n\\nSystem requirements\\n-------------------\\n\\n* Administrator privileges are required for workflow deployment and execution.\\n* User status (active/away) is configurable through the profile",
"title": "Routing | Computer for Support Teams | DevRev"
},
{
"id": "ART-2024_KNOWLEDGE_NODE-27",
"text": "help now... ask again in 5d\\n\\nSample response:\\n\\n> I am unable to assist you at the moment, however please reach out to me again in five days and I will be happy to help you.\\n\\n### Summarize\\n\\nUsing the summarize command, you can sum up the entire conversation. It applies to the following:\\n\\n* Conversation\\n* Tickets\\n* Issues\\n* Part\\n* Workspace\\n* Customer\\n* Account\\n\\nSample response:\\n\\n> **Summary:**\\n>\\n> * Rahul from DummyOrg is having difficulty installing the Plug Widget.\\n> *",
"title": "Slash commands | Automate | Snap-ins | DevRev"
},
{
"id": "ART-3205_KNOWLEDGE_NODE-26",
"text": "and click **Deploy snap-in**.\\n3. Open the Workflow Builder and locate the **Set User Preference For Group** action node.\\n4. Select the users you want to set as online in the **Users** input field, along with the group they belong to in the **Group**. Remaining group members are automatically set as offline.\\n\\n[PreviousSmart issue creator](/docs/automations/smart-issue-creator)[NextSLA status change Slack notifier](/docs/automations/sla-change-notifier)\\n\\n#### On this page\\n\\n* [Installing",
"title": "Set user preference for group | Automate | Snap-ins | DevRev"
},
{
"id": "ART-1981_KNOWLEDGE_NODE-26",
"text": "a small number of tags to help categorize tickets. For example, at DevRev we have the following: bug, feature-request, other-request, question, and incident.\\n* Designate one or more customer experience engineers to be on call. Add them to the **Support** group inside **Settings > Groups** and as default owner in the **Support Routing** snap-in. Default owners are notified through email and the DevRev app as soon as a new conversation is started.\\n\\nMonitor the inbox\\n-----------------\\n\\n*",
"title": "Support best practices | Computer for Support Teams | DevRev"
},
{
"id": "ART-1976_KNOWLEDGE_NODE-27",
"text": "created > Output > ID Owned by > Set: Pick user > Output > User |\\n\\nPick user node capabilities\\n---------------------------\\n\\n* Object: Selection of ticket or conversation routing type.\\n* Group: Selection of routing destination group.\\n* Users: Selection of specific ticket assignment users.\\n* Strategy: Selection of assignment methodology (round-robin, load balancing, random).\\n* Agent availability: Assignment filters based on agent status (away or active).\\n\\nAdditional routing",
"title": "Routing | Computer for Support Teams | DevRev"
}
] |
c24840e2-3831-494a-96c7-c83674761d8e
|
check onboarding modules completion status
|
[
{
"id": "ART-16805_KNOWLEDGE_NODE-26",
"text": "types.\\n* Detailed learner progress tracking with enrollment status, completion percentages, quiz scores, and learning duration metrics.\\n* Group import and organizational hierarchy management.\\n* Learning analytics with cross-referential data for course-learner-user relationships and progress reporting.\\n\\nSupported objects\\n-----------------\\n\\nThe following is a list of Articulate Reach 360 objects and their corresponding DevRev equivalents. Those marked as Sync to DevRev are eligible for",
"title": "Articulate Reach 360 AirSync | AirSync | Snap-ins | DevRev"
},
{
"id": "ART-16805_KNOWLEDGE_NODE-31",
"text": "DevRev for any learning content, users, or progress data added to Articulate Reach 360 after the last sync or import.\\n* **View Report**\\n\\n This option allows you to access detailed information about the initial import and any subsequent syncs performed, including learning analytics and data extraction reports.\\n* **Delete Import**\\n\\n If you want to remove the import and all learning data that were imported from Articulate Reach 360 into DevRev, you can use this option.\\n* **Edit",
"title": "Articulate Reach 360 AirSync | AirSync | Snap-ins | DevRev"
}
] |
95da762a-e14a-464f-affd-7f28c0b50941
|
privilege title that controls article access
|
[
{
"id": "ART-1955_KNOWLEDGE_NODE-52",
"text": "Members Reader:* Contains privileges for read operations on Group Members.\\n\\n Privileges: object\\\\_member object ['READ']\\n* *Article Admin:* Contains admin privileges for operations on articles.\\n\\n Privileges: article object ['CREATE', 'READ', 'UPDATE', 'DELETE']\\n* *DevOrg Commerce Admin AccountCommerceDetails Creator:* Contains workspace commerce admin privileges for accountCommerceDetails objects.\\n\\n Privileges: account\\\\_commerce\\\\_details object ['READ', 'UPDATE']\\n* *Account",
"title": "Default privileges by group | Roles | Computer by DevRev | DevRev"
},
{
"id": "ART-1955_KNOWLEDGE_NODE-72",
"text": "for operations on Group Members.\\n\\n Privileges: object\\\\_member object ['CREATE', 'DELETE']\\n* *Group Members Reader:* Contains privileges for read operations on Group Members.\\n\\n Privileges: object\\\\_member object ['READ']\\n* *Article Admin:* Contains admin privileges for operations on articles.\\n\\n Privileges: article object ['CREATE', 'READ', 'UPDATE', 'DELETE']\\n* *DevOrg Commerce Admin AccountCommerceDetails Creator:* Contains workspace commerce admin privileges for",
"title": "Default privileges by group | Roles | Computer by DevRev | DevRev"
},
{
"id": "ART-1955_KNOWLEDGE_NODE-36",
"text": "linkable object ['CREATE', 'UPDATE', 'DELETE']\\n* *enhancement Editor:* Contains privileges for modifying (create, update, delete) enhancement.\\n\\n Privileges: enhancement object ['CREATE', 'UPDATE', 'DELETE']\\n* *Article Interactor:* Contains privileges for operations on articles.\\n\\n Privileges: article object ['CREATE', 'READ', 'UPDATE']\\n* *Member Ticket Field Access:* Contains the field access on tickets\\n\\n Privileges: ticket object None\\n* *Account Interactor:* Contains privileges on",
"title": "Default privileges by group | Roles | Computer by DevRev | DevRev"
},
{
"id": "ART-1955_KNOWLEDGE_NODE-78",
"text": "object ['CREATE']\\n* *App Fragment Creator:* Contains privileges for creating app fragments\\n\\n Privileges: app\\\\_fragment object ['CREATE']\\n* *Command Interactor:* Contains CRUD privileges on commands\\n\\n Privileges: command object ['READ', 'CREATE', 'UPDATE', 'DELETE']\\n* *Article Admin Field Access:* Article field access role for admin users\\n\\n Privileges: article object None\\n* *Devu Admin Field Access:* Devu Admin field access role\\n\\n Privileges: devu object None\\n* *Vista Viewer &",
"title": "Default privileges by group | Roles | Computer by DevRev | DevRev"
},
{
"id": "ART-1955_KNOWLEDGE_NODE-58",
"text": "app\\\\_fragment object ['CREATE']\\n* *Command Interactor:* Contains CRUD privileges on commands\\n\\n Privileges: command object ['READ', 'CREATE', 'UPDATE', 'DELETE']\\n* *Article Admin Field Access:* Article field access role for admin users\\n\\n Privileges: article object None\\n* *Devu Admin Field Access:* Devu Admin field access role\\n\\n Privileges: devu object None\\n* *Org Preferences Update:* A role that allows a user to update org preferences.\\n\\n Privileges: org\\\\_preferences object",
"title": "Default privileges by group | Roles | Computer by DevRev | DevRev"
},
{
"id": "ART-1985_KNOWLEDGE_NODE-48",
"text": "approval) and has all drafter & approver rights.\\n\\nBy default, all users have drafter and approver rights but not publisher rights. To assign publisher rights, go to **Settings > User Management > Internal Groups > Publisher Group > + User**.\\n\\n![]()\\n\\nContact your DevRev representative to enable the article publisher group.\\n\\nAdmin users can perform all drafter, approver, and publisher functions, including article deletion.\\n\\n### Submit an article for review\\n\\n1. Create an article and",
"title": "Articles | Knowledge Base | Computer for Support Teams | DevRev"
},
{
"id": "ART-1828_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-17233_KNOWLEDGE_NODE-11",
"text": "specifies the permission level for each user or group using the `permission` type.\\nThis type is a structure that connects a reference to a user-like record type (the `member_id` field)\\nwith an `enum` value that defines the user\\xe2\\x80\\x99s role or permission level.\\n\\n### Scope interaction\\n\\n###### Internal scope\\n\\n###### External scope\\n\\nFor `scope=internal` articles:\\n\\n* By default, only the owner has access.\\n* Additional access is granted exclusively through the `shared_with`",
"title": "Permissions | DevRev | Docs"
},
{
"id": "ART-1302_KNOWLEDGE_NODE-34",
"text": "properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe authors of the article.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ncustom_schema_spec object Optional\\nRequested custom schemas described abstractly. Every",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1301_KNOWLEDGE_NODE-34",
"text": "properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe authors of the article.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ncustom_schema_spec object Optional\\nRequested custom schemas described abstractly. Every",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1780_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1566_KNOWLEDGE_NODE-28",
"text": "object Required\\nShow 3 properties\\ntitle string Required\\n\\nName of the article.\\n\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\n\\nType of the article.\\n\\nauthored_by list of strings Optional\\n\\nThe authors of the article.\\n\\ncustom_fields map from strings to any Optional\\n\\nApplication-defined custom fields.\\n\\ncustom_schema_spec object Optional\\n\\nRequested",
"title": "Transition (Beta) — DevRev | Docs"
},
{
"id": "ART-1836_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1822_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1549_KNOWLEDGE_NODE-28",
"text": "object Required\\nShow 3 properties\\ntitle string Required\\n\\nName of the article.\\n\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\n\\nType of the article.\\n\\nauthored_by list of strings Optional\\n\\nThe authors of the article.\\n\\ncustom_fields map from strings to any Optional\\n\\nApplication-defined custom fields.\\n\\ncustom_schema_spec object Optional\\n\\nRequested",
"title": "List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1545_KNOWLEDGE_NODE-28",
"text": "object Required\\nShow 3 properties\\ntitle string Required\\n\\nName of the article.\\n\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\n\\nType of the article.\\n\\nauthored_by list of strings Optional\\n\\nThe authors of the article.\\n\\ncustom_fields map from strings to any Optional\\n\\nApplication-defined custom fields.\\n\\ncustom_schema_spec object Optional\\n\\nRequested",
"title": "Create (Beta) — DevRev | Docs"
},
{
"id": "ART-1593_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1547_KNOWLEDGE_NODE-28",
"text": "object Required\\nShow 3 properties\\ntitle string Required\\n\\nName of the article.\\n\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\n\\nType of the article.\\n\\nauthored_by list of strings Optional\\n\\nThe authors of the article.\\n\\ncustom_fields map from strings to any Optional\\n\\nApplication-defined custom fields.\\n\\ncustom_schema_spec object Optional\\n\\nRequested",
"title": "Get Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1562_KNOWLEDGE_NODE-28",
"text": "object Required\\nShow 3 properties\\ntitle string Required\\n\\nName of the article.\\n\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\n\\nType of the article.\\n\\nauthored_by list of strings Optional\\n\\nThe authors of the article.\\n\\ncustom_fields map from strings to any Optional\\n\\nApplication-defined custom fields.\\n\\ncustom_schema_spec object Optional\\n\\nRequested",
"title": "Get (Beta) — DevRev | Docs"
},
{
"id": "ART-1551_KNOWLEDGE_NODE-28",
"text": "object Required\\nShow 3 properties\\ntitle string Required\\n\\nName of the article.\\n\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\n\\nType of the article.\\n\\nauthored_by list of strings Optional\\n\\nThe authors of the article.\\n\\ncustom_fields map from strings to any Optional\\n\\nApplication-defined custom fields.\\n\\ncustom_schema_spec object Optional\\n\\nRequested",
"title": "Update (Beta) — DevRev | Docs"
},
{
"id": "ART-1543_KNOWLEDGE_NODE-28",
"text": "object Required\\nShow 3 properties\\ntitle string Required\\n\\nName of the article.\\n\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\n\\nType of the article.\\n\\nauthored_by list of strings Optional\\n\\nThe authors of the article.\\n\\ncustom_fields map from strings to any Optional\\n\\nApplication-defined custom fields.\\n\\ncustom_schema_spec object Optional\\n\\nRequested",
"title": "Metric Definitions List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1827_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1785_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1595_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1605_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-17233_KNOWLEDGE_NODE-7",
"text": "object to the *platform groups* object in DevRev.\\n3. Reference your object in other fields, such as in the `shared_with` field of articles.\\n\\nShared with field\\n-----------------\\n\\nThe `shared_with` field enables you to define permissions for articles (and other objects in the future).\\nIt specifies both who can access the content and what permission level they have.\\nThis field utilizes the `permission` type to associate users or groups with their designated roles.\\n\\n### Structure\\n\\nEach",
"title": "Permissions | DevRev | Docs"
},
{
"id": "ART-1592_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1838_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1789_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1792_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1654_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1783_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Locate — DevRev | Docs"
},
{
"id": "ART-1829_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1784_KNOWLEDGE_NODE-26",
"text": "object.\\napplies_to_parts list of strings Required\\nThe parts that the article applies to.\\nowned_by list of strings Required\\nThe users that own the article.\\nresource object Required\\nShow 3 properties\\ntitle string Required\\nName of the article.\\naccess_level enum Optional\\nAllowed values: external internal private public restricted\\narticle_type \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nType of the article.\\nauthored_by list of strings Optional\\nThe",
"title": "Locate Post — DevRev | Docs"
}
] |
b91b3d58-d9ff-44ef-b3f0-5f3896622fdd
|
plug widget not appearing on website after code installation
|
[
{
"id": "ART-2894_KNOWLEDGE_NODE-2",
"text": "insert the code snippet provided below on every page where you want the widget to appear for website visitors.\\n\\n## Unique app ID\\n\\nEnsure to replace the app ID with your app ID which identifies your PLuG search widget. You can access your app ID from your DevRev account by following these steps.\\n\\n 1. In DevRev, go to **Settings** > **Support** > **PLuG Settings** through the settings icon in the top-left corner.\\n 2. Click **Enable PLuG Widget** if it isn\\xe2\\x80\\x99t already enabled.\\n",
"title": "Install PLuG search — DevRev | Docs"
},
{
"id": "ART-15490_KNOWLEDGE_NODE-1",
"text": "code snippet provided below on every page where you want the widget to appear for website visitors.\\n\\nUnique app ID\\n-------------\\n\\nEnsure to replace the app ID with your app ID which identifies your Plug search widget. You can access your app ID from your DevRev account by following these steps.\\n\\n1. In DevRev, go to **Settings** > **Support** > **Plug Settings** through the settings icon in the top-left corner.\\n2. Click **Enable Plug Widget** if it isn\\xe2\\x80\\x99t already enabled.\\n3.",
"title": "Install Plug search | DevRev | Docs"
},
{
"id": "ART-2059_KNOWLEDGE_NODE-6",
"text": "to the Customize documentation.\\n\\nAlternatively, for the most comprehensive customizations, refer to our SDK functions here.\\n\\nIntegration code.\\n\\nTo get the PLuG chat widget to appear on your website and web app, copy and paste the snippet below on every page where you want the widget to appear for website visitors.\\n\\nUnique app ID.\\n\\nMake sure to replace the app ID with your app ID which identifies your PLuG chat widget. You can access your app ID from your DevRev account by following",
"title": "Install PLuG chat on your website"
},
{
"id": "ART-2059_KNOWLEDGE_NODE-9",
"text": "App.js.\\n\\n1 useEffect ( () => {\\n2 window. plugSDK. init ({\\n3 // Please ensure you replace the app_id with your unique app id\\n4 app_id : \"<your_unique_app_id>\" ,\\n5 });\\n6 }, []);\\n\\nYou should now have PLuG chat widget installed on your website. Facing some issues? Reach out to us through our own PLuG chat widget from the bottom right of your screen.\\n\\nOnce the widget is installed on your website, every user who visits your website is considered an anonymous user. Anonymous users are the",
"title": "Install PLuG chat on your website"
},
{
"id": "ART-2059_KNOWLEDGE_NODE-7",
"text": "these steps.\\n\\nIn DevRev, go to Settings. > Support. > PLuG Settings. through the settings icon in the top-left corner.\\nClick Enable PLuG Widget. if it isn\\'t already enabled.\\nCopy your Unique App ID. from the Configuration tab..\\nSetup for HTML.\\n\\nPlace this code in the head of your HTML page.\\n\\n1 //\\n2 < script\\n3 type = \"text/javascript\"\\n4 src = \"https://plug-platform.devrev.ai/static/plug.js\"\\n5 > </ script >\\n\\nPlace this code in the body of your HTML page.\\n\\n1 < script >\\n2",
"title": "Install PLuG chat on your website"
},
{
"id": "ART-2893_KNOWLEDGE_NODE-2",
"text": "2| type=\"text/javascript\" \\n 3| src=\"https://plug-platform.devrev.ai/static/plug.js\" \\n 4| ></script>\\n[/code] \\n \\nPlace the following code in the `<body>` section of your HTML page:\\n\\n[code]\\n\\n 1| <script> \\n ---|--- \\n 2| window.plugSDK.init({ \\n 3| // Please ensure you replace the app_id with your unique app id \\n 4| app_id: \"<your_unique_app_id>\", \\n 5| }); \\n 6| </script>\\n[/code] \\n \\nThe PLuG widget should now be installed on",
"title": "Install the Web SDK — DevRev | Docs"
},
{
"id": "ART-15716_KNOWLEDGE_NODE-10",
"text": "work perfectly in a mobile WebView\\n\\nSetting Up the PluG Widget on a Website\\n\\nGo to your DevRev workspace, open PluG settings, configure the widget, and copy the provided JavaScript snippet. Paste it before the closing tag in your website\\xe2\\x80\\x99s HTML. Deploy your site and the widget should appear.\\n\\n[PLuG installation steps](https://developer.devrev.ai/public/sdks/web/installation)\\n\\nRenaming the \\'DevRev Turing\\' Chatbot - asked in slack channel\\n\\nTroubleshooting PluG AI",
"title": "Support queries related playbook"
},
{
"id": "ART-3109_KNOWLEDGE_NODE-25",
"text": "Plug widget to reflect your unique identity truly.\\n\\nTo configure the appearance of your Plug widget, open your DevRev app and navigate to **Settings > Support > Plug Chat > Configuration, Styling, and Layout**.\\n\\n### Configuration\\n\\n* Hide Plug widget: Hide the Plug Widget on specific URLs by clicking **+ Rule** and adding the URLs you want to configure.\\n\\n### Styling\\n\\n* Launcher logo: The image that's visible as your widget icon. A 20-pixel square image is recommended.\\n* Alignment: The",
"title": "Plug widget customization | Computer for Your Customers | DevRev"
},
{
"id": "ART-2893_KNOWLEDGE_NODE-4",
"text": "update their information.\\n\\n#####\\n\\nOnce the SDK is installed, the chat widget appears by default. If you are not using the PLuG SDK for support or chat-related flows, you can disable the chat widget by setting the `disable_plug_chat_window` input to `true`.\\n\\n[code]\\n\\n <script> \\n --- \\n window.plugSDK.init({ \\n app_id: \\'<your_unique_app_id>\\', \\n disable_plug_chat_window: true, \\n }); \\n </script>\\n[/code] \\n \\nTo ensure seamless",
"title": "Install the Web SDK — DevRev | Docs"
},
{
"id": "ART-2897_KNOWLEDGE_NODE-18",
"text": "search agent on your website. This initialization is required before performing any other actions with the PLuG widget SDK.\\n\\n[code]\\n\\n 1| useEffect(() => { \\n ---|--- \\n 2| window.plugSDK.init({ \\n 3| app_id: \\'<your_unique_app_id>\\', \\n 4| disable_plug_chat_window: true, \\n 5| }); \\n 6| \\n 7| window.plugSDK.onEvent((payload) => { \\n 8| if (payload.type === \\'ON_PLUG_WIDGET_READY\\') { \\n 9| window.plugSDK.initSearchAgent(); \\n",
"title": "Methods — DevRev | Docs"
},
{
"id": "ART-15504_KNOWLEDGE_NODE-2",
"text": "code in the `<head>` section of your HTML page:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | <script |\\n| 2 | type=\"text/javascript\" |\\n| 3 | src=\"https://plug-platform.devrev.ai/static/plug.js\" |\\n| 4 | ></script> |\\n```\\n\\nPlace the following code in the `<body>` section of your HTML page:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | <script> |\\n| 2 | window.plugSDK.init({ |\\n| 3 | // Please ensure you replace the app_id with your unique app id |\\n| 4 | app_id: \"<your_unique_app_id>\", |\\n| 5 | }); |\\n| 6 |",
"title": "Install the Web SDK | DevRev | Docs"
},
{
"id": "ART-1466_KNOWLEDGE_NODE-25",
"text": "application.\\n\\n1 await window. plugSDK. shutdown () ;\\n\\nAfter calling the shutdown() method, you can use the init() method to reinitialize the PLuG widget on your website if you want to display it again in the logged-out version of your application.\\n\\nOnce the shutdown() method is called, all other widget functionalities, such as session recording and Nudges, will also be stopped. You will need to reinitialize the widget to reactivate these features.\\n\\nInitialize the search",
"title": "Methods — DevRev | Docs"
},
{
"id": "ART-2900_KNOWLEDGE_NODE-4",
"text": "widget launcher to best fit your website or app. \\n`widget_alignment`| Align the widget to be placed either on the left or right side, relative to the launcher. \\n`enable_default_launcher`| Show/hide the default PLuG Widget launcher. \\n`theme`| Set the theme of the PLuG Widget. \\n \\n## Code sandbox\\n\\n## Properties\\n\\n### PLuG launcher\\n\\nCustomize the widget launcher to best fit your website or app; or show or hide the default PLuG widget launcher.\\n\\nTo customize your PLuG launcher",
"title": "Custom implementation — DevRev | Docs"
},
{
"id": "ART-2059_KNOWLEDGE_NODE-8",
"text": "window.plugSDK.init({\\n3 // Please ensure you replace the app_id with your unique app id\\n4 app_id: \"<your_unique_app_id>\",\\n5 });\\n6 </ script >\\nSetup for React.\\n\\nPlace this in public/index.html file, inside the body tag of your HTML page.\\n\\n1 <script\\n2 type= \"text/javascript\"\\n3 src= \"https://plug-platform.devrev.ai/static/plug.js\"\\n4 ></script>;\\n\\nPlace this code inside the react component where you want to render the chat widget. Typically you should do it as top level component like",
"title": "Install PLuG chat on your website"
},
{
"id": "ART-15509_KNOWLEDGE_NODE-17",
"text": "the `initSearchAgent()` method sets up the Plug search agent on your website. This initialization is required before performing any other actions with the Plug widget SDK.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | useEffect(() => { |\\n| 2 | window.plugSDK.init({ |\\n| 3 | app_id: \\'<your_unique_app_id>\\', |\\n| 4 | disable_plug_chat_window: true, |\\n| 5 | }); |\\n| 6 | |\\n| 7 | window.plugSDK.onEvent((payload) => { |\\n| 8 | if (payload.type === \\'ON_PLUG_WIDGET_READY\\') { |\\n| 9 |",
"title": "Methods | DevRev | Docs"
},
{
"id": "ART-2897_KNOWLEDGE_NODE-4",
"text": "our SDK, you can integrate our feature-rich widget, creating a dynamic and personalized user experience.\\n\\n## Initialize SDK\\n\\nTo get started with the PLuG SDK on your website, call the `init()` method. This method is essential for enabling the SDK\\xe2\\x80\\x99s functionality, including session recording, the chat widget, and the search agent. Initialization is required before you can perform any other actions using the PLuG SDK.\\n\\n[code]\\n\\n 1| useEffect(() => { \\n ---|--- \\n 2|",
"title": "Methods — DevRev | Docs"
},
{
"id": "ART-1466_KNOWLEDGE_NODE-1",
"text": "feature-rich widget, creating a dynamic and personalized user experience.\\n\\nInitialize SDK.\\n\\nTo get started with the PLuG SDK on your website, call the init() method. This method is essential for enabling the SDK\\xe2\\x80\\x99s functionality, including session recording, the chat widget, and the search agent. Initialization is required before you can perform any other actions using the PLuG SDK.\\n\\n1 useEffect ( () => { 2 window. plugSDK. init ( { 3 app_id : < your_unique_app_id > , 4 }); 5 },",
"title": "Methods — DevRev | Docs"
},
{
"id": "ART-15504_KNOWLEDGE_NODE-1",
"text": "is installed, the chat widget appears by default.\\n\\nGetting your unique app ID\\n--------------------------\\n\\nYou can access your app ID from your DevRev account by following these steps:\\n\\n1. In DevRev, go to **Settings > Support > Plug Settings** via the settings icon in the top-left corner.\\n2. If the Plug feature is not already enabled, click **Enable Plug**.\\n3. Under the **Configuration** tab, copy the **Unique App ID**.\\n\\n###### Setup\\n\\n###### Setup for React\\n\\nPlace the following",
"title": "Install the Web SDK | DevRev | Docs"
},
{
"id": "ART-1466_KNOWLEDGE_NODE-26",
"text": "agent.\\n\\nCalling the initSearchAgent() method sets up the PLuG search agent on your website. This initialization is required before performing any other actions with the PLuG widget SDK.\\n\\n1 useEffect ( () => { 2 window. plugSDK. init ( { 3 app_id : \\' <your_unique_app_id> \\' , 4 disable_plug_chat_window : true , 5 } ) ; 6 7 window. plugSDK. onEvent ( ( payload ) => { 8 if ( payload. type === \\' ON_PLUG_WIDGET_READY \\' ) { 9 window. plugSDK. initSearchAgent () ; 10 } 11 } ) ; 12 } , []) ;",
"title": "Methods — DevRev | Docs"
},
{
"id": "ART-2894_KNOWLEDGE_NODE-4",
"text": "2| window.plugSDK.init({ \\n 3| app_id: \\'<your_unique_app_id>\\', \\n 4| disable_plug_chat_window: true, \\n 5| }); \\n 6| \\n 7| window.plugSDK.onEvent((payload) => { \\n 8| if (payload.type === \\'ON_PLUG_WIDGET_READY\\') { \\n 9| window.plugSDK.initSearchAgent(); \\n 10| } \\n 11| }); \\n 12| </script>\\n[/code] \\n \\nTo toggle `searchAgent`, call the following method on any event required:\\n\\n[code]\\n\\n",
"title": "Install PLuG search — DevRev | Docs"
},
{
"id": "ART-15504_KNOWLEDGE_NODE-4",
"text": "[identify your customers](/sdks/web/user-identity) and update their information.\\n\\n##### \\n\\nOnce the SDK is installed, the chat widget appears by default. If you are not using the Plug SDK for support or chat-related flows, you can disable the chat widget by setting the `disable_plug_chat_window` input to `true`.\\n\\n```\\n| |\\n| --- |\\n| <script> |\\n| window.plugSDK.init({ |\\n| app_id: \\'<your_unique_app_id>\\', |\\n| disable_plug_chat_window: true, |\\n| }); |\\n| </script> |\\n```\\n\\nTo ensure",
"title": "Install the Web SDK | DevRev | Docs"
},
{
"id": "ART-15509_KNOWLEDGE_NODE-3",
"text": "experience.\\n\\nInitialize SDK\\n--------------\\n\\nTo get started with the Plug SDK on your website, call the `init()` method. This method is essential for enabling the SDK\\xe2\\x80\\x99s functionality, including session recording, the chat widget, and the search agent. Initialization is required before you can perform any other actions using the Plug SDK.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | useEffect(() => { |\\n| 2 | window.plugSDK.init({ |\\n| 3 | app_id: <your_unique_app_id>, |\\n| 4 | }); |\\n|",
"title": "Methods | DevRev | Docs"
},
{
"id": "ART-10697_KNOWLEDGE_NODE-31",
"text": "boosting engagement and reducing repetitive inquiries. To enable Plug, go to **Settings > Portal Settings**, activate Plug widget, and **Save** and **Publish**.\\n\\n![]()\\xc2\\xa0For more information about *Support App*, refer to the following articles: \\xe2\\x80\\xa3 [Support snap-ins | Support](/docs/product/snapins-support) \\xe2\\x80\\xa3 [Support best practices | Support](/docs/product/support-bp) \\xe2\\x80\\xa3 [Support](/docs/product/support) \\xe2\\x80\\xa3",
"title": "February 2025 | Changelog | DevRev"
},
{
"id": "ART-15496_KNOWLEDGE_NODE-4",
"text": "in the `custom_launcher_selector` property. This CSS selector is the reference based on which your Plug widget opens. This property accepts a string value. The selector can also be configured through the plug settings on app.devrev.ai.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | custom_launcher_selector?: '#my-plug-widget' |\\n```\\n\\nUse the `enable_default_launcher` property only if you are not using the custom launcher selector.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | enable_default_launcher?:",
"title": "Custom implementation | DevRev | Docs"
},
{
"id": "ART-2900_KNOWLEDGE_NODE-5",
"text": "styles, specify the CSS selector in the `custom_launcher_selector` property. This CSS selector is the reference based on which your PLuG widget opens. This property accepts a string value. The selector can also be configured through the plug settings on app.devrev.ai.\\n\\n[code]\\n\\n 1| custom_launcher_selector?: '#my-plug-widget' \\n ---|---\\n[/code] \\n \\nUse the `enable_default_launcher` property only if you are not using the custom launcher selector.\\n\\n[code]\\n\\n 1|",
"title": "Custom implementation — DevRev | Docs"
},
{
"id": "ART-2897_KNOWLEDGE_NODE-5",
"text": "window.plugSDK.init({ \\n 3| app_id: <your_unique_app_id>, \\n 4| }); \\n 5| }, []);\\n[/code] \\n \\nThe `init()` method can accept multiple inputs, which are explained below:\\n\\nInput parameter| Description| Values \\n---|---|--- \\n`app_id`| The unique identifier for your PLuG SDK. This parameter is required.| String \\n`disable_plug_chat_window`| The chat widget is enabled by default. Use this option if you want to disable the chat widget.| Boolean (True or False)",
"title": "Methods — DevRev | Docs"
},
{
"id": "ART-1270_KNOWLEDGE_NODE-2",
"text": "{startConversationContent: \\'Hi\\',}); Start a conversation.\\n\\nplugSDK.prefillSearchQuery(query:\"string\") Prefill the search input of the search agent.\\n\\nInitialize chat.\\n\\nCalling the init() method initializes the PLuG chat widget on your website. Initializing the PLuG widget is necessary for you to perform any other actions on the PLuG widget SDK.\\n\\n1 useEffect ( () => { 2 window. plugSDK. init ( { 3 app_id : < your_unique_app_id > , 4 }); 5 }, []);\\n\\nWhen React is using Strict mode, you",
"title": "Methods — DevRev | Docs"
},
{
"id": "ART-15509_KNOWLEDGE_NODE-4",
"text": "5 | }, []); |\\n```\\n\\nThe `init()` method can accept multiple inputs, which are explained below:\\n\\n| Input parameter | Description | Values |\\n| --- | --- | --- |\\n| `app_id` | The unique identifier for your Plug SDK. This parameter is required. | String |\\n| `disable_plug_chat_window` | The chat widget is enabled by default. Use this option if you want to disable the chat widget. | Boolean (True or False) |\\n| `enable_default_launcher` | Show/hide the default Plug widget launcher. | Boolean",
"title": "Methods | DevRev | Docs"
},
{
"id": "ART-15490_KNOWLEDGE_NODE-2",
"text": "Copy your **Unique App ID** from the **Configuration tab**.\\n\\n###### Setup\\n\\n###### Setup for React\\n\\nPlace the following code in the `<head>` section of your HTML page:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | <script |\\n| 2 | src=\"https://plug-platform.devrev.ai/static/plug.js\" |\\n| 3 | type=\"text/javascript\"> |\\n| 4 | </script> |\\n```\\n\\nPlace the following code in the `<body>` section of your HTML page:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | <script> |\\n| 2 | window.plugSDK.init({ |\\n| 3 |",
"title": "Install Plug search | DevRev | Docs"
}
] |
80b67b4b-b879-40df-a547-0e01355494f1
|
how to park ticket to another department
|
[
{
"id": "ART-15989_KNOWLEDGE_NODE-25",
"text": "successful validation, the snap-in relocates the issue or ticket to the part specified in the **Issue/Ticket - Target Part Field**.\\n\\nInstallation\\n------------\\n\\n1. Open the DevRev marketplace and install the **Automated Part Update** snap-in.\\n2. Select the workspace where you want to install the snap-in, confirm your\\n selection, and click **Deploy snap-in**.\\n3. Set the following operating parameters.\\n\\n* **For Initial Part of Issue**: Enter the part to be used as a condition for the",
"title": "Automated part update | Automate | Snap-ins | DevRev"
},
{
"id": "ART-1976_KNOWLEDGE_NODE-25",
"text": "and effective resolution. Users can design workflows tailored to various scenarios; the example below illustrates a basic routing use case.\\n\\n| NODE | ACTIVITY |\\n| --- | --- |\\n| Trigger | Ticket created |\\n| Action | Pick user by group |\\n| Action | Update ticket |\\n| | ID: Ticket created > Output > ID |\\n| | Group > Output > ID |\\n| | Owned by > Set: Pick user > Output > User |\\n\\nOrgs can set up pull-based routing by updating the group instead of the user ID in the workflow illustrated",
"title": "Routing | Computer for Support Teams | DevRev"
}
] |
58be3ae0-a271-4f80-9371-ec9ed5155f38
|
setup auto email for customer when they mail
|
[
{
"id": "ART-1953_KNOWLEDGE_NODE-34",
"text": "subject>\"\\n\\n![]()\\n\\nThis email is only sent to organizations that have installed [Auto-reply snap-in](https://docs.devrev.ai/automations/auto-reply).\\n\\nAuto reply on email\\n-------------------\\n\\n* **Trigger**: A new email is received from a customer.\\n* **Action**: An automated reply is sent.\\n* **Sender**: {Company\\\\_Name} [[email protected]](mailto:[email protected])\\n* **Subject**: \"<customer email subject>\"\\n\\n![]()\\n\\nThis email is only sent to organizations that have",
"title": "Customer email notifications | Computer by DevRev | DevRev"
},
{
"id": "ART-2006_KNOWLEDGE_NODE-28",
"text": "on the submit button.\\n7. Click **Save**.\\n\\n![]()\\n\\nIf Turing in your workspace is in Auto-response mode, don't enable auto-customer reply or you'll send two messages to your customer. By using this snap-in, you can still request email addresses for enriching customer data, as well as contacting customers through the right channel if they drift off your website.\\n\\n[PreviousAuto-link DevRev GitHub accounts](/docs/automations/auto-link-github-devrev)[NextAuto parts to",
"title": "Automatic customer reply | Automate | Snap-ins | DevRev"
},
{
"id": "ART-3207_KNOWLEDGE_NODE-41",
"text": "to send emails | This is required if workflows or bots are configured to send emails. Keep it enabled unless you intend to turn it off. |\\n\\n### Step 6: Auto-Reply & Threading Features\\n\\nYou can configure DevRev to send automatic responses when new emails are received:\\n\\n* **Auto-reply message**: Acknowledge new requests and provide links or resources.\\n* **Send auto-reply message to**: Choose recipients such as, only customers.\\n\\n> You can include links to help docs, response times, or",
"title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-1953_KNOWLEDGE_NODE-35",
"text": "installed [Auto-reply snap-in](https://docs.devrev.ai/automations/auto-reply).\\n\\n[PreviousUpdates](/docs/product/updates)[NextRoles](/docs/product/roles)\\n\\n#### On this page\\n\\n* [White-label customer email notifications](#whitelabel-customer-email-notifications)\\n* [Reply to the customer on a conversation](#reply-to-the-customer-on-a-conversation)\\n* [Reply to the customer on a ticket](#reply-to-the-customer-on-a-ticket)\\n* [Ticket linked to a",
"title": "Customer email notifications | Computer by DevRev | DevRev"
},
{
"id": "ART-2006_KNOWLEDGE_NODE-25",
"text": "these functionalities can be enabled or disabled.\\n\\nInstallation\\n------------\\n\\n1. Install the [automatic customer reply snap-in](/marketplace/auto-reply) from the DevRev marketplace.\\n2. Select the workspace to install the snap-in, confirm installation, and click **Deploy snap-in**.\\n3. If you want to enable automatic customer response, turn on the **Enable automated reply** toggle.\\n\\n * In the **Automated reply** field, enter the text you want to send as an automated reply.\\n4. To",
"title": "Automatic customer reply | Automate | Snap-ins | DevRev"
},
{
"id": "ART-1953_KNOWLEDGE_NODE-33",
"text": "[[email protected]](mailto:[email protected])\\n* **Subject**: \"CSAT for TKT-XXX\"\\n\\n![]()\\n\\nThis email is only sent to organizations that have installed [CSAT snap-in](https://docs.devrev.ai/automations/csat-conv).\\n\\nAuto customer reply\\n-------------------\\n\\n* **Trigger**: A new conversation is initiated from a customer.\\n* **Action**: An automated reply is sent.\\n* **Sender**: {Company\\\\_Name} [[email protected]](mailto:[email protected])\\n* **Subject**: \"<customer email",
"title": "Customer email notifications | Computer by DevRev | DevRev"
},
{
"id": "ART-4020_KNOWLEDGE_NODE-24",
"text": "[Documentation](/docs)\\n3. [Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Send customized emails](/docs/automations/send-emails)\\n\\nSend customized emails\\n======================\\n\\nThe [**send customized emails**](https://marketplace.devrev.ai/marketplace/send-emails) snap-in automates email sending. Once activated, this operation becomes available in the Workflow builder, enabling the delivery of personalized messages.\\n\\nConfiguration\\n-------------\\n\\n1. Create a **SendGrid**",
"title": "Send customized emails | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2912_KNOWLEDGE_NODE-24",
"text": "[Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Ticket email notifier](/docs/automations/ticket-email-notifier)\\n\\nTicket email notifier\\n=====================\\n\\nThe Ticket Email Notifier snap-in automates email notifications for specific ticket subtypes. When a ticket of the chosen subtype is created, it generates and sends a customized email.\\n\\n![]()\\n\\nFor more information, refer to the [Ticket email notifier snap-in](https://marketplace.devrev.ai/ticket-email-notifier) on the",
"title": "Ticket email notifier | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2912_KNOWLEDGE_NODE-25",
"text": "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 **Ticket email notifier** and click **Install**.\\n3. In DevRev, **Snap-ins** > **Ticket email notifier** > **Configure**.\\n4. Select SendGrid connection and **Connect**.\\n5. Enter the required parameters like **Subtypes**, **Recipient name**, **Subject**, **Introductory part**, **Table contents**, and",
"title": "Ticket email notifier | Automate | Snap-ins | DevRev"
},
{
"id": "ART-4020_KNOWLEDGE_NODE-25",
"text": "account.\\n2. Generate an **API key**.\\n3. Create a SendGrid connection:\\n a. Go to **Settings** > **Snap-ins** > **+ Connection**\\n b. Select **SendGrid**.\\n c. Add the **API key** and click **Save**.\\n\\nInstallation\\n------------\\n\\n1. Install the [**send customized emails**](https://marketplace.devrev.ai/marketplace/send-emails) from the DevRev marketplace.\\n2. Open the Workflow Builder and locate the **send customized emails** action node.\\n3. Configure the node by selecting the",
"title": "Send customized emails | Automate | Snap-ins | DevRev"
},
{
"id": "ART-1953_KNOWLEDGE_NODE-27",
"text": "conversation, ensuring seamless and continuous communication.\\n\\nBy default, notifications are sent from [[email protected]](mailto:[email protected]). However, this setting can be overridden to use the organization\\xe2\\x80\\x99s primary email address as the sender, or notifications can be turned off entirely.\\n\\nTo configure the notifications setting, under [**Settings** > **Snap-ins** > **Email Integration**](https://app.devrev.ai/devrev/settings/snap-ins/email-with-tickets), go to",
"title": "Customer email notifications | Computer by DevRev | DevRev"
}
] |
85211e38-8901-49a2-8ae0-bdfa7964ff19
|
Voice/Video Support - VoIP integration with call recording and transcription
|
[
{
"id": "ART-2034_KNOWLEDGE_NODE-25",
"text": "recording, caller identity, and call transcript, enabling the support team to maintain a complete context of the customer's problem.\\n\\nPrerequisites\\n-------------\\n\\n* Ensure you have a Twilio account.\\n\\n If you would like to provide live call support, you need a Twilio Flex account. If voice notes are adequate for your business requirements, a Twilio account suffices.\\n* Configure the required [IVR](https://www.twilio.com/docs/flex/admin-guide/tutorials/ivr) on Twilio.\\n* Obtain [Twilio",
"title": "Twilio | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-15701_KNOWLEDGE_NODE-9",
"text": "information.\\n\\nDevRev recommends to switch on both agent and customer recording and realtime and post call analytics.\\n\\nCapturing user input in IVR: If you are taking inputs from user in the IVR and you want that information to be visible to the agent/ captured in the call, use set contact attributes block. Store the keys in the User Defined Namespace and add the key which needs to be displayed/ captured. For eg: previous_ticket_id is being captured by the user input.\\n\\nAdd users: Navigate",
"title": "Amazon Connect Telephony Integration Guide"
},
{
"id": "ART-15701_KNOWLEDGE_NODE-8",
"text": "View Phone numbersb. Click on Claim a numberc. Choose the channel as Voice and select the desired country code for the phone number. AWS will provide the list of available phone numbers. Select the desired one. d. Choose the Sample Inbound Flow (Default flow created by AWS) e. Click on Save\\n\\nIVR Setup: Navigate to flows from the left nav\\n\\nFor Recordings and Transcripts: The set recording and analytics behavior block in the start of the IVR Flow is necessary to record all the call",
"title": "Amazon Connect Telephony Integration Guide"
},
{
"id": "ART-15701_KNOWLEDGE_NODE-16",
"text": "created\\n\\nEnter the SSO URL in case you have configured SAML login as identity management in amazon connect instance.\\n\\nEnter the complete S3 Bucket names and path for call recording and transcript. The complete bucket names and path can be found here. Copy the complete path directly.\\n\\nSelect Invite All checkbox if you would like to invite all the support agents to DevRev workspace if not present.\\n\\nClick on install snap-in.\\n\\nAfter the snap-in status shows Active, go to the configured",
"title": "Amazon Connect Telephony Integration Guide"
},
{
"id": "ART-15701_KNOWLEDGE_NODE-20",
"text": "AWS Service, Amazon S3 Event Notification as the Event type, Object Created event and specify the recording and transcript bucket name. Rest all steps will remain the same. The connection created in previous step can be used for this event bridge rule as well.\\n\\nGo to Amazon S3 > Buckets. Go to the bucket where recording and transcript is being stored. Go to Properties and switch on Send notifications to Amazon EventBridge for all events in this bucket under Event notifications.\\n\\nWhenever",
"title": "Amazon Connect Telephony Integration Guide"
},
{
"id": "ART-15616_KNOWLEDGE_NODE-12",
"text": "support quality Feature Comparison Matrix\\n\\nFeature\\n\\nDevRev\\n\\nZendesk\\n\\nAI Agents with reasoning\\n\\n\\xe2\\x9c\\x85\\n\\n\\xe2\\x9d\\x8c\\n\\nIn-app AI Search\\n\\n\\xe2\\x9c\\x85\\n\\n\\xe2\\x9d\\x8c\\n\\nAI-powered clustering\\n\\n\\xe2\\x9c\\x85\\n\\n\\xe2\\x9d\\x8c\\n\\nVoice capabilities\\n\\n\\xe2\\x9d\\x8c\\n\\n\\xe2\\x9c\\x85\\n\\nCustom reports & dashboards\\n\\n\\xe2\\x9c\\x85\\n\\n\\xe2\\x9c\\x85\\n\\nWorkforce management\\n\\n\\xe2\\x9d\\x8c\\n\\n\\xe2\\x9c\\x85\\n\\nNative session analytics\\n\\n\\xe2\\x9c\\x85\\n\\n\\xe2\\x9d\\x8c\\n\\nBuilt-in Incident",
"title": "Zendesk - Competitive - for the PLuG on website"
}
] |
430135d6-8258-4117-bb31-dbc249ae678b
|
DevRev support for Webhooks real-time event notifications
|
[
{
"id": "ART-1459_KNOWLEDGE_NODE-11",
"text": "HTTP server. In the above example, you may be interested in `work_created` and `work_deleted`.\\n\\n 3. Register webhook endpoint\\n\\nBefore webhook events can be processed, you must inform DevRev of the URL where the events should be delivered, along with the specific event types that you are interested in. As a result of this registration, DevRev passes back a secret that is used to verify requests. This secret is never provided when invoking a webhook, only when you call into DevRev (using",
"title": "Webhooks — DevRev | Docs"
},
{
"id": "ART-1459_KNOWLEDGE_NODE-4",
"text": "you must register the endpoint\\xe2\\x80\\x99s URL with DevRev by creating a webhook object that is associated with your Dev org. After successful registration and verification of the endpoint, DevRev issues HTTP requests (that is, invoke the endpoint) for all events that match the event types that the webhook is registered for. Your HTTP server receives an event\\xe2\\x80\\x99s information, verify it using the event\\xe2\\x80\\x99s provided metadata, and return a response indicating successful",
"title": "Webhooks — DevRev | Docs"
},
{
"id": "ART-1264_KNOWLEDGE_NODE-10",
"text": "in order\\n to avoid overwhelming your HTTP server.\\n In the above example, you may be interested in `work_created` and `work_deleted`.\\n3. Register webhook endpoint\\n\\n Before webhook events can be processed, you must inform DevRev of the URL where the events should be\\n delivered, along with the specific event types that you are interested in.\\n As a result of this registration, DevRev passes back a secret that is used to\\n verify requests. This secret is never provided when",
"title": "Webhooks | DevRev | Docs"
},
{
"id": "ART-1264_KNOWLEDGE_NODE-2",
"text": "on the DevRev platform.\\nA webhook can be thought of as a \\xe2\\x80\\x98reverse API\\xe2\\x80\\x99 that\\xe2\\x80\\x99s driven by events rather than requests. While APIs are used to pull data from the system, webhooks are a mechanism for the system to push data to a pre-configured endpoint.\\nWebhooks allow you to receive notifications based on events without having to explicitly make a request.\\n\\nWebhook workflow\\n----------------\\n\\nYou must first set up an HTTP server that listens on a publicly",
"title": "Webhooks | DevRev | Docs"
},
{
"id": "ART-4063_KNOWLEDGE_NODE-1",
"text": "__\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[API Reference](/public/api-reference/getting-started)[Webhooks](/public/api-reference/webhooks/event-responses)\\n\\n# Event Webhooks\\n\\nPOST\\n\\nhttps://api.devrev.ai/webhooks.event\\n\\nTry it\\n\\nDescribes a webhook invocation for an event from DevRev to a webhook\\xe2\\x80\\x99s target URL, where the receiving handler must implement the specified protocol. Note the",
"title": "Event Webhooks — DevRev | Docs"
},
{
"id": "ART-15268_KNOWLEDGE_NODE-0",
"text": "b'Event Webhooks | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[webhooks](/api-reference/webhooks/event-responses)\\n\\nEvent Webhooks\\n==============\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/webhooks.event\\n\\nPOST\\n\\n/webhooks.event\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/webhooks.event \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -H",
"title": "Event Webhooks | DevRev | Docs"
},
{
"id": "ART-1459_KNOWLEDGE_NODE-9",
"text": "invocations such that any non-trivial processing is done asynchronously. If a response isn\\xe2\\x80\\x99t returned within 3 seconds, the invocation will be aborted and retried at a later time.\\n\\n## Steps to set up and receive webhooks\\n\\nLet us use an example to walk through how webhooks can be set up. You are building a work distribution system, and would like to be notified anytime a new work item is created or deleted on DevRev.\\n\\nYou can start receiving event notifications using the",
"title": "Webhooks — DevRev | Docs"
},
{
"id": "ART-1234_KNOWLEDGE_NODE-0",
"text": "b'Event responses | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[webhooks](/api-reference/webhooks/event-responses)\\n\\nEvent responses\\n===============\\n\\nCopy page\\n\\n`webhooks` endpoint\\n\\n\\xe2\\x84\\xb9\\xef\\xb8\\x8f Webhooks enable building custom workflows in response to events on the DevRev platform. A webhook can be thought of as a \\xe2\\x80\\x98reverse API\\xe2\\x80\\x99 that\\xe2\\x80\\x99s driven",
"title": "Event responses | DevRev | Docs"
},
{
"id": "ART-1264_KNOWLEDGE_NODE-3",
"text": "accessible endpoint.\\nWhen ready, you must register the endpoint\\xe2\\x80\\x99s URL with DevRev by creating a webhook object that is\\nassociated with your Dev org. After successful registration and verification of the endpoint,\\nDevRev issues HTTP requests (that is, invoke the endpoint) for all events that match the event types\\nthat the webhook is registered for. Your HTTP server receives an event\\xe2\\x80\\x99s information,\\nverify it using the event\\xe2\\x80\\x99s provided metadata, and return a",
"title": "Webhooks | DevRev | Docs"
},
{
"id": "ART-1272_KNOWLEDGE_NODE-8",
"text": "collect events from webhooks, emails, and timer-based API calls. Events can also be manually published. DevRev supports the ingestion of webhooks from any source. Each event source is assigned to a dev org.\\n\\nFor example, if you want to collect webhook events from an organization\\xe2\\x80\\x99s GitHub, create an event source that gives you a URL to subscribe to on GitHub. Webhook events published to this URL are available from this event source.\\n\\nFunction\\n--------\\n\\nThe framework for",
"title": "Concepts | DevRev | Docs"
},
{
"id": "ART-1459_KNOWLEDGE_NODE-17",
"text": "events to the webhook endpoint. The APIs for standard CRUDL behavior for webhooks are found in the API methods section.\\n\\n## Webhook failure handling\\n\\nTo mitigate intermittent and/or transient failures, DevRev retries unacknowledged webhooks invocations. By default, three attempts are made: the first immediately, the second after a 30-second delay, and the third after a three-minute delay. If sustained failures are encountered, the webhook service marks the webhook endpoint to be in a",
"title": "Webhooks — DevRev | Docs"
},
{
"id": "ART-1478_KNOWLEDGE_NODE-10",
"text": "\"status_code\": 400 \\n 20| } \\n 21| }\\n[/code] \\n \\n## DevRev Webhook\\n\\nThe `devrev-webhook` event source can be used to listen for events occuring on DevRev. These includes events like `work_created` and `conversation_updated`. The payload of the events is defined by the Webhooks Event Schema.\\n\\n### Webhook-event-request example:\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"account_created\": { \\n 3| \"account\": { \\n 4| \"created_by\": {},",
"title": "Event sources — DevRev | Docs"
},
{
"id": "ART-1459_KNOWLEDGE_NODE-13",
"text": "--header \\'Content-Type: application/json\\' --data-raw \\n >| \\'{ \\n >| \"event_types\": [\"work_created\", \"work_deleted\"], \\n >| \"url\": \"your-webhook-endpoint-url\" \\n >| }\\'\\n[/code] \\n \\nThe following response is sent by DevRev\\n\\n### Webhook create response `[json]`\\n\\n[code]\\n\\n 1| 201 Created \\n ---|--- \\n 2| \\n 3| { \\n 4| \"webhook\": { \\n 5| \\t \"id\": \"don:integration:dvrv-us-1:devo/123:webhook/234\", \\n 6| \\t",
"title": "Webhooks — DevRev | Docs"
},
{
"id": "ART-1264_KNOWLEDGE_NODE-0",
"text": "b'Webhooks | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\nOn this page\\n\\n* [Webhook workflow](/guides/webhooks#webhook-workflow)\\n* [Webhook event handling](/guides/webhooks#webhook-event-handling)\\n* [Event POST [json]](/guides/webhooks#event-post-json)\\n* [Steps to set up and receive webhooks](/guides/webhooks#steps-to-set-up-and-receive-webhooks)\\n* [Webhook create request [bash]](/guides/webhooks#webhook-create-request-bash)\\n* [Webhook",
"title": "Webhooks | DevRev | Docs"
},
{
"id": "ART-1459_KNOWLEDGE_NODE-14",
"text": "\"event_types\": [\"work_created\", \"work_deleted\"], \\n 7| \\t \"url\": \"your-webhook-endpoint-url\" \\n 8| \\t \"secret\": secret-string, \\n 9| \\t \"status\": \"unverified\" \\n 10| } \\n 11| }\\n[/code] \\n \\nAfter creation, DevRev sends a verify request to verify the endpoint is reachable and was intentionally created by the owner (that is, not a malicious client using a URL that they don\\xe2\\x80\\x99t own). To perform a successful verification, your endpoint must echo the",
"title": "Webhooks — DevRev | Docs"
},
{
"id": "ART-1284_KNOWLEDGE_NODE-8",
"text": "input.request.body |\\n| 16 | event_key := \"argocd.workflow\" |\\n| 17 | } else = {\"response\": response } { |\\n| 18 | response := { |\\n| 19 | \"status_code\": 400 |\\n| 20 | } |\\n| 21 | } |\\n```\\n\\nDevRev Webhook\\n--------------\\n\\nThe `devrev-webhook` event source can be used to listen for events occuring on DevRev. These includes events like `work_created` and `conversation_updated`.\\nThe payload of the events is defined by the Webhooks Event Schema.\\n\\n### Webhook-event-request example:\\n\\n```\\n|",
"title": "Event sources | DevRev | Docs"
},
{
"id": "ART-1459_KNOWLEDGE_NODE-5",
"text": "reception. The types of events that can be received through webhooks are object mutation events (create, update, delete). Events are delivered concurrently in a semi-ordered (but not guaranteed) manner, where object timestamps and versions enable you to determine the order of events for a particular object.\\n\\nDevRevCustomer endpointDevRevCustomer endpoint1\\\\. Register webhook2\\\\. Verify webhook registration3\\\\. Receive webhook eventWebhook create requestWebhook create responseVerify",
"title": "Webhooks — DevRev | Docs"
},
{
"id": "ART-1439_KNOWLEDGE_NODE-0",
"text": "b'[](/public/api-reference/webhooks/event-responses)\\n\\nPublic\\n\\n[API Reference](/public/api-reference/getting-started)[Webhooks](/public/api-reference/webhooks/event-responses)\\n\\n#\\n\\nEvent responses\\n\\n`webhooks` endpoint\\n\\n\\xe2\\x84\\xb9\\xef\\xb8\\x8f Webhooks enable building custom workflows in response to events on the DevRev platform. A webhook can be thought of as a \\xe2\\x80\\x98reverse API\\xe2\\x80\\x99 that\\xe2\\x80\\x99s driven by events rather than requests. While APIs are used to pull data",
"title": "Event responses — DevRev | Docs"
},
{
"id": "ART-1366_KNOWLEDGE_NODE-4",
"text": "[webhooks](/public/guides/webhooks) are also supported.\\n\\n[Public](/public)[Beta](/beta)\\n\\n## \\xf0\\x9f\\xa7\\xa9 Snap-ins\\n\\nNumerous snap-ins are available on the DevRev [Marketplace](https://devrev.ai/marketplace). The [snap-in framework](/public/snapin-development/concepts) is available for you to create your own snap-ins for automation of DevRev workflows or integration with other system.\\n\\n## \\xf0\\x9f\\x92\\xbb SDKs\\n\\n[PLuG Web SDK](/public/sdks/web/installation)[DevRev SDK for",
"title": "For Developers — DevRev | Docs"
},
{
"id": "ART-1264_KNOWLEDGE_NODE-4",
"text": "response indicating successful reception.\\nThe types of events that can be received through webhooks are object mutation events (create, update, delete).\\nEvents are delivered concurrently in a semi-ordered (but not guaranteed) manner,\\nwhere object timestamps and versions enable you to determine the order of events for a particular object.\\n\\nDevRevCustomer endpointDevRevCustomer endpoint1. Register webhook2. Verify webhook registration3. Receive webhook eventWebhook create requestWebhook",
"title": "Webhooks | DevRev | Docs"
},
{
"id": "ART-1264_KNOWLEDGE_NODE-12",
"text": "--header \"Authorization: Bearer <TOKEN>\" |\\n| > | --header \\'Content-Type: application/json\\' --data-raw |\\n| > | \\'{ |\\n| > | \"event_types\": [\"work_created\", \"work_deleted\"], |\\n| > | \"url\": \"your-webhook-endpoint-url\" |\\n| > | }\\' |\\n```\\n\\nThe following response is sent by DevRev\\n\\n### Webhook create response `[json]`\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | 201 Created |\\n| 2 | |\\n| 3 | { |\\n| 4 | \"webhook\": { |\\n| 5 | \"id\": \"don:integration:dvrv-us-1:devo/123:webhook/234\", |\\n| 6 |",
"title": "Webhooks | DevRev | Docs"
},
{
"id": "ART-1264_KNOWLEDGE_NODE-8",
"text": "invocations such that any non-trivial processing is done asynchronously. If a response isn\\xe2\\x80\\x99t returned within 3 seconds, the invocation will be aborted and retried at a later time.\\n\\nSteps to set up and receive webhooks\\n------------------------------------\\n\\nLet us use an example to walk through how webhooks can be set up.\\nYou are building a work distribution system, and would like to be notified anytime a new work item\\nis created or deleted on DevRev.\\n\\nYou can start receiving",
"title": "Webhooks | DevRev | Docs"
},
{
"id": "ART-4206_KNOWLEDGE_NODE-16",
"text": "endpoint in your application that can receive POST requests.\\n2. Register this endpoint with DevRev using the webhooks.create API.\\n3. Make async API calls with your agent ID and webhook ID.\\n4. Process incoming webhook events to:\\n * Track progress (optional).\\n * Display the final agent response to the user.\\n * Handle any errors.\\n\\nExample flow for a chat application:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | // 1. When user sends a message |\\n| 2 | function handleUserMessage(message) {",
"title": "Agents async API | DevRev | Docs"
},
{
"id": "ART-1264_KNOWLEDGE_NODE-13",
"text": "\"event_types\": [\"work_created\", \"work_deleted\"], |\\n| 7 | \"url\": \"your-webhook-endpoint-url\" |\\n| 8 | \"secret\": secret-string, |\\n| 9 | \"status\": \"unverified\" |\\n| 10 | } |\\n| 11 | } |\\n```\\n\\nAfter creation, DevRev sends a verify request to verify the endpoint is reachable and was intentionally\\ncreated by the owner (that is, not a malicious client using a URL that they don\\xe2\\x80\\x99t own).\\nTo perform a successful verification, your endpoint must echo the provided challenge within 3 mins of",
"title": "Webhooks | DevRev | Docs"
},
{
"id": "ART-2599_KNOWLEDGE_NODE-25",
"text": "DevRev,\\nDevRev webhook is triggered and corresponding changes are reflected in Datadog.\\nTimeline entries are synced one-way\\xe2\\x80\\x94from DevRev to Datadog.\\n\\nInstallation\\n------------\\n\\n1. Open the DevRev marketplace and install the **Datadog** snap-in.\\n2. Select the workspace where you want to install the snap-in, confirm your\\n selection, and click **Deploy snap-in**.\\n3. In DevRev app, setup the connection in **Settings** > **Snap-ins** >\\n **Connections** on top.\\n * Search",
"title": "Datadog | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-1284_KNOWLEDGE_NODE-3",
"text": "URL |\\n| --- | --- | --- | --- | --- |\\n| devrev-webhook | DevRev webhook | All supported DevRev webhook event types | DevRev webhook events such as `work_created` and `conversation_updated` | [DevRev Webhook](/snapin-development/references/event-sources#devrev-webhook) |\\n| flow-events | Flow Events | Configurable | Event sources schedule and publish events directly from a snap-in. | [Scheduled events](/snapin-development/references/event-sources#scheduled-events) |\\n| flow-custom-webhook |",
"title": "Event sources | DevRev | Docs"
},
{
"id": "ART-1264_KNOWLEDGE_NODE-16",
"text": "behavior for webhooks are found in the API methods section.\\n\\nWebhook failure handling\\n------------------------\\n\\nTo mitigate intermittent and/or transient failures, DevRev retries unacknowledged webhooks invocations. By default, three attempts are made: the first immediately, the second after a 30-second delay, and the third after a three-minute delay. If sustained failures are encountered, the webhook service marks the webhook endpoint to be in a degraded state and it\\xe2\\x80\\x99ll fail",
"title": "Webhooks | DevRev | Docs"
},
{
"id": "ART-1459_KNOWLEDGE_NODE-12",
"text": "TLS), however the webhook request contains a derivative of the secret that you will use to verify DevRev as the originator.\\n\\n[API Reference: Create Webhook](/public/api-reference/webhooks/create)\\n\\nYou will invoke DevRev webhook create with the following fields for our example:\\n\\n### Webhook create request `[bash]`\\n\\n[code]\\n\\n $| curl --request POST \\'https://api.devrev.ai/webhooks.create\\' \\n ---|--- \\n >| --header \"Authorization: Bearer <TOKEN>\" \\n >|",
"title": "Webhooks — DevRev | Docs"
},
{
"id": "ART-1459_KNOWLEDGE_NODE-7",
"text": "POST `[json]`\\n\\nEvent POST from DevRev to your endpoint\\n\\n[code]\\n\\n 1| POST your-webhook-endpoint-url \\n ---|--- \\n 2| X-DevRev-Signature: z1BY0e8JYzEGfxZ8e4k8agCdWQyTr2An \\n 3| \\n 4| { \\n 5| \\t\"id\": \"don:integration:dvrv-us-1:devo/1H79gci4u/webhook/123:event/abcdef\", \\n 6| \\t\"webhook_id\": \"don:integration:dvrv-us-1:devo/1H79gci4u/webhook/123\", \\n 7| \\t\"timestamp\": \"2022-08-01T12:00:00.123456789Z\", \\n 8| \\t\"type\": \"work_created\", \\n 9|",
"title": "Webhooks — DevRev | Docs"
},
{
"id": "ART-1284_KNOWLEDGE_NODE-17",
"text": "the DevRev API to schedule an event for this event source. The following example illustrates how this works:\\n\\n`manifest.yaml`\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | version: \"2\" |\\n| 2 | |\\n| 3 | service_account: |\\n| 4 | display_name: Test bot |\\n| 5 | |\\n| 6 | event_sources: |\\n| 7 | organization: |\\n| 8 | - name: devrev-webhook |\\n| 9 | description: Event coming from DevRev |\\n| 10 | display_name: DevRev |\\n| 11 | type: devrev-webhook |\\n| 12 | config: |\\n| 13 | event_types: |\\n| 14 | -",
"title": "Event sources | DevRev | Docs"
},
{
"id": "ART-1264_KNOWLEDGE_NODE-6",
"text": "event\\xe2\\x80\\x99s data.\\n\\n### Event POST `[json]`\\n\\nEvent POST from DevRev to your endpoint\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | POST your-webhook-endpoint-url |\\n| 2 | X-DevRev-Signature: z1BY0e8JYzEGfxZ8e4k8agCdWQyTr2An |\\n| 3 | |\\n| 4 | { |\\n| 5 | \"id\": \"don:integration:dvrv-us-1:devo/1H79gci4u/webhook/123:event/abcdef\", |\\n| 6 | \"webhook_id\": \"don:integration:dvrv-us-1:devo/1H79gci4u/webhook/123\", |\\n| 7 | \"timestamp\": \"2022-08-01T12:00:00.123456789Z\", |\\n| 8 | \"type\": \"work_created\",",
"title": "Webhooks | DevRev | Docs"
},
{
"id": "ART-1468_KNOWLEDGE_NODE-9",
"text": "use connections to pass secret values to corresponding functions.\\n\\n## Event source\\n\\n[Event sources](/public/snapin-development/references/event-sources) collect events from webhooks, emails, and timer-based API calls. Events can also be manually published. DevRev supports the ingestion of webhooks from any source. Each event source is assigned to a dev org.\\n\\nFor example, if you want to collect webhook events from an organization\\xe2\\x80\\x99s GitHub, create an event source that gives you a",
"title": "Concepts — DevRev | Docs"
},
{
"id": "ART-4063_KNOWLEDGE_NODE-11",
"text": "request types.\\n\\n### Errors\\n\\n400\\n\\nBad Request Error\\n\\n401\\n\\nUnauthorized Error\\n\\n403\\n\\nForbidden Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nPOST\\n\\n/webhooks.event\\n\\n[code]\\n\\n $| curl -X POST https://api.devrev.ai/webhooks.event \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer <token>\" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"id\": \"foo\", \\n >|",
"title": "Event Webhooks — DevRev | Docs"
},
{
"id": "ART-1264_KNOWLEDGE_NODE-15",
"text": "\"DlrVaK7zRyZWwbJhj5dZHDlrVaK7Jhj5dZZjH\" |\\n| 10 | } |\\n| 11 | } |\\n```\\n\\nThe following response is expected from your endpoint\\n\\n### Echo challenge `[json]`\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | 200 OK |\\n| 2 | |\\n| 3 | { |\\n| 4 | \"challenge\": \"DlrVaK7zRyZWwbJhj5dZHDlrVaK7Jhj5dZZjH\" |\\n| 5 | } |\\n```\\n\\nYou are all set.\\nOnce verified, the status of the webhook is updated to be active and DevRev begins to deliver\\nthe subscribed events to the webhook endpoint.\\nThe APIs for standard CRUDL",
"title": "Webhooks | DevRev | Docs"
},
{
"id": "ART-1235_KNOWLEDGE_NODE-0",
"text": "b'Create Webhook | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[webhooks](/api-reference/webhooks/event-responses)\\n\\nCreate Webhook\\n==============\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/webhooks.create\\n\\nPOST\\n\\n/webhooks.create\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/webhooks.create \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -H",
"title": "Create Webhook | DevRev | Docs"
},
{
"id": "ART-1264_KNOWLEDGE_NODE-11",
"text": "invoking a webhook, only when you call into DevRev\\n (using TLS), however the webhook request contains a derivative of the secret that you will use to verify\\n DevRev as the originator.\\n\\n [API Reference: Create Webhook](/api-reference/webhooks/create)\\n\\n You will invoke DevRev webhook create with the following fields for our example:\\n\\n### Webhook create request `[bash]`\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl --request POST \\'https://api.devrev.ai/webhooks.create\\' |\\n| > |",
"title": "Webhooks | DevRev | Docs"
},
{
"id": "ART-15495_KNOWLEDGE_NODE-0",
"text": "b'March 3, 2025 | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[Changelog\\n=========](/changelog)\\n\\n[March 3, 2025](/changelog/2025/3/3)\\n\\n[March 3, 2025](/changelog/2025/3/3)\\n\\nNew Endpoints\\n-------------\\n\\n### Webhooks\\n\\n* Added [`POST /webhooks.event`](/api-reference/webhooks/event) as an *exposition* endpoint for what webhook handlers must support\\n\\nModified Endpoints\\n------------------\\n\\n### Parts\\n\\n* Added new properties to",
"title": "March 3, 2025 | DevRev | Docs"
},
{
"id": "ART-1459_KNOWLEDGE_NODE-2",
"text": "[json]](/public/guides/webhooks#webhook-create-response-json)\\n * [Verify request [json]](/public/guides/webhooks#verify-request-json)\\n * [Echo challenge [json]](/public/guides/webhooks#echo-challenge-json)\\n * [Webhook failure handling](/public/guides/webhooks#webhook-failure-handling)\\n * [Webhook security](/public/guides/webhooks#webhook-security)\\n\\n[Guides](/public/guides/webhooks)\\n\\n#\\n\\nWebhooks\\n\\nWebhooks allow you to build custom workflows in response to events on the DevRev",
"title": "Webhooks — DevRev | Docs"
},
{
"id": "ART-4206_KNOWLEDGE_NODE-5",
"text": "| \"value\": \"your-secret-key\" |\\n| > | } |\\n| > | ] |\\n| > | }\\' |\\n```\\n\\nSave the webhook ID from the response (format: `don:integration:dvrv-us-1:devo/0:webhook/auCJ7By8`). You need this when making async API calls.\\n\\nMake sure that your webhook endpoint can appropriately respond to the verify events sent by DevRev to verify your webhook. This verify event has a challenge string which you need to return in response. You return the response like this:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | 200",
"title": "Agents async API | DevRev | Docs"
},
{
"id": "ART-1353_KNOWLEDGE_NODE-3",
"text": "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",
"title": "For Developers | DevRev | Docs"
},
{
"id": "ART-15268_KNOWLEDGE_NODE-1",
"text": "\"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{ |\\n| > | \"id\": \"string\", |\\n| > | \"webhook_id\": \"don:integration:dvrv-us-1:devo/example:webhook/webhook-id\" |\\n| > | }\\' |\\n```\\n\\n[Try it](/api-reference/webhooks/event?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"challenge\": \"string\" |\\n| 3 | } |\\n```\\n\\nDescribes a webhook invocation for an event from DevRev to a webhook\\'s\\ntarget URL, where the receiving handler must implement the specified\\nprotocol.",
"title": "Event Webhooks | DevRev | Docs"
},
{
"id": "ART-1312_KNOWLEDGE_NODE-1",
"text": "perform a variety of actions, including rendering them in UI and generating SDKs. Two versions of the DevRev API are available: public and beta (early access). Use the drop-down menu in the upper-left corner of this site to switch between versions.\\nTo take action based on events from the DevRev platform, webhooks are also supported.\\n\\n\\xf0\\x9f\\xa7\\xa9 Snap-ins\\nNumerous snap-ins are available on the DevRev Marketplace. The snap-in framework is available for you to create your own snap-ins for",
"title": "For Developers – DevRev | Docs"
},
{
"id": "ART-1831_KNOWLEDGE_NODE-448",
"text": "Create.\\n\\nPOST https:// api.devrev.ai / webhooks.create\\nCreates a new webhook target.\\nRequest.\\n\\nThis endpoint expects an object.\\nurl string Required\\nThe URL of the webhook endpoint.\\nevent_types list of enums Optional\\nThe event types that the webhook endpoint will receive.\\nShow 49 enum values\\nheaders list of objects Optional\\nThe headers to include in every webhook invocation.\\nShow 2 properties\\nsecret string Optional\\nThe secret to use when verifying webhook events. If provided, the",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1277_KNOWLEDGE_NODE-2",
"text": "is on the process of working with the payload associated with these events. The objective is to adeptly extract pertinent fields from the payload within the defined functions, subsequently executing a well-defined action. This action involves the addition of a comment to the object timeline, a feature that can be conveniently customized.\\n\\nBackground context\\n------------------\\n\\n1. **Webhook event handling**: Understand the intricacies of responding to a\\n DevRev webhook event,",
"title": "Snap-in triggered by a DevRev event | DevRev | Docs"
},
{
"id": "ART-1264_KNOWLEDGE_NODE-17",
"text": "any queued events without invocation attempts. When in this state, verify requests are restarted to determine when the endpoint becomes healthy again and eventually promoted back to the active state.\\n\\nWebhook security\\n----------------\\n\\nA header signature `X-DevRev-Signature` is always provided, which is a hash-based message authentication code (HMAC) utilizing SHA256 consisting of the secret as the key and the raw request payload as the message. Any adversary that intercepts and modifies",
"title": "Webhooks | DevRev | Docs"
},
{
"id": "ART-1459_KNOWLEDGE_NODE-16",
"text": "\"verify\": { \\n 9| \\t\\t\"challenge\": \"DlrVaK7zRyZWwbJhj5dZHDlrVaK7Jhj5dZZjH\" \\n 10| } \\n 11| }\\n[/code] \\n \\nThe following response is expected from your endpoint\\n\\n### Echo challenge `[json]`\\n\\n[code]\\n\\n 1| 200 OK \\n ---|--- \\n 2| \\n 3| { \\n 4| \"challenge\": \"DlrVaK7zRyZWwbJhj5dZHDlrVaK7Jhj5dZZjH\" \\n 5| }\\n[/code] \\n \\nYou are all set. Once verified, the status of the webhook is updated to be active and DevRev begins to deliver the subscribed",
"title": "Webhooks — DevRev | Docs"
},
{
"id": "ART-1838_KNOWLEDGE_NODE-439",
"text": "https://api.devrev.ai/webhooks.update \\\\ > -H \" Authorization: Bearer <token> \" \\\\ > -H \" Content-Type: application/json \" \\\\ > -d \\' { > \"id\": \"don:integration:<partition>:devo/<dev-org-id>:webhook/<webhook-id>\" > } \\'\\n200 Successful 1 { 2 \" webhook \" : { 3 \" created_date \" : \" 2023-01-01T12:00:00Z \" , 4 \" display_id \" : \" display_id \" , 5 \" id \" : \" id \" , 6 \" modified_date \" : \" 2023-01-01T12:00:00Z \" , 7 \" event_types \" : [ 8 \" account_created \" 9 ] , 10 \" headers \" : [ 11 { 12 \" name \" :",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1834_KNOWLEDGE_NODE-431",
"text": "webhooks.create\\ncURL\\n$ curl -X POST https://api.devrev.ai/webhooks.create \\\\ > -H \" Authorization: Bearer <token> \" \\\\ > -H \" Content-Type: application/json \" \\\\ > -d \\' { > \"url\": \"url\" > } \\'\\n200 Successful 1 { 2 \" webhook \" : { 3 \" created_date \" : \" 2023-01-01T12:00:00Z \" , 4 \" display_id \" : \" display_id \" , 5 \" id \" : \" id \" , 6 \" modified_date \" : \" 2023-01-01T12:00:00Z \" , 7 \" event_types \" : [ 8 \" account_created \" 9 ] , 10 \" headers \" : [ 11 { 12 \" name \" : \" name \" , 13 \" value \"",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1564_KNOWLEDGE_NODE-495",
"text": "any.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\n\\nThe list of webhooks.\\n\\nShow 11 properties\\nAPI Reference webhooks Update.\\n\\nPOST https://api.devrev.ai / webhooks.update\\n\\nUpdates the requested webhook.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\n\\nID for the webhook.\\n\\naction \"activate\" or \"deactivate\" Optional\\nAllowed values: activate deactivate\\n\\nThe action to update the webhook\\xe2\\x80\\x99s status.\\n\\nevent_types object",
"title": "List (Beta) — DevRev | Docs"
},
{
"id": "ART-1543_KNOWLEDGE_NODE-494",
"text": "any.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\n\\nThe list of webhooks.\\n\\nShow 11 properties\\nAPI Reference webhooks Update.\\n\\nPOST https://api.devrev.ai / webhooks.update\\n\\nUpdates the requested webhook.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\n\\nID for the webhook.\\n\\naction \"activate\" or \"deactivate\" Optional\\nAllowed values: activate deactivate\\n\\nThe action to update the webhook\\xe2\\x80\\x99s status.\\n\\nevent_types object",
"title": "Metric Definitions List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1549_KNOWLEDGE_NODE-495",
"text": "any.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\n\\nThe list of webhooks.\\n\\nShow 11 properties\\nAPI Reference webhooks Update.\\n\\nPOST https://api.devrev.ai / webhooks.update\\n\\nUpdates the requested webhook.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\n\\nID for the webhook.\\n\\naction \"activate\" or \"deactivate\" Optional\\nAllowed values: activate deactivate\\n\\nThe action to update the webhook\\xe2\\x80\\x99s status.\\n\\nevent_types object",
"title": "List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1562_KNOWLEDGE_NODE-496",
"text": "any.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\n\\nThe list of webhooks.\\n\\nShow 11 properties\\nAPI Reference webhooks Update.\\n\\nPOST https://api.devrev.ai / webhooks.update\\n\\nUpdates the requested webhook.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\n\\nID for the webhook.\\n\\naction \"activate\" or \"deactivate\" Optional\\nAllowed values: activate deactivate\\n\\nThe action to update the webhook\\xe2\\x80\\x99s status.\\n\\nevent_types object",
"title": "Get (Beta) — DevRev | Docs"
},
{
"id": "ART-1547_KNOWLEDGE_NODE-496",
"text": "any.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\n\\nThe list of webhooks.\\n\\nShow 11 properties\\nAPI Reference webhooks Update.\\n\\nPOST https://api.devrev.ai / webhooks.update\\n\\nUpdates the requested webhook.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\n\\nID for the webhook.\\n\\naction \"activate\" or \"deactivate\" Optional\\nAllowed values: activate deactivate\\n\\nThe action to update the webhook\\xe2\\x80\\x99s status.\\n\\nevent_types object",
"title": "Get Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1832_KNOWLEDGE_NODE-440",
"text": "properties\\nPOST / webhooks.create\\ncURL\\n$ curl -X POST https://api.devrev.ai/webhooks.create \\\\ > -H \" Authorization: Bearer <token> \" \\\\ > -H \" Content-Type: application/json \" \\\\ > -d \\' { > \"url\": \"url\" > } \\'\\n200 Successful 1 { 2 \" webhook \" : { 3 \" created_date \" : \" 2023-01-01T12:00:00Z \" , 4 \" display_id \" : \" display_id \" , 5 \" id \" : \" id \" , 6 \" modified_date \" : \" 2023-01-01T12:00:00Z \" , 7 \" event_types \" : [ 8 \" account_created \" 9 ] , 10 \" headers \" : [ 11 { 12 \" name \" : \"",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1277_KNOWLEDGE_NODE-1",
"text": "development](/snapin-development/concepts)[Tutorials](/snapin-development/tutorials/overview)\\n\\nSnap-in triggered by a DevRev event\\n===================================\\n\\nCopy page\\n\\nIntroduction\\n------------\\n\\nIn this tutorial, you\\xe2\\x80\\x99ll learn to create a dynamic snap-in that responds to both DevRev Webhook events triggered by the creation of a [work](https://docs.devrev.ai/product/core) and specialized [command](/snapin-development/references/commands) within DevRev.\\n\\nThe focus",
"title": "Snap-in triggered by a DevRev event | DevRev | Docs"
},
{
"id": "ART-4108_KNOWLEDGE_NODE-1",
"text": "__\\n\\n[Pricing](https://devrev.ai/pricing)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](https://devrev.ai/request-a-demo)\\n\\n[Back to Changelog](/public/changelog)\\n\\n# March 3, 2025\\n\\n## New Endpoints\\n\\n### Webhooks\\n\\n * Added [`POST /webhooks.event`](/public/api-reference/webhooks/event) as an _exposition_ endpoint for what webhook handlers must support\\n\\n## Modified Endpoints\\n\\n### Parts\\n\\n * Added new properties to `enhancement` objects:\\n * `actual_close_date`\\n *",
"title": "March 3, 2025 — DevRev | Docs"
},
{
"id": "ART-1299_KNOWLEDGE_NODE-1",
"text": "Methods.\\n\\nSpecifications covering the supported APIs are based on OpenAPI Specification 3.0. You can download the specs to use an OpenAPI 3.0-compliant tool to perform a variety of actions, including rendering them in UI and generating SDKs. Two versions of the DevRev API are available: public and beta (early access). Use the drop-down menu in the upper-left corner of this site to switch between versions.\\n\\nTo take action based on events from the DevRev platform, webhooks are also",
"title": "For Developers — DevRev | Docs"
},
{
"id": "ART-1459_KNOWLEDGE_NODE-3",
"text": "platform. A webhook can be thought of as a \\xe2\\x80\\x98reverse API\\xe2\\x80\\x99 that\\xe2\\x80\\x99s driven by events rather than requests. While APIs are used to pull data from the system, webhooks are a mechanism for the system to push data to a pre-configured endpoint. Webhooks allow you to receive notifications based on events without having to explicitly make a request.\\n\\n## Webhook workflow\\n\\nYou must first set up an HTTP server that listens on a publicly accessible endpoint. When ready,",
"title": "Webhooks — DevRev | Docs"
},
{
"id": "ART-1307_KNOWLEDGE_NODE-438",
"text": "object\\nShow 11 properties\\nAPI Reference webhooks Get Post.\\n\\nPOST https:// api.devrev.ai / webhooks.get\\nGets the requested webhook\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nID for the webhook.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhook object\\nShow 11 properties\\nAPI Reference webhooks List.\\n\\nGET https:// api.devrev.ai / webhooks.list\\nLists the webhooks.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\nThe",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1834_KNOWLEDGE_NODE-437",
"text": "Update.\\n\\nPOST https:// api.devrev.ai / webhooks.update\\nUpdates the requested webhook.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nID for the webhook.\\naction \"activate\" or \"deactivate\" Optional\\nAllowed values: activate deactivate\\nThe action to update the webhook\\'s status.\\nevent_types object Optional\\nShow 3 properties\\nheaders object Optional\\nShow 3 properties\\nsecret string Optional\\nIf provided, updates the secret that\\'s used when verifying webhook events,",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1781_KNOWLEDGE_NODE-435",
"text": "object\\nShow 11 properties\\nAPI Reference webhooks Get Post.\\n\\nPOST https:// api.devrev.ai / webhooks.get\\nGets the requested webhook\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nID for the webhook.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhook object\\nShow 11 properties\\nAPI Reference webhooks List.\\n\\nGET https:// api.devrev.ai / webhooks.list\\nLists the webhooks.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\nThe",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1801_KNOWLEDGE_NODE-439",
"text": "object\\nShow 11 properties\\nAPI Reference webhooks Get Post.\\n\\nPOST https:// api.devrev.ai / webhooks.get\\nGets the requested webhook\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nID for the webhook.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhook object\\nShow 11 properties\\nAPI Reference webhooks List.\\n\\nGET https:// api.devrev.ai / webhooks.list\\nLists the webhooks.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\nThe",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1788_KNOWLEDGE_NODE-437",
"text": "object\\nShow 11 properties\\nAPI Reference webhooks Get Post.\\n\\nPOST https:// api.devrev.ai / webhooks.get\\nGets the requested webhook\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nID for the webhook.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhook object\\nShow 11 properties\\nAPI Reference webhooks List.\\n\\nGET https:// api.devrev.ai / webhooks.list\\nLists the webhooks.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\nThe",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1791_KNOWLEDGE_NODE-436",
"text": "object\\nShow 11 properties\\nAPI Reference webhooks Get Post.\\n\\nPOST https:// api.devrev.ai / webhooks.get\\nGets the requested webhook\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nID for the webhook.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhook object\\nShow 11 properties\\nAPI Reference webhooks List.\\n\\nGET https:// api.devrev.ai / webhooks.list\\nLists the webhooks.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\nThe",
"title": "Self Delete — DevRev | Docs"
},
{
"id": "ART-1821_KNOWLEDGE_NODE-438",
"text": "object\\nShow 11 properties\\nAPI Reference webhooks Get Post.\\n\\nPOST https:// api.devrev.ai / webhooks.get\\nGets the requested webhook\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nID for the webhook.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhook object\\nShow 11 properties\\nAPI Reference webhooks List.\\n\\nGET https:// api.devrev.ai / webhooks.list\\nLists the webhooks.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\nThe",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1824_KNOWLEDGE_NODE-432",
"text": "api.devrev.ai / webhooks.create\\nCreates a new webhook target.\\nRequest.\\n\\nThis endpoint expects an object.\\nurl string Required\\nThe URL of the webhook endpoint.\\nevent_types list of enums Optional\\nThe event types that the webhook endpoint will receive.\\nShow 49 enum values\\nheaders list of objects Optional\\nThe headers to include in every webhook invocation.\\nShow 2 properties\\nsecret string Optional\\nThe secret to use when verifying webhook events. If provided, the secret must be between 8",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1607_KNOWLEDGE_NODE-437",
"text": "api.devrev.ai / webhooks.create\\nCreates a new webhook target.\\nRequest.\\n\\nThis endpoint expects an object.\\nurl string Required\\nThe URL of the webhook endpoint.\\nevent_types list of enums Optional\\nThe event types that the webhook endpoint will receive.\\nShow 49 enum values\\nheaders list of objects Optional\\nThe headers to include in every webhook invocation.\\nShow 2 properties\\nsecret string Optional\\nThe secret to use when verifying webhook events. If provided, the secret must be between 8",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1818_KNOWLEDGE_NODE-438",
"text": "object\\nShow 11 properties\\nAPI Reference webhooks Get Post.\\n\\nPOST https:// api.devrev.ai / webhooks.get\\nGets the requested webhook\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nID for the webhook.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhook object\\nShow 11 properties\\nAPI Reference webhooks List.\\n\\nGET https:// api.devrev.ai / webhooks.list\\nLists the webhooks.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\nThe",
"title": "Sla Trackers Get Post — DevRev | Docs"
},
{
"id": "ART-1588_KNOWLEDGE_NODE-437",
"text": "api.devrev.ai / webhooks.create\\nCreates a new webhook target.\\nRequest.\\n\\nThis endpoint expects an object.\\nurl string Required\\nThe URL of the webhook endpoint.\\nevent_types list of enums Optional\\nThe event types that the webhook endpoint will receive.\\nShow 49 enum values\\nheaders list of objects Optional\\nThe headers to include in every webhook invocation.\\nShow 2 properties\\nsecret string Optional\\nThe secret to use when verifying webhook events. If provided, the secret must be between 8",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1591_KNOWLEDGE_NODE-439",
"text": "object\\nShow 11 properties\\nAPI Reference webhooks Get Post.\\n\\nPOST https:// api.devrev.ai / webhooks.get\\nGets the requested webhook\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nID for the webhook.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhook object\\nShow 11 properties\\nAPI Reference webhooks List.\\n\\nGET https:// api.devrev.ai / webhooks.list\\nLists the webhooks.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\nThe",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1478_KNOWLEDGE_NODE-17",
"text": "filter returns `false`, the event is not dispatched to the webhook.\\n\\nFor example, to create an event source which listens for issue creation and comments on issues, you can define the event source as follows:\\n\\n[code]\\n\\n 1| event_sources: \\n ---|--- \\n 2| organization: \\n 3| - name: devrev-webhook \\n 4| description: Events coming from DevRev for issues \\n 5| display_name: DevRev webhook \\n 6| type: devrev-webhook \\n 7| config: \\n",
"title": "Event sources — DevRev | Docs"
},
{
"id": "ART-1575_KNOWLEDGE_NODE-441",
"text": "object\\nShow 11 properties\\nAPI Reference webhooks Get Post.\\n\\nPOST https:// api.devrev.ai / webhooks.get\\nGets the requested webhook\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nID for the webhook.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhook object\\nShow 11 properties\\nAPI Reference webhooks List.\\n\\nGET https:// api.devrev.ai / webhooks.list\\nLists the webhooks.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\nThe",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1607_KNOWLEDGE_NODE-439",
"text": "https:// api.devrev.ai / webhooks.fetch\\nFetches an object via webhook.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the webhook to fetch the object for.\\nobject string Required\\nThe ID of the object to fetch for the webhook.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference webhooks Get.\\n\\nGET https:// api.devrev.ai / webhooks.get\\nGets the requested webhook\\'s information.\\nQuery parameters.\\n\\nid string Required\\nID for the",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1478_KNOWLEDGE_NODE-4",
"text": "types\\n\\nEvent source code| Event source name| Event type code| Remarks| Documentation URL \\n---|---|---|---|--- \\ndevrev-webhook| DevRev webhook| All supported DevRev webhook event types| DevRev webhook events such as `work_created` and `conversation_updated`| [DevRev Webhook](/public/snapin-development/references/event-sources#devrev-webhook) \\nflow-events| Flow Events| Configurable| Event sources schedule and publish events directly from a snap-in.| [Scheduled",
"title": "Event sources — DevRev | Docs"
},
{
"id": "ART-1824_KNOWLEDGE_NODE-434",
"text": "https:// api.devrev.ai / webhooks.fetch\\nFetches an object via webhook.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the webhook to fetch the object for.\\nobject string Required\\nThe ID of the object to fetch for the webhook.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference webhooks Get.\\n\\nGET https:// api.devrev.ai / webhooks.get\\nGets the requested webhook\\'s information.\\nQuery parameters.\\n\\nid string Required\\nID for the",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1805_KNOWLEDGE_NODE-438",
"text": "object\\nShow 11 properties\\nAPI Reference webhooks Get Post.\\n\\nPOST https:// api.devrev.ai / webhooks.get\\nGets the requested webhook\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nID for the webhook.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhook object\\nShow 11 properties\\nAPI Reference webhooks List.\\n\\nGET https:// api.devrev.ai / webhooks.list\\nLists the webhooks.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\nThe",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1633_KNOWLEDGE_NODE-444",
"text": "api.devrev.ai / webhooks.update\\nUpdates the requested webhook.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nID for the webhook.\\naction \"activate\" or \"deactivate\" Optional\\nAllowed values: activate deactivate\\nThe action to update the webhook\\'s status.\\nevent_types object Optional\\nShow 3 properties\\nheaders object Optional\\nShow 3 properties\\nsecret string Optional\\nIf provided, updates the secret that\\'s used when verifying webhook events, which must be between 8 and",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1300_KNOWLEDGE_NODE-437",
"text": "object\\nShow 11 properties\\nAPI Reference webhooks Get Post.\\n\\nPOST https:// api.devrev.ai / webhooks.get\\nGets the requested webhook\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nID for the webhook.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhook object\\nShow 11 properties\\nAPI Reference webhooks List.\\n\\nGET https:// api.devrev.ai / webhooks.list\\nLists the webhooks.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\nThe",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1829_KNOWLEDGE_NODE-453",
"text": "api.devrev.ai / webhooks.update\\nUpdates the requested webhook.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nID for the webhook.\\naction \"activate\" or \"deactivate\" Optional\\nAllowed values: activate deactivate\\nThe action to update the webhook\\'s status.\\nevent_types object Optional\\nShow 3 properties\\nheaders object Optional\\nShow 3 properties\\nsecret string Optional\\nIf provided, updates the secret that\\'s used when verifying webhook events, which must be between 8 and",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-4206_KNOWLEDGE_NODE-4",
"text": "create a webhook to receive agent execution events:\\n\\nBashJavaScript\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl --location \\'https://api.devrev.ai/internal/webhooks.create\\' \\\\ |\\n| > | --header \\'Content-Type: application/json\\' \\\\ |\\n| > | --header \\'Authorization: Bearer <YOUR_API_TOKEN>\\' \\\\ |\\n| > | --data \\'{ |\\n| > | \"url\": \"https://your-application.com/webhook-endpoint\", |\\n| > | \"event_types\": [\"ai_agent_response\"], |\\n| > | \"headers\": [ |\\n| > | { |\\n| > | \"name\": \"x-api-key\", |\\n| >",
"title": "Agents async API | DevRev | Docs"
},
{
"id": "ART-1234_KNOWLEDGE_NODE-1",
"text": "by events rather than requests. While APIs are used to pull data from the system, webhooks are a mechanism for the system to push data to a pre-configured endpoint. Webhooks allow you to receive notifications based on events without having to explicitly make a request.\\n\\n\\xf0\\x9f\\x93\\x8c For more information about webhooks, refer to [Getting started with webhooks](/public/guides/webhooks).\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/api-reference/timeline-entries/update)[#### Create",
"title": "Event responses | DevRev | Docs"
},
{
"id": "ART-1823_KNOWLEDGE_NODE-433",
"text": "api.devrev.ai / webhooks.create\\nCreates a new webhook target.\\nRequest.\\n\\nThis endpoint expects an object.\\nurl string Required\\nThe URL of the webhook endpoint.\\nevent_types list of enums Optional\\nThe event types that the webhook endpoint will receive.\\nShow 49 enum values\\nheaders list of objects Optional\\nThe headers to include in every webhook invocation.\\nShow 2 properties\\nsecret string Optional\\nThe secret to use when verifying webhook events. If provided, the secret must be between 8",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1789_KNOWLEDGE_NODE-437",
"text": "object\\nShow 11 properties\\nAPI Reference webhooks Get Post.\\n\\nPOST https:// api.devrev.ai / webhooks.get\\nGets the requested webhook\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nID for the webhook.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhook object\\nShow 11 properties\\nAPI Reference webhooks List.\\n\\nGET https:// api.devrev.ai / webhooks.list\\nLists the webhooks.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\nThe",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1284_KNOWLEDGE_NODE-14",
"text": "`true`, the event is dispatched to the webhook. If the filter returns `false`, the event is not dispatched to the webhook.\\n\\nFor example, to create an event source which listens for issue creation and comments on issues, you can define the event source as follows:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | event_sources: |\\n| 2 | organization: |\\n| 3 | - name: devrev-webhook |\\n| 4 | description: Events coming from DevRev for issues |\\n| 5 | display_name: DevRev webhook |\\n| 6 | type:",
"title": "Event sources | DevRev | Docs"
},
{
"id": "ART-1803_KNOWLEDGE_NODE-438",
"text": "object\\nShow 11 properties\\nAPI Reference webhooks Get Post.\\n\\nPOST https:// api.devrev.ai / webhooks.get\\nGets the requested webhook\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nID for the webhook.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhook object\\nShow 11 properties\\nAPI Reference webhooks List.\\n\\nGET https:// api.devrev.ai / webhooks.list\\nLists the webhooks.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\nThe",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1292_KNOWLEDGE_NODE-0",
"text": "b'Development best practices | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\nOn this page\\n\\n* [Act on specific webhook conditions](/snapin-development/best-practices#act-on-specific-webhook-conditions)\\n* [Use the DevRev SDK](/snapin-development/best-practices#use-the-devrev-sdk)\\n* [Think from a snap-in installer perspective](/snapin-development/best-practices#think-from-a-snap-in-installer-perspective)\\n\\n[Snap-in",
"title": "Development best practices | DevRev | Docs"
},
{
"id": "ART-1551_KNOWLEDGE_NODE-494",
"text": "webhook.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhook object\\nShow 11 properties\\nAPI Reference webhooks List.\\n\\nGET https://api.devrev.ai / webhooks.list\\n\\nLists the webhooks.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\n\\nThe list of webhooks.\\n\\nShow 11 properties\\nAPI Reference webhooks List Post.\\n\\nPOST https://api.devrev.ai / webhooks.list\\n\\nLists the webhooks.\\n\\nRequest.\\n\\nThis endpoint expects a map from strings to",
"title": "Update (Beta) — DevRev | Docs"
},
{
"id": "ART-4063_KNOWLEDGE_NODE-12",
"text": "\"webhook_id\": \"don:integration:dvrv-us-1:devo/example:webhook/webhook-id\" \\n >| }\\'\\n[/code] \\n \\nTry it\\n\\n200webhooksEventExample\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"challenge\": \"foo\" \\n 3| }\\n[/code] \\n \\n[Get WebhookUp Next](/public/api-reference/webhooks/get)\\n\\n[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)\\n\\n[Enterprise grade security to protect customer dataLearn more about",
"title": "Event Webhooks — DevRev | Docs"
},
{
"id": "ART-1485_KNOWLEDGE_NODE-13",
"text": "is to incorporate the [event source](/public/snapin-development/references/event-sources). For this scenario, events from DevRev are essential. Therefore, an event source of type `devrev-webhook` is added. In the configuration, the event type is specified as `work_created`.\\n[code]\\n\\n 1| event_sources: \\n ---|--- \\n 2| organization: \\n 3| - name: devrev-webhook \\n 4| display_name: DevRev \\n 5| type: devrev-webhook \\n 6| config: \\n 7|",
"title": "Snap-in triggered by a DevRev event — DevRev | Docs"
},
{
"id": "ART-1650_KNOWLEDGE_NODE-434",
"text": "object\\nShow 11 properties\\nAPI Reference webhooks Get Post.\\n\\nPOST https:// api.devrev.ai / webhooks.get\\nGets the requested webhook\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nID for the webhook.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhook object\\nShow 11 properties\\nAPI Reference webhooks List.\\n\\nGET https:// api.devrev.ai / webhooks.list\\nLists the webhooks.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\nThe",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1836_KNOWLEDGE_NODE-437",
"text": "2023-01-01T12:00:00Z \" , 8 \" event_types \" : [ 9 \" account_created \" 10 ] , 11 \" headers \" : [ 12 { 13 \" name \" : \" name \" , 14 \" value \" : \" value \" 15 } 16 ] , 17 \" secret \" : \" secret \" , 18 \" status \" : \" active \" , 19 \" url \" : \" url \" 20 } 21 ] 22 }\\nAPI Reference webhooks List Post.\\n\\nPOST https:// api.devrev.ai / webhooks.list\\nLists the webhooks.\\nRequest.\\n\\nThis endpoint expects a map from strings to any.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\nThe",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1284_KNOWLEDGE_NODE-15",
"text": "devrev-webhook |\\n| 7 | config: |\\n| 8 | event_types: |\\n| 9 | - work_created |\\n| 10 | - timeline_entry_created |\\n| 11 | filter: |\\n| 12 | jq_query: | |\\n| 13 | if .type == \"work_created\" then |\\n| 14 | if (.work_created.work.type == \"issue\") then true |\\n| 15 | else false |\\n| 16 | end |\\n| 17 | elif .type == \"timeline_entry_created\" then |\\n| 18 | if (.timeline_entry_created.entry.type == \"timeline_comment\" and .timeline_entry_created.entry.object_type == \"issue\") then true |\\n| 19 | else",
"title": "Event sources | DevRev | Docs"
},
{
"id": "ART-15268_KNOWLEDGE_NODE-2",
"text": "Note the documented endpoint is for exposition and not\\nprovided by DevRev.\\n\\n### Headers\\n\\nAuthorizationstringRequired\\n\\nBearer authentication of the form `Bearer <token>`, where token is your auth token.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\nidstringRequired`format: \"id\"`\\n\\nThe event\\'s ID.\\n\\nwebhook\\\\_idstringRequired`format: \"id\"`\\n\\nID of the webhook for the event.\\n\\ntypeenumOptional\\n\\nThe event types that the webhook will receive.\\n\\nShow 73 enum",
"title": "Event Webhooks | DevRev | Docs"
},
{
"id": "ART-1835_KNOWLEDGE_NODE-434",
"text": ": \" 2023-01-01T12:00:00Z \" , 4 \" display_id \" : \" display_id \" , 5 \" id \" : \" id \" , 6 \" modified_date \" : \" 2023-01-01T12:00:00Z \" , 7 \" event_types \" : [ 8 \" account_created \" 9 ] , 10 \" headers \" : [ 11 { 12 \" name \" : \" name \" , 13 \" value \" : \" value \" 14 } 15 ] , 16 \" secret \" : \" secret \" , 17 \" status \" : \" active \" , 18 \" url \" : \" url \" 19 } 20 }\\nAPI Reference webhooks List.\\n\\nGET https:// api.devrev.ai / webhooks.list\\nLists the webhooks.\\nResponse.\\n\\nThis endpoint returns an",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1430_KNOWLEDGE_NODE-2",
"text": "Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nPOST\\n\\n/webhooks.create\\n\\n[code]\\n\\n $| curl -X POST https://api.devrev.ai/webhooks.create \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer <token>\" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"url\": \"foo\" \\n >| }\\'\\n[/code] \\n \\nTry it\\n\\n201webhooksCreateExample\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"webhook\": { \\n 3| \"id\": \"foo\",",
"title": "Create Webhook — DevRev | Docs"
},
{
"id": "ART-1564_KNOWLEDGE_NODE-494",
"text": "webhook.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhook object\\nShow 11 properties\\nAPI Reference webhooks List.\\n\\nGET https://api.devrev.ai / webhooks.list\\n\\nLists the webhooks.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\n\\nThe list of webhooks.\\n\\nShow 11 properties\\nAPI Reference webhooks List Post.\\n\\nPOST https://api.devrev.ai / webhooks.list\\n\\nLists the webhooks.\\n\\nRequest.\\n\\nThis endpoint expects a map from strings to",
"title": "List (Beta) — DevRev | Docs"
},
{
"id": "ART-1549_KNOWLEDGE_NODE-494",
"text": "webhook.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhook object\\nShow 11 properties\\nAPI Reference webhooks List.\\n\\nGET https://api.devrev.ai / webhooks.list\\n\\nLists the webhooks.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\n\\nThe list of webhooks.\\n\\nShow 11 properties\\nAPI Reference webhooks List Post.\\n\\nPOST https://api.devrev.ai / webhooks.list\\n\\nLists the webhooks.\\n\\nRequest.\\n\\nThis endpoint expects a map from strings to",
"title": "List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1835_KNOWLEDGE_NODE-435",
"text": "object.\\nwebhooks list of objects\\nThe list of webhooks.\\nShow 11 properties\\nGET / webhooks.list\\n$ curl https://api.devrev.ai/webhooks.list \\\\ > -H \" Authorization: Bearer <token> \"\\n200 Retrieved 1 { 2 \" webhooks \" : [ 3 { 4 \" created_date \" : \" 2023-01-01T12:00:00Z \" , 5 \" display_id \" : \" display_id \" , 6 \" id \" : \" id \" , 7 \" modified_date \" : \" 2023-01-01T12:00:00Z \" , 8 \" event_types \" : [ 9 \" account_created \" 10 ] , 11 \" headers \" : [ 12 { 13 \" name \" : \" name \" , 14 \" value \" : \"",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1649_KNOWLEDGE_NODE-445",
"text": "list of webhooks.\\nShow 11 properties\\nAPI Reference webhooks Update.\\n\\nPOST https:// api.devrev.ai / webhooks.update\\nUpdates the requested webhook.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nID for the webhook.\\naction \"activate\" or \"deactivate\" Optional\\nAllowed values: activate deactivate\\nThe action to update the webhook\\'s status.\\nevent_types object Optional\\nShow 3 properties\\nheaders object Optional\\nShow 3 properties\\nsecret string Optional\\nIf provided,",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1650_KNOWLEDGE_NODE-435",
"text": "list of webhooks.\\nShow 11 properties\\nAPI Reference webhooks List Post.\\n\\nPOST https:// api.devrev.ai / webhooks.list\\nLists the webhooks.\\nRequest.\\n\\nThis endpoint expects a map from strings to any.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\nThe list of webhooks.\\nShow 11 properties\\nAPI Reference webhooks Update.\\n\\nPOST https:// api.devrev.ai / webhooks.update\\nUpdates the requested webhook.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1277_KNOWLEDGE_NODE-9",
"text": "event source\\nof type `devrev-webhook` is added. In the configuration, the event type is\\nspecified as `work_created`.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | event_sources: |\\n| 2 | organization: |\\n| 3 | - name: devrev-webhook |\\n| 4 | display_name: DevRev |\\n| 5 | type: devrev-webhook |\\n| 6 | config: |\\n| 7 | event_types: |\\n| 8 | - work_created |\\n```\\n\\n[4](/snapin-development/tutorials/triggered-event#input-fields)\\n\\n### Input fields\\n\\nTo enable users to configure specific comments,",
"title": "Snap-in triggered by a DevRev event | DevRev | Docs"
},
{
"id": "ART-1836_KNOWLEDGE_NODE-438",
"text": "list of webhooks.\\nShow 11 properties\\nAPI Reference webhooks Update.\\n\\nPOST https:// api.devrev.ai / webhooks.update\\nUpdates the requested webhook.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nID for the webhook.\\naction \"activate\" or \"deactivate\" Optional\\nAllowed values: activate deactivate\\nThe action to update the webhook\\'s status.\\nevent_types object Optional\\nShow 3 properties\\nheaders object Optional\\nShow 3 properties\\nsecret string Optional\\nIf provided,",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1590_KNOWLEDGE_NODE-439",
"text": "list of webhooks.\\nShow 11 properties\\nAPI Reference webhooks List Post.\\n\\nPOST https:// api.devrev.ai / webhooks.list\\nLists the webhooks.\\nRequest.\\n\\nThis endpoint expects a map from strings to any.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\nThe list of webhooks.\\nShow 11 properties\\nAPI Reference webhooks Update.\\n\\nPOST https:// api.devrev.ai / webhooks.update\\nUpdates the requested webhook.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1478_KNOWLEDGE_NODE-21",
"text": "\\n 9| description: Event coming from DevRev \\n 10| display_name: DevRev \\n 11| type: devrev-webhook \\n 12| config: \\n 13| event_types: \\n 14| - work_created \\n 15| - name: scheduled-events \\n 16| description: Events scheduled from snap-ins \\n 17| display_name: scheduled-events \\n 18| type: flow-events \\n 19| \\n 20| functions: \\n 21| - name: function_1 \\n 22| description:",
"title": "Event sources — DevRev | Docs"
},
{
"id": "ART-1547_KNOWLEDGE_NODE-495",
"text": "webhook.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhook object\\nShow 11 properties\\nAPI Reference webhooks List.\\n\\nGET https://api.devrev.ai / webhooks.list\\n\\nLists the webhooks.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\n\\nThe list of webhooks.\\n\\nShow 11 properties\\nAPI Reference webhooks List Post.\\n\\nPOST https://api.devrev.ai / webhooks.list\\n\\nLists the webhooks.\\n\\nRequest.\\n\\nThis endpoint expects a map from strings to",
"title": "Get Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1837_KNOWLEDGE_NODE-435",
"text": "\" display_id \" , 6 \" id \" : \" id \" , 7 \" modified_date \" : \" 2023-01-01T12:00:00Z \" , 8 \" event_types \" : [ 9 \" account_created \" 10 ] , 11 \" headers \" : [ 12 { 13 \" name \" : \" name \" , 14 \" value \" : \" value \" 15 } 16 ] , 17 \" secret \" : \" secret \" , 18 \" status \" : \" active \" , 19 \" url \" : \" url \" 20 } 21 ] 22 }\\nAPI Reference webhooks Update.\\n\\nPOST https:// api.devrev.ai / webhooks.update\\nUpdates the requested webhook.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nID",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1830_KNOWLEDGE_NODE-450",
"text": "api.devrev.ai / webhooks.fetch\\nFetches an object via webhook.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the webhook to fetch the object for.\\nobject string Required\\nThe ID of the object to fetch for the webhook.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference webhooks Get.\\n\\nGET https:// api.devrev.ai / webhooks.get\\nGets the requested webhook\\'s information.\\nQuery parameters.\\n\\nid string Required\\nID for the",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1300_KNOWLEDGE_NODE-438",
"text": "list of webhooks.\\nShow 11 properties\\nAPI Reference webhooks List Post.\\n\\nPOST https:// api.devrev.ai / webhooks.list\\nLists the webhooks.\\nRequest.\\n\\nThis endpoint expects a map from strings to any.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\nThe list of webhooks.\\nShow 11 properties\\nAPI Reference webhooks Update.\\n\\nPOST https:// api.devrev.ai / webhooks.update\\nUpdates the requested webhook.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1282_KNOWLEDGE_NODE-11",
"text": "DevRev webhook |\\n| 5 | type: devrev-webhook |\\n| 6 | config: |\\n| 7 | event_types: |\\n| 8 | - work_created |\\n```\\n\\nGlobals\\n-------\\n\\nGlobals are implemented today using per-object schemas, which is a customization term to store custom schemas in line with the object. Each global\\xe2\\x80\\x99s schema maps to a FieldDescriptor.\\n\\nThe definition of globals looks like this:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | globals: |\\n| 2 | - name: <name of the global> |\\n| 3 | description: <its",
"title": "Snap-in V1 manifest | DevRev | Docs"
},
{
"id": "ART-1264_KNOWLEDGE_NODE-14",
"text": "the Create Request:\\n\\n### Verify request `[json]`\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | POST your-webhook-endpoint-url |\\n| 2 | X-DevRev-Signature: GfxZ8e4k8agCdWQyTr2z1BY0e8JYzEAn |\\n| 3 | { |\\n| 4 | \"id\": \"don:integration:dvrv-us-1:devo/1H79gci4u:webhook/123:event/abcdef\", |\\n| 5 | \"webhook_id\": \"don:integration:dvrv-us-1:devo/1H79gci4u:webhook/123\", |\\n| 6 | \"timestamp\": \"2022-08-01T12:00:00.123456789Z\", |\\n| 7 | \"type\": \"verify\", |\\n| 8 | \"verify\": { |\\n| 9 | \"challenge\":",
"title": "Webhooks | DevRev | Docs"
},
{
"id": "ART-1485_KNOWLEDGE_NODE-7",
"text": "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",
"title": "Snap-in triggered by a DevRev event — DevRev | Docs"
},
{
"id": "ART-1789_KNOWLEDGE_NODE-438",
"text": "list of webhooks.\\nShow 11 properties\\nAPI Reference webhooks List Post.\\n\\nPOST https:// api.devrev.ai / webhooks.list\\nLists the webhooks.\\nRequest.\\n\\nThis endpoint expects a map from strings to any.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\nThe list of webhooks.\\nShow 11 properties\\nAPI Reference webhooks Update.\\n\\nPOST https:// api.devrev.ai / webhooks.update\\nUpdates the requested webhook.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1549_KNOWLEDGE_NODE-490",
"text": "object.\\ntimeline_entry object\\nShow 2 variants\\nAPI Reference webhooks Create.\\n\\nPOST https://api.devrev.ai / webhooks.create\\n\\nCreates a new webhook target.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nurl string Required\\n\\nThe URL of the webhook endpoint.\\n\\nevent_types list of enums Optional\\n\\nThe event types that the webhook endpoint will receive.\\n\\nShow 49 enum values\\nheaders list of objects Optional\\n\\nThe headers to include in every webhook invocation.\\n\\nShow 2",
"title": "List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1459_KNOWLEDGE_NODE-15",
"text": "provided challenge within 3 mins of the Create Request:\\n\\n### Verify request `[json]`\\n\\n[code]\\n\\n 1| POST your-webhook-endpoint-url \\n ---|--- \\n 2| X-DevRev-Signature: GfxZ8e4k8agCdWQyTr2z1BY0e8JYzEAn \\n 3| { \\n 4| \"id\": \"don:integration:dvrv-us-1:devo/1H79gci4u:webhook/123:event/abcdef\", \\n 5| \"webhook_id\": \"don:integration:dvrv-us-1:devo/1H79gci4u:webhook/123\", \\n 6| \"timestamp\": \"2022-08-01T12:00:00.123456789Z\", \\n 7| \"type\": \"verify\", \\n 8|",
"title": "Webhooks — DevRev | Docs"
},
{
"id": "ART-1591_KNOWLEDGE_NODE-440",
"text": "list of webhooks.\\nShow 11 properties\\nAPI Reference webhooks List Post.\\n\\nPOST https:// api.devrev.ai / webhooks.list\\nLists the webhooks.\\nRequest.\\n\\nThis endpoint expects a map from strings to any.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\nThe list of webhooks.\\nShow 11 properties\\nAPI Reference webhooks Update.\\n\\nPOST https:// api.devrev.ai / webhooks.update\\nUpdates the requested webhook.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1264_KNOWLEDGE_NODE-9",
"text": "event notifications using the following steps:\\n\\n1. Set up a secure HTTP server and expose a publicly accessible endpoint, which serves as the webhook invocation target.\\n Insert your endpoint where the following is mentioned: `your-webhook-endpoint-url`.\\n2. Identify the events you want to monitor and the event payloads to parse.\\n Look up the supported events and event payloads in our API Methods section.\\n A general guideline here is to only subscribe to event types which you require",
"title": "Webhooks | DevRev | Docs"
},
{
"id": "ART-1547_KNOWLEDGE_NODE-491",
"text": "object.\\ntimeline_entry object\\nShow 2 variants\\nAPI Reference webhooks Create.\\n\\nPOST https://api.devrev.ai / webhooks.create\\n\\nCreates a new webhook target.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nurl string Required\\n\\nThe URL of the webhook endpoint.\\n\\nevent_types list of enums Optional\\n\\nThe event types that the webhook endpoint will receive.\\n\\nShow 49 enum values\\nheaders list of objects Optional\\n\\nThe headers to include in every webhook invocation.\\n\\nShow 2",
"title": "Get Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1564_KNOWLEDGE_NODE-490",
"text": "object.\\ntimeline_entry object\\nShow 2 variants\\nAPI Reference webhooks Create.\\n\\nPOST https://api.devrev.ai / webhooks.create\\n\\nCreates a new webhook target.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nurl string Required\\n\\nThe URL of the webhook endpoint.\\n\\nevent_types list of enums Optional\\n\\nThe event types that the webhook endpoint will receive.\\n\\nShow 49 enum values\\nheaders list of objects Optional\\n\\nThe headers to include in every webhook invocation.\\n\\nShow 2",
"title": "List (Beta) — DevRev | Docs"
},
{
"id": "ART-1485_KNOWLEDGE_NODE-5",
"text": "[Resources](/public/snapin-development/tutorials/triggered-event#resources)\\n\\n[Snap-in development](/public/snapin-development/concepts)[Tutorials](/public/snapin-development/tutorials/overview)\\n\\n#\\n\\nSnap-in triggered by a DevRev event\\n\\n## Introduction\\n\\nIn this tutorial, you\\xe2\\x80\\x99ll learn to create a dynamic snap-in that responds to both DevRev Webhook events triggered by the creation of a [work](https://docs.devrev.ai/product/core) and specialized",
"title": "Snap-in triggered by a DevRev event — DevRev | Docs"
},
{
"id": "ART-1543_KNOWLEDGE_NODE-489",
"text": "object.\\ntimeline_entry object\\nShow 2 variants\\nAPI Reference webhooks Create.\\n\\nPOST https://api.devrev.ai / webhooks.create\\n\\nCreates a new webhook target.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nurl string Required\\n\\nThe URL of the webhook endpoint.\\n\\nevent_types list of enums Optional\\n\\nThe event types that the webhook endpoint will receive.\\n\\nShow 49 enum values\\nheaders list of objects Optional\\n\\nThe headers to include in every webhook invocation.\\n\\nShow 2",
"title": "Metric Definitions List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-4063_KNOWLEDGE_NODE-9",
"text": "\"date-time\"`\\n\\nTimestamp of the webhook\\xe2\\x80\\x99s invocation for the event. Note this should be used to protect against replay attacks, where the event should only be processed if the timestamp isn\\xe2\\x80\\x99t stale by several seconds.\\n\\nverifyobjectOptional\\n\\nShow property\\n\\nwebhook_createdobjectOptional\\n\\nShow property\\n\\nwebhook_deletedobjectOptional\\n\\nShow property\\n\\nwebhook_updatedobjectOptional\\n\\nShow property\\n\\nwidget_createdobjectOptional\\n\\nShow",
"title": "Event Webhooks — DevRev | Docs"
},
{
"id": "ART-1551_KNOWLEDGE_NODE-490",
"text": "object.\\ntimeline_entry object\\nShow 2 variants\\nAPI Reference webhooks Create.\\n\\nPOST https://api.devrev.ai / webhooks.create\\n\\nCreates a new webhook target.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nurl string Required\\n\\nThe URL of the webhook endpoint.\\n\\nevent_types list of enums Optional\\n\\nThe event types that the webhook endpoint will receive.\\n\\nShow 49 enum values\\nheaders list of objects Optional\\n\\nThe headers to include in every webhook invocation.\\n\\nShow 2",
"title": "Update (Beta) — DevRev | Docs"
},
{
"id": "ART-1558_KNOWLEDGE_NODE-493",
"text": "returns an object.\\nwebhooks list of objects\\n\\nThe list of webhooks.\\n\\nShow 11 properties\\nAPI Reference webhooks List Post.\\n\\nPOST https://api.devrev.ai / webhooks.list\\n\\nLists the webhooks.\\n\\nRequest.\\n\\nThis endpoint expects a map from strings to any.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\n\\nThe list of webhooks.\\n\\nShow 11 properties\\nAPI Reference webhooks Update.\\n\\nPOST https://api.devrev.ai / webhooks.update\\n\\nUpdates the requested",
"title": "Metric Definitions List (Beta) — DevRev | Docs"
},
{
"id": "ART-4063_KNOWLEDGE_NODE-2",
"text": "documented endpoint is for exposition and not provided by DevRev.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\nidstringRequired`format: \"id\"`\\n\\nThe event\\xe2\\x80\\x99s ID.\\n\\nwebhook_idstringRequired`format: \"id\"`\\n\\nID of the webhook for the event.\\n\\ntypeenumOptional\\n\\nThe event types that the webhook will receive.\\n\\nShow 70 enum values\\n\\naccount_createdobjectOptional\\n\\nShow property\\n\\naccount_deletedobjectOptional\\n\\nShow 2 properties\\n\\naccount_updatedobjectOptional\\n\\nShow 2",
"title": "Event Webhooks — DevRev | Docs"
},
{
"id": "ART-1828_KNOWLEDGE_NODE-436",
"text": "api.devrev.ai / webhooks.list\\nLists the webhooks.\\nRequest.\\n\\nThis endpoint expects a map from strings to any.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\nThe list of webhooks.\\nShow 11 properties\\nAPI Reference webhooks Update.\\n\\nPOST https:// api.devrev.ai / webhooks.update\\nUpdates the requested webhook.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nID for the webhook.\\naction \"activate\" or \"deactivate\" Optional\\nAllowed values: activate",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1818_KNOWLEDGE_NODE-439",
"text": "list of webhooks.\\nShow 11 properties\\nAPI Reference webhooks List Post.\\n\\nPOST https:// api.devrev.ai / webhooks.list\\nLists the webhooks.\\nRequest.\\n\\nThis endpoint expects a map from strings to any.\\nResponse.\\n\\nThis endpoint returns an object.\\nwebhooks list of objects\\nThe list of webhooks.\\nShow 11 properties\\nAPI Reference webhooks Update.\\n\\nPOST https:// api.devrev.ai / webhooks.update\\nUpdates the requested webhook.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string",
"title": "Sla Trackers Get Post — DevRev | Docs"
}
] |
04bea083-cdf2-48b4-a8c7-3fabf538626a
|
set multiple SLA policies as default for different types of tickets
|
[
{
"id": "ART-1986_KNOWLEDGE_NODE-27",
"text": "the **Create SLA** window, provide a name and description of the SLA.\\n\\n After creating the SLA, assign policies to it.\\n\\nCreating policies within SLA\\n----------------------------\\n\\nMultiple policies can be created within an SLA. Each policy has a priority order, so if a ticket meets the conditions of two or more policies, the policy with the highest priority is applied.\\n\\nTo create a policy within an SLA, do the following:\\n\\n1. Click **+ Policy**.\\n2. Select either *Ticket Policy* or",
"title": "Service-level agreement | Computer for Support Teams | DevRev"
},
{
"id": "ART-1986_KNOWLEDGE_NODE-28",
"text": "*Conversation Policy*.\\n3. In the **New ticket policy** pane, under **Conditions**, select the ticket attributes values of **Tag**, **Part**, and **Severity**.\\n4. Under **Metrics**, enable or disable **First response**, **Next response**, and **Resolution time**.\\n5. Click **Publish**.\\n\\n![]()\\n\\nSLA metrics are only applied to tickets or conversations that meet the policy's conditions.\\n\\nPublishing an SLA\\n-----------------\\n\\nSLAs can be published once all policies are created. Published",
"title": "Service-level agreement | Computer for Support Teams | DevRev"
},
{
"id": "ART-4181_KNOWLEDGE_NODE-12",
"text": "criteria, ensuring the right SLAs are consistently applied to relevant old and new customers\\n\\n![]()\\n\\nFlexible Exceptions\\n\\nCreate Exceptions for customers who require special treatment, overriding the Assignment Rules when necessary\\n\\n![]()\\n\\nDefault SLA Fallback\\n\\nAuto-assign a Default SLA to customers who do not meet any of the specified criteria\\n\\nAutomated SLA Assignment\\n\\nAuto-assign SLA based on predefined criteria, ensuring the right SLAs are consistently applied to relevant",
"title": "Support like a lightning fast pit-crew"
},
{
"id": "ART-4181_KNOWLEDGE_NODE-11",
"text": "Assignment\\n\\nAuto-assign SLA based on predefined criteria, ensuring the right SLAs are consistently applied to relevant old and new customers\\n\\nFlexible Exceptions\\n\\nCreate Exceptions for customers who require special treatment, overriding the Assignment Rules when necessary\\n\\nDefault SLA Fallback\\n\\nAuto-assign a Default SLA to customers who do not meet any of the specified criteria\\n\\n![]()\\n\\n![]()\\n\\n![]()\\n\\n![]()\\n\\nAutomated SLA Assignment\\n\\nAuto-assign SLA based on predefined",
"title": "Support like a lightning fast pit-crew"
},
{
"id": "ART-4181_KNOWLEDGE_NODE-13",
"text": "old and new customers\\n\\nFlexible Exceptions\\n\\nCreate Exceptions for customers who require special treatment, overriding the Assignment Rules when necessary\\n\\nDefault SLA Fallback\\n\\nAuto-assign a Default SLA to customers who do not meet any of the specified criteria\\n\\n![]()\\n\\n![]()\\n\\n![]()\\n\\n![]()\\n\\nAutomated SLA Assignment\\n\\nAuto-assign SLA based on predefined criteria, ensuring the right SLAs are consistently applied to relevant old and new customers\\n\\n![]()\\n\\nFlexible",
"title": "Support like a lightning fast pit-crew"
},
{
"id": "ART-4181_KNOWLEDGE_NODE-6",
"text": "time and resolution time, or tailor metrics to your requirements\\n\\n![]()\\n\\nTrigger SLAs at the right moment, every time\\n\\nMap conditions to parts of your product, tags, severity levels, or any other relevant criteria on our simple UI\\n\\n![]()\\n\\nTrigger SLAs at the right moment, every time\\n\\nMap conditions to parts of your product, tags, severity levels, or any other relevant criteria on our simple UI\\n\\n![]()\\n\\nSLAs in sync with your business\\n\\nAccount for calendar and business hours,",
"title": "Support like a lightning fast pit-crew"
},
{
"id": "ART-2695_KNOWLEDGE_NODE-28",
"text": "conditions in more than one policy.\\n\\nPublish an OLA\\n--------------\\n\\nAfter creating the necessary policies, click **Publish** to activate the OLA.\\n\\n![]()\\n\\nOnce an OLA is published, it cannot be edited, nor can you modify the policies or their priority order.\\n\\nOnly one OLA can be in the *Published* state at any time. If there is an existing published OLA, it is archived when you publish a new one. Any new issues will follow the guidelines of the newly-published OLA, while issues",
"title": "Operational-level agreement | Computer for Support Teams | DevRev"
}
] |
390c548c-e125-40c5-8427-11e4de46b0cc
|
tickets not getting assigned automatically from unassigned bucket
|
[
{
"id": "ART-1976_KNOWLEDGE_NODE-25",
"text": "and effective resolution. Users can design workflows tailored to various scenarios; the example below illustrates a basic routing use case.\\n\\n| NODE | ACTIVITY |\\n| --- | --- |\\n| Trigger | Ticket created |\\n| Action | Pick user by group |\\n| Action | Update ticket |\\n| | ID: Ticket created > Output > ID |\\n| | Group > Output > ID |\\n| | Owned by > Set: Pick user > Output > User |\\n\\nOrgs can set up pull-based routing by updating the group instead of the user ID in the workflow illustrated",
"title": "Routing | Computer for Support Teams | DevRev"
},
{
"id": "ART-1986_KNOWLEDGE_NODE-32",
"text": "accounts without an existing SLA. This means that the assignment rules or exceptions for the default SLA are bypassed.\\n\\n**Dedicated assignment rules**\\n\\nThis section within the SLA part lets you view the list of assignment rules created for all published SLAs. You can create/edit/delete assignment rules for any published SLA from this space and view the priority order for the application of assignment rules (to refer to when multiple SLAs are valid for the same account).\\n\\nSLA metric",
"title": "Service-level agreement | Computer for Support Teams | DevRev"
}
] |
5985d184-b237-423a-89e5-74d07c195fad
|
how to find my tickets in DevRev
|
[
{
"id": "ART-1979_KNOWLEDGE_NODE-27",
"text": "also be used to engage customers for feedback/ideas (such as new feature ideas). Scoping is important for broadcast tickets as there needs to be a differentiation between broadcast (all revs) vs. multicast (particular revs).\\n\\nViews of tickets can be found under **Support** in the DevRev app.\\n\\n![]()\\n\\nYou can export views to CSV or JSON by selecting **Actions** in the upper-right corner and choosing the format.\\n\\nAttributes\\n----------\\n\\nTickets have attributes that can be used to filter",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-1979_KNOWLEDGE_NODE-37",
"text": "filters and **Group** conditions across various vistas in DevRev to track specific work, capacity, and more.\\n\\nYou can add custom attributes to tickets to track additional information. For more information on custom attributes, see [object customization](./object-customization).\\n\\nIssues are attached to tickets in order to track efforts with product priorities.\\n\\nCreate a ticket\\n---------------\\n\\n1. Go to **Support** > **Tickets** from the sidebar on the left.\\n2. Click **New Ticket** on",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-3207_KNOWLEDGE_NODE-47",
"text": "**Primary Use Case** is **Tickets**, go to **Support** > **Tickets** in the DevRev app; otherwise, if the **Primary Use Case** is **Conversation** go to **Inbox**. Find and open your verification message here.\\n6. Open the given link to confirm the request. Make sure you click the link that allows your support address to be forwarded to v\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\[email protected].\\n7. Go back to your Gmail forwarding settings, select **Forward a copy of incoming mail** and **Save",
"title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-1954_KNOWLEDGE_NODE-25",
"text": "DevRev](/docs/intro)\\n[Updates](/docs/product/updates)\\n\\nUpdates\\n=======\\n\\nUpdates help you stay on top of all your activity on DevRev.\\n\\nConversations, tickets, and issues where you are an owner, member, or creator, or where comments are made or you are @mentioned, are automatically shown in your updates. A group can also be mentioned here which will send a notification to all the members of the group. For other tickets and issues, you can follow them to receive some or all updates through",
"title": "Updates | Computer by DevRev | DevRev"
},
{
"id": "ART-1978_KNOWLEDGE_NODE-32",
"text": "on the following URL: support.devrev.ai/<yourcompany>.\\n* Your customers can log in on the portal by entering their registered email address and OTP sent to that email address.\\n\\n![]()\\n\\n### Customer roles and permissions\\n\\nThe customer portal has two levels of customer roles and permissions:\\n\\n* **Verified customers**: Customers who can log in on the portal and see the tickets that they have created.\\n* **Customer admins**: Customers who can log in on the portal and see not just their own",
"title": "Customer portal | Computer for Support Teams | DevRev"
},
{
"id": "ART-4271_KNOWLEDGE_NODE-28",
"text": "PLuG widget:\\n\\n * The ticket number and basic details appear in the same conversation pane.\\n * Users can click **Details** to view complete ticket information.\\n * If the **Tickets** tab is enabled in PLuG, users can track their ticket status there.\\n\\n### Slack experience\\n\\nWhen a conversation is converted to a ticket in Slack:\\n\\n * Ticket information is sent within the same thread.\\n * All subsequent messages sync with the newly created ticket.\\n * The transition is seamless for the",
"title": "Convert Conversations to Tickets | Conversations | Support | DevRev"
}
] |
cddb0614-bcc7-4b89-b504-8ac7b91020fd
|
duplicate CSAT ratings on the same ticket
|
[
{
"id": "ART-1979_KNOWLEDGE_NODE-59",
"text": "duplicate tickets transfer to the primary ticket.\\n* The older messages and attachments on the duplicate ticket remains within the duplicate ticket post merge.\\n* Any new customer message on duplicate tickets post merge sync to the primary ticket.\\n* Duplicate tickets remain accessible through the **Linked Objects** section of the primary ticket.\\n* CSAT triggers only for the primary ticket resolution.\\n* Merge actions cannot be reversed, and merged tickets cannot be merged again.\\n\\nFollow up",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-2011_KNOWLEDGE_NODE-28",
"text": "only once per ticket** toggle.\\n10. If you want to automatically send CSAT surveys when tickets reach the *Resolved* stage, keep the **Trigger the CSAT survey based on configured rules** toggle turned off.\\n11. If you want to send CSAT at a specific ticket stage, turn the **Trigger the CSAT survey based on configured rules** toggle on and set up a custom workflow with the following configuration:\\n\\n| **Component** | **Details** |\\n| --- | --- |\\n| Trigger | Update Ticket |\\n| Stage Control |",
"title": "CSAT on ticket | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2011_KNOWLEDGE_NODE-27",
"text": "from the customer along with the scale rating, ensure that the toggle for **Additional Feedback Request** configuration is enabled.\\n6. Write a query for the customers after the survey is populated in **Survey query**.\\n7. Write a message for the customers after the survey response is submitted in **Survey response message**.\\n8. Specify the time for the survey to expire (in minutes) in **Survey expires after**.\\n\\n ![]()\\n9. If you want to send the survey only once, enable the **Send survey",
"title": "CSAT on ticket | Automate | Snap-ins | DevRev"
}
] |
804b6b70-ce94-4f03-b4e2-ccd7fecbe6f4
|
change home links pluG support
|
[
{
"id": "ART-1978_KNOWLEDGE_NODE-37",
"text": "portal\\n-----------------------------\\n\\nYou can customize the look of your support portal to match your branding goals.\\n\\n1. Go to **Settings** > **Plug & Portal** > **Portal Settings**.\\n2. Under **Configuration**, enter your site name and upload your company logo.\\n * (Optional) Enable the footer and add your social media and text links in their respective fields.\\n * (Optional) Enable **Search** to get answers in search results.\\n * (Optional) Enable Plug widget to facilitate",
"title": "Customer portal | Computer for Support Teams | DevRev"
},
{
"id": "ART-3109_KNOWLEDGE_NODE-29",
"text": "go to **Settings > Support > Plug Chat > Layout** through the settings icon on the top-left corner.\\n2. Select **Add a Card** and enter a title, description, image, and redirect URL.\\n3. Click **Save and Publish** in the top-right corner. The new card is visible in your Plug widget.\\n\\nWant to add more personalization to your Plug widget? Create your own. Visit [SDK Methods and Customization](https://developer.devrev.ai/sdks/web/customize) to create your own Plug from the ground",
"title": "Plug widget customization | Computer for Your Customers | DevRev"
},
{
"id": "ART-2059_KNOWLEDGE_NODE-5",
"text": "Jul 06 to Jul 19, 2023 Jun 20 to Jul 05, 2023 Jun 05 to Jun 19, 2023 May 22 to Jun 05, 2023 Apr 22 to May 22, 2023\\n\\nDeveloper DevRevU\\n\\nOn this page\\nIntegration code Unique app ID Setup for HTML Setup for React\\nInstall PLuG chat on your website.\\n\\nThere are two primary methods to customize PLuG chat. The easiest way is to do so through the app by navigating to Settings > Support > PLuG Settings > Configuration, Styling and Layout Tabs.. For detailed descriptions of the parameters, refer",
"title": "Install PLuG chat on your website"
},
{
"id": "ART-4256_KNOWLEDGE_NODE-12",
"text": "only.\\n\\nFor scenarios where custom handling is needed, links from the support chat can be captured with the following method:\\n\\n[code]\\n\\n 1| DevRev.setInAppLinkHandler((url) => { \\n ---|--- \\n 2| \\t// Perform an action here. \\n 3| });\\n[/code] \\n \\nIf a custom handler is not defined, all external and in-app links from the support chat will open using the system\\xe2\\x80\\x99s default browser, such as Chrome.\\n\\n## Analytics\\n\\n#####\\n\\nThis feature requires the SDK to be",
"title": "DevRev SDK for React Native — DevRev | Docs"
},
{
"id": "ART-15507_KNOWLEDGE_NODE-23",
"text": "certain cases, the links opened from the support chat are opened in the app instead of a browser. You can control whether the chat modal should be dismissed after the link is opened by calling the following method:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | DevRev.setShouldDismissModalsOnOpenLink(value: boolean) |\\n```\\n\\nSetting this flag to true applies the system\\xe2\\x80\\x99s default behavior for opening links, which includes dismissing any DevRev modal screens to facilitate handling your own",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-15507_KNOWLEDGE_NODE-24",
"text": "deep links.\\n\\n### In-app link callback\\n\\n##### \\n\\nThis feature is supported only on Android.\\n\\nFor scenarios where custom handling is needed, links from the support chat can be captured with the following method:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | DevRev.setInAppLinkHandler((url) => { |\\n| 2 | // Perform an action here. |\\n| 3 | }); |\\n```\\n\\nDynamic theme configuration\\n---------------------------\\n\\nThe DevRev SDK allows you to configure the theme dynamically based on the system",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-12456_KNOWLEDGE_NODE-12",
"text": "opening links, which includes dismissing any DevRev modal screens to facilitate handling your own deep links.\\n\\n### In-app link callback\\n\\n#####\\n\\nThis feature is for Android only.\\n\\nFor scenarios where custom handling is needed, links from the support chat can be captured with the following method:\\n\\n[code]\\n\\n 1| DevRevSDK.setInAppLinkHandler((url) => { \\n ---|--- \\n 2| \\t// Perform an action here. \\n 3| });\\n[/code] \\n \\n## Dynamic theme configuration (iOS only)\\n\\nThe",
"title": "Features — DevRev | Docs"
},
{
"id": "ART-15513_KNOWLEDGE_NODE-26",
"text": "|\\n```\\n\\nThe support button can be customized using default parameters, enabling you to tailor its appearance to your application\\xe2\\x80\\x99s design:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | android:src=\"@your_drawable_here\" |\\n| 2 | android:backgroundTint=\"@your_background_color\" |\\n```\\n\\nIn-app link handling\\n--------------------\\n\\nThe DevRev SDK provides a mechanism to handle links opened from within any screen that is part of the DevRev SDK.\\n\\nYou can fully customize the link handling",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-12456_KNOWLEDGE_NODE-11",
"text": "DevRev.createSupportConversation() \\n ---|---\\n[/code] \\n \\n### In-app link handling\\n\\nIn certain cases, the links opened from the support chat are opened in the app instead of a browser. You can control whether the chat modal should be dismissed after the link is opened by calling the following method:\\n\\n[code]\\n\\n 1| DevRev.setShouldDismissModalsOnOpenLink(value: boolean) \\n ---|---\\n[/code] \\n \\nSetting this flag to true applies the system\\xe2\\x80\\x99s default behavior for",
"title": "Features — DevRev | Docs"
},
{
"id": "ART-2982_KNOWLEDGE_NODE-11",
"text": "support chat screen and simultaneously creates a new conversation.\\n\\n[code]\\n\\n 1| DevRev.createSupportConversation() \\n ---|---\\n[/code] \\n \\n### In-app link handling\\n\\nIn some instances, links opened from the support chat are displayed within the app rather than in a browser. You can manage whether the chat modal should close after a link is opened by using the following method:\\n\\n[code]\\n\\n 1| DevRev.setShouldDismissModalsOnOpenLink(value: boolean) \\n ---|---\\n[/code] \\n",
"title": "React Native integration — DevRev | Docs"
},
{
"id": "ART-2982_KNOWLEDGE_NODE-12",
"text": "\\nSetting this flag to `true` applies the system\\xe2\\x80\\x99s default behavior for opening links, which includes dismissing any DevRev modal screens to facilitate handling your own deep links.\\n\\n### In-app link callback\\n\\n#####\\n\\nThis functionality is for Android only.\\n\\nFor scenarios where custom handling is needed, links from the support chat can be captured with the following method:\\n\\n[code]\\n\\n 1| DevRevSDK.setInAppLinkHandler((url) => { \\n ---|--- \\n 2| \\t// Perform an",
"title": "React Native integration — DevRev | Docs"
},
{
"id": "ART-12460_KNOWLEDGE_NODE-12",
"text": "1| DevRev.createSupportConversation(isAnimated, successCallback, errorCallback) \\n ---|---\\n[/code] \\n \\n## In-app link handling\\n\\nThe DevRev SDK provides a mechanism to handle links opened from within any screen that is part of the DevRev SDK.\\n\\nYou can fully customize the link handling behavior by setting the specialized in-app link handler. That way you can decide what should happen when a link is opened from within the app.\\n\\n[code]\\n\\n 1| DevRev.setInAppLinkHandler(handler,",
"title": "Features — DevRev | Docs"
}
] |
2b0ce252-ee87-4fee-824f-588db340cb8c
|
save current view option when modifying a view
|
[
{
"id": "ART-16615_KNOWLEDGE_NODE-30",
"text": "**Hide columns**: Click on 3 dots next to a column to hide it from the view to reduce clutter\\n7. **Save preferences**: For any change in view preference settings like filter, sort, column, row selection click Save on top to save it as a new view or update the existing view\\n\\nBest practices\\n--------------\\n\\n* **Optimal Setup**: Use Stage or Status as your primary column grouping since these represent natural workflow progression. Reserve swimlanes for secondary attributes like Owner,",
"title": "Board view | Vistas | Computer by DevRev | DevRev"
},
{
"id": "ART-1949_KNOWLEDGE_NODE-25",
"text": "**Tickets**; **Build > Issues** and **Now, Next, Later**; and **Product > Parts**. Depending on the type of object there are different options for querying, sorting, customizing, and grouping.\\n\\n\\xf0\\x9f\\x8e\\xa5 Video: Applying filters to Vistas\\n\\nCreate a vista\\n--------------\\n\\n1. Select the object you want to make a list of, for example, tickets.\\n2. Make a change to the default view of the object by applying a filter, sorting, grouping, or customizing. A **Save as** button appears in the",
"title": "Vistas | Computer by DevRev | DevRev"
},
{
"id": "ART-1996_KNOWLEDGE_NODE-26",
"text": "developed and bring it to **Next**.\\n* Group the enhancements by **Created by**, **Stage**, and, **Type** or by adding any filter and save your roadmap by clicking **Save as** on the top right corner.\\n* Customize the view of the roadmap by going to **Customize** and selecting the filters you want to add to your roadmap.\\n\\n![]()\\n\\nGantt view\\n----------\\n\\n* Visualize the timeline by replacing the traditional list view with the dynamic Gantt view for a comprehensive perspective of",
"title": "Roadmap | Computer for Builders | DevRev"
},
{
"id": "ART-1949_KNOWLEDGE_NODE-26",
"text": "upper-right corner after you make a change.\\n You can toggle on **Show groups** in **Group by** dropdown to open up a side panel showing the groups.\\n\\n![]()\\n\\n![]()\\n\\nYou can also apply **Actions** > **Smart Clustering** if the number of tickets or issues is under 10,000. Clustering isn't available for conversations.\\n\\n1. Click **Save as**. You can give the list a name, and description and save it which causes it to show up in the **My list** section at the bottom of the left-side nav",
"title": "Vistas | Computer by DevRev | DevRev"
},
{
"id": "ART-1996_KNOWLEDGE_NODE-28",
"text": "these insights.\\n* Optimize resource allocation by analyzing the scope of enhancements; reallocate resources based on completed tasks and optimize future planning.\\n* Plan unplanned enhancements by adding target dates directly within the Gantt view.\\n* Switch between multiple views (day, month, and year) for a granular or broad overview of your roadmap.\\n* Create custom roadmaps by changing filters to focus on specific aspects of your roadmap. Save your customized views by clicking **Save as**",
"title": "Roadmap | Computer for Builders | DevRev"
}
] |
cbedeeda-be56-496d-873e-37503e8a7609
|
access customer portal for tickets
|
[
{
"id": "ART-1978_KNOWLEDGE_NODE-32",
"text": "on the following URL: support.devrev.ai/<yourcompany>.\\n* Your customers can log in on the portal by entering their registered email address and OTP sent to that email address.\\n\\n![]()\\n\\n### Customer roles and permissions\\n\\nThe customer portal has two levels of customer roles and permissions:\\n\\n* **Verified customers**: Customers who can log in on the portal and see the tickets that they have created.\\n* **Customer admins**: Customers who can log in on the portal and see not just their own",
"title": "Customer portal | Computer for Support Teams | DevRev"
},
{
"id": "ART-1978_KNOWLEDGE_NODE-33",
"text": "tickets but also all the tickets raised by the other users from their organization. You can add multiple customer admins from the same customer organization.\\n\\nOnly verified users can login into the portal.\\n\\nTo create a verified user:\\n\\n1. Go to **Accounts** in the DevRev app and create an account.\\n2. Create a contact under **Contacts** and link it to the account.\\n\\n### Set up customer admins\\n\\nTo set up customer admins, follow these steps:\\n\\n1. Log in on your DevRev app with your",
"title": "Customer portal | Computer for Support Teams | DevRev"
},
{
"id": "ART-1978_KNOWLEDGE_NODE-34",
"text": "registered email address and go to **Settings** > **User management** > **Groups > Customer Admins**.\\n2. Select the **Add User** option in the top-right corner to search for the customer whom you want to designate as a customer admin.\\n\\n### Customer portal login methods\\n\\nThe customer portal supports three login methods:\\n\\n1. Email OTP (One-Time Password): User enters their email, receives a one-time code, and enters it to log in.\\n2. SSO: Users log in through organization\\xe2\\x80\\x99s",
"title": "Customer portal | Computer for Support Teams | DevRev"
},
{
"id": "ART-1978_KNOWLEDGE_NODE-41",
"text": "If no such contact is found, JIT provisioning automatically creates a user account, allowing immediate access to the portal. This means users can sign up and log in without manual contact creation within the app.\\n* **Existing contacts without mapped accounts**: If a user is already a contact within the app but does not have a mapped account, they can still log in and create a ticket. In this scenario, the login is performed under the default workspace assigned to the contact.\\n* **Account",
"title": "Customer portal | Computer for Support Teams | DevRev"
},
{
"id": "ART-1978_KNOWLEDGE_NODE-39",
"text": "toggle and craft your own title and description.\\n7. Enable **Public portal** to allow unauthenticated users to view/search public articles.\\n8. Click **Save & publish** to make the changes visible on your portal.\\n\\nIf you want to customize the font color and favicon, contact DevRev support. For favicon customization, an icon in .ico format is needed.\\n\\nCustomize portal URL\\n--------------------\\n\\nBy default, your customer portal is hosted at support.devrev.ai/<yourcompany>. The",
"title": "Customer portal | Computer for Support Teams | DevRev"
},
{
"id": "ART-2027_KNOWLEDGE_NODE-31",
"text": "to the ticket via email. They cannot view the ticket on the portal, as they are added to the **Email members** field but not to the **Reported by** field.\\n\\nEmployees\\n\\n* With DevRev account (added to email thread)\\n\\n *Added to:* **To**, **CC**, or **Email members** field.\\n\\n *Is able to:* View the ticket on DevRev, reply via email, and receive in-app notifications. If they make changes to ticket attributes, they remain subscribers.\\n* Manually added subscribers\\n\\n *Added to:*",
"title": "Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2027_KNOWLEDGE_NODE-30",
"text": "or @mentioned in the DevRev app.\\n\\n *Is able to:* View the ticket on the portal and reply via email as an email member.\\n* A customer admin for the same workspace\\n\\n *Added to:* **Customer Admins** group.\\n\\n *Is able to:* View the ticket on the portal once their workspace is updated on the ticket.\\n* An end user outside original sender's organization\\n\\n *Added to:* **To** or **CC** fields in the email thread, or mentioned in the DevRev app (adds them to **CC**).\\n\\n *Is able to:* Reply",
"title": "Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-1978_KNOWLEDGE_NODE-0",
"text": "b\"Customer portal | Computer for Support Teams | DevRev\\n\\n* Computer\\n* Resources\\n* [Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nComputer\\n\\nResources\\n\\n[Our Customers](/case-study)\\n\\n[Login](https://app.devrev.ai/login)[Book a demo](/request-a-demo)\\n\\nSearch\\n\\n`CTRL`\\xc2\\xa0+\\xc2\\xa0`K`\\n\\n* [Introduction](/docs)\\n* [Computer by DevRev](/docs/intro)\\n\\n + [Core concepts](/docs/product/core)\\n + [Apps](/docs/product/apps)\\n +",
"title": "Customer portal | Computer for Support Teams | DevRev"
},
{
"id": "ART-2027_KNOWLEDGE_NODE-29",
"text": "your communication requirements.\\n\\nThe visibility and interaction capabilities with a ticket in DevRev are determined by the user's role and how they were added to the email thread.\\n\\nEnd users\\n\\n* Original sender\\n\\n *Added to:* **Reported by** or **Email members** field.\\n\\n *Is able to:* View the ticket on the portal and reply via email.\\n* An end user in the same organization\\n\\n *Added to:* **To** or **CC** fields in the email thread; **Reported by** field, **Email members** field,",
"title": "Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-6174_KNOWLEDGE_NODE-29",
"text": "rules\\n\\nWorkflows enable seamless handovers from automated conversations to your support teams when necessary.\\n\\nPlug widget end-user experience\\n-------------------------------\\n\\nWhen a conversation is converted to a ticket in the Plug widget:\\n\\n* The ticket number and basic details appear in the same conversation pane.\\n* Users can click **Details** to view complete ticket information.\\n* If the **Tickets** tab is enabled in Plug, users can track their ticket status",
"title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev"
}
] |
9c20f56a-3add-4189-9dac-4e2a5e9b281c
|
FORBIDDEN error when creating sprint board
|
[
{
"id": "ART-15506_KNOWLEDGE_NODE-15",
"text": "expired. |\\n| 403 Forbidden | The request was forbidden. | Check the authorization header for errors and make sure the token is a valid AAT. |\\n| 404 Not Found | The requested resource could not be found. | Verify the endpoint URL is correct. |\\n| 429 Too Many Requests | Rate limit exceeded. | Implement request throttling or wait before retrying. |\\n| 500 Internal Server Error | Server encounters an unexpected error. | Wait and try again later. If the issue persists, contact support with the",
"title": "Identify your users with Plug | DevRev | Docs"
},
{
"id": "ART-1958_KNOWLEDGE_NODE-27",
"text": "of all the roles associated with the target. If at least one role provides the necessary privilege, say create privilege, the actor is granted permission to proceed with the action, allowing them to create the issue.\\n\\n```\\nGroups\\n\\n\\n\\nGroups\\n\\n\\n\\nUser\\n\\n\\n\\nEngineering\\n\\n\\n\\nSupport\\n\\n\\n\\nRole READ on parts\\n\\n\\n\\nRole CREATE on tickets\\n\\n\\n\\nCREATE on tickets \\nREAD on parts\\n```\\n\\nIf a user attempts an action they\\'re not authorized to perform, they see a message which says \"You",
"title": "Access control | Computer by DevRev | DevRev"
}
] |
f339aa34-adea-4749-a289-07b29f31acc6
|
how to open help section in DevRev
|
[
{
"id": "ART-15507_KNOWLEDGE_NODE-22",
"text": "supported by our DevRev SDK. The support chat feature can be shown as a modal screen from the top-most screen.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | DevRev.showSupport() |\\n```\\n\\n### Create a new support conversation\\n\\nYou can initiate a new support conversation directly from your app. This method displays the support chat screen and simultaneously creates a new conversation.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | DevRev.createSupportConversation() |\\n```\\n\\n### In-app link handling\\n\\nIn",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-12449_KNOWLEDGE_NODE-16",
"text": "this stage, your app is fully configured to utilize all functionalities of the DevRev SDK. Pressing the support button directs the user to the chat interface, enabling effective interaction and support.\\n\\n### In-app link handling\\n\\nThe DevRev SDK provides a mechanism to handle links opened from within any screen that is part of the DevRev SDK.\\n\\nYou can fully customize the link handling behavior by setting the specialized in-app link handler. That way you can decide what should happen when a",
"title": "Features — DevRev | Docs"
},
{
"id": "ART-1983_KNOWLEDGE_NODE-32",
"text": "Q&A on the DevRev app by pressing cmd+K on Mac or Ctrl+K on Windows. Q&As appear within the KB section of the Search bar. You can search Q&As by entering keywords within a Question or Answer.\\n\\nQ&A structure\\n-------------\\n\\n* **Question**: Define the customer query.\\n* **Answer**: Provide the corresponding solution or information.\\n* **Part**: Choose the product or service area the Q&A pertains to.\\n* **Status**: Determine the progress phase of the Q&A.\\n + *Published*: These Q&As are live",
"title": "Questions & answers | Computer for Support Teams | DevRev"
},
{
"id": "ART-4255_KNOWLEDGE_NODE-13",
"text": "1| DevRev.showSupport(context: Context) \\n ---|---\\n[/code] \\n \\nThe DevRev SDK also provides a support button, which can be integrated into your application. To include it on the current screen, add the following code to your XML layout:\\n\\n[code]\\n\\n 1| <ai.devrev.sdk.plug.view.PlugFloatingActionButton \\n ---|--- \\n 2| android:id=\"@+id/plug_fab\" \\n 3| android:layout_width=\"wrap_content\" \\n 4| android:layout_height=\"wrap_content\" \\n 5|",
"title": "DevRev SDK for Android — DevRev | Docs"
},
{
"id": "ART-4256_KNOWLEDGE_NODE-10",
"text": "following method:\\n\\n[code]\\n\\n 1| DevRev.showSupport() \\n ---|---\\n[/code] \\n \\n### Creating a new support conversation\\n\\nYou can initiate a new support conversation directly from your app. This method displays the support chat screen and simultaneously creates a new conversation.\\n\\n[code]\\n\\n 1| DevRev.createSupportConversation() \\n ---|---\\n[/code] \\n \\n### In-app link handling\\n\\nIn certain cases, tapping links in the support chat opens them in the app instead of a",
"title": "DevRev SDK for React Native — DevRev | Docs"
},
{
"id": "ART-12967_KNOWLEDGE_NODE-6",
"text": "[Support](https://devrev.ai/support)\\n * [Search](https://devrev.ai/search)\\n * [PLuG - User Engagement](https://devrev.ai/plug-user-engagement)\\n * [PLuG - User Observability](https://devrev.ai/plug-observability)\\n * [Marketplace](https://marketplace.devrev.ai/)\\n\\nPlatform\\n\\n * [Airdrop](https://devrev.ai/airdrop)\\n * [Analytics](https://devrev.ai/analytics)\\n * [Workflow Engine](https://devrev.ai/workflow-engine)\\n * [Turing AI](https://devrev.ai/turing-ai)\\n\\nResources\\n\\n *",
"title": "Get Metric Definition (POST) — DevRev | Docs"
},
{
"id": "ART-12987_KNOWLEDGE_NODE-11",
"text": "[Support](https://devrev.ai/support)\\n * [Search](https://devrev.ai/search)\\n * [PLuG - User Engagement](https://devrev.ai/plug-user-engagement)\\n * [PLuG - User Observability](https://devrev.ai/plug-observability)\\n * [Marketplace](https://marketplace.devrev.ai/)\\n\\nPlatform\\n\\n * [Airdrop](https://devrev.ai/airdrop)\\n * [Analytics](https://devrev.ai/analytics)\\n * [Workflow Engine](https://devrev.ai/workflow-engine)\\n * [Turing AI](https://devrev.ai/turing-ai)\\n\\nResources\\n\\n *",
"title": "Update Command — DevRev | Docs"
},
{
"id": "ART-12456_KNOWLEDGE_NODE-10",
"text": "chat feature can be shown as a modal screen from the top-most screen.\\n\\n#####\\n\\nThis feature requires the SDK to be configured and the user to be identified, whether they are unverified or anonymous.\\n\\n[code]\\n\\n 1| DevRev.showSupport() \\n ---|---\\n[/code] \\n \\n### Creating a new support conversation\\n\\nYou can initiate a new support conversation directly from your app. This method displays the support chat screen and simultaneously creates a new conversation.\\n\\n[code]\\n\\n 1|",
"title": "Features — DevRev | Docs"
},
{
"id": "ART-16579_KNOWLEDGE_NODE-24",
"text": "DevRev.showSupport(); |\\n```\\n\\n#### Create a new support conversation\\n\\nYou can initiate a new support conversation directly from your app. This method displays the support chat screen and simultaneously creates a new conversation.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | DevRev.createSupportConversation(); |\\n```\\n\\nIn-app link handling\\n--------------------\\n\\nIn certain cases, tapping links in the support chat opens them in the app instead of a browser. You can control whether the chat modal",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-15515_KNOWLEDGE_NODE-25",
"text": "create a new support conversation directly, use the following method:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | DevRev.createSupportConversation(isAnimated:) |\\n```\\n\\nFor example:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | // Push the support chat screen to a navigation stack. |\\n| 2 | await DevRev.showSupport(from: mainNavigationController) |\\n| 3 | |\\n| 4 | // Show the support chat screen modally from a specific view controller. |\\n| 5 | await DevRev.showSupport(from: settingsViewController) |\\n| 6",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-1280_KNOWLEDGE_NODE-2",
"text": "check all the available commands, run the following command:\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | devrev --help |\\n```\\n\\nUse `devrev [command] --help` for more information about a command.\\n\\nAuthentication\\n--------------\\n\\n###### Authenticate\\n\\nTo authenticate, run the following command:\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | devrev profiles authenticate --org <DevOrg-slug-name> --usr <[email protected]> |\\n```\\n\\n**Arguments**:\\n\\n* `<DevOrg-slug-name>`: The unique slug name of your",
"title": "DevRev CLI reference | DevRev | Docs"
},
{
"id": "ART-12453_KNOWLEDGE_NODE-14",
"text": "display the support chat screen from the top-most view controller, use the following method:\\n\\n[code]\\n\\n 1| await DevRev.showSupport(isAnimated:) \\n ---|---\\n[/code] \\n \\nFor example:\\n\\n[code]\\n\\n 1| // Push the support chat screen to a navigation stack. \\n ---|--- \\n 2| await DevRev.showSupport(from: mainNavigationController) \\n 3| \\n 4| // Show the support chat screen modally from a specific view controller. \\n 5| await DevRev.showSupport(from:",
"title": "Features — DevRev | Docs"
},
{
"id": "ART-15515_KNOWLEDGE_NODE-26",
"text": "| |\\n| 7 | // Show the support chat screen from the top-most view controller, without an animation. |\\n| 8 | await DevRev.showSupport(isAnimated: false) |\\n| 9 | |\\n| 10 | // Create a new support conversation directly from the top-most view controller. |\\n| 11 | await DevRev.createSupportConversation(isAnimated: true) |\\n```\\n\\n### SwiftUI\\n\\nTo display the support chat screen in a SwiftUI app, you can use the following view:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | DevRev.supportView",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-12449_KNOWLEDGE_NODE-13",
"text": "dialog, your application should use the `showSupport` API, as shown in the following example:\\n\\n###### Kotlin\\n\\n###### Java\\n\\n[code]\\n\\n 1| DevRev.showSupport(context: Context) \\n ---|---\\n[/code] \\n \\n#### Creating a new conversation\\n\\nYou have the ability to create a new conversation from within your app. The method will show the support chat screen and create a new conversation at the same time.\\n\\n###### Kotlin\\n\\n###### Java\\n\\n[code]\\n\\n 1|",
"title": "Features — DevRev | Docs"
},
{
"id": "ART-4257_KNOWLEDGE_NODE-16",
"text": "view controller, without an animation. \\n 8| await DevRev.showSupport(isAnimated: false)\\n[/code] \\n \\n### SwiftUI\\n\\nTo display the support chat screen in a SwiftUI app, you can use the following view:\\n\\n[code]\\n\\n 1| DevRev.supportView \\n ---|---\\n[/code] \\n \\n#### New conversation closure\\n\\nYou can receive a callback when a new conversation is created by setting the following closure:\\n\\n[code]\\n\\n 1| DevRev.conversationCreatedCompletion \\n ---|---\\n[/code] \\n",
"title": "DevRev SDK for iOS — DevRev | Docs"
},
{
"id": "ART-12453_KNOWLEDGE_NODE-15",
"text": "settingsViewController) \\n 6| \\n 7| // Show the support chat screen from the top-most view controller, without an animation. \\n 8| await DevRev.showSupport(isAnimated: false)\\n[/code] \\n \\n### SwiftUI\\n\\nTo display the support chat screen in a SwiftUI app, you can use the following view:\\n\\n[code]\\n\\n 1| DevRev.supportView \\n ---|---\\n[/code] \\n \\n#### New conversation closure\\n\\nYou can receive a callback when a new conversation is created by setting the following",
"title": "Features — DevRev | Docs"
},
{
"id": "ART-12453_KNOWLEDGE_NODE-13",
"text": "view controller or the top-most one, or can be pushed onto a navigation stack.\\n\\nTo show the support chat screen in your app, you can use the following overloaded method:\\n\\n[code]\\n\\n 1| await DevRev.showSupport(from:isAnimated:) \\n ---|---\\n[/code] \\n \\n * When a `UIViewController` is passed as the `from` parameter, the screen is shown modally.\\n\\n * When a `UINavigationController` is passed as the `from` parameter, the screen is pushed onto the navigation stack.\\n\\nIf you want to",
"title": "Features — DevRev | Docs"
},
{
"id": "ART-15513_KNOWLEDGE_NODE-23",
"text": "Array of websites associated with the account |\\n| `tier` | `String?` | The account\\xe2\\x80\\x99s tier or plan level |\\n| `customFields` | `[String: Any]?` | Dictionary of custom fields configured in DevRev |\\n\\nPlug support chat\\n-----------------\\n\\nOnce user identification is complete, you can start using the chat (conversations) dialog supported by our DevRev SDK. To open the chat dialog, your application should use the `showSupport` API, as shown in the following example:\\n\\n######",
"title": "Features | DevRev | Docs"
}
] |
bda45aec-389d-4e41-9d32-147eef8a1b6c
|
three different login options video
|
[
{
"id": "ART-1978_KNOWLEDGE_NODE-34",
"text": "registered email address and go to **Settings** > **User management** > **Groups > Customer Admins**.\\n2. Select the **Add User** option in the top-right corner to search for the customer whom you want to designate as a customer admin.\\n\\n### Customer portal login methods\\n\\nThe customer portal supports three login methods:\\n\\n1. Email OTP (One-Time Password): User enters their email, receives a one-time code, and enters it to log in.\\n2. SSO: Users log in through organization\\xe2\\x80\\x99s",
"title": "Customer portal | Computer for Support Teams | DevRev"
},
{
"id": "ART-15510_KNOWLEDGE_NODE-6",
"text": "identifier, ensuring that no other data is stored or associated with the user.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | DevRev.identifyAnonymousUser(successCallback, errorCallback) |\\n```\\n\\n### Unverified identification\\n\\nThe unverified identification method identifies users with a unique identifier, but it does not verify their identity with the DevRev backend.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | DevRev.identifyUnverifiedUser(identity, successCallback, errorCallback) |\\n```\\n\\n### Verified",
"title": "Features | DevRev | Docs"
}
] |
043056b2-fa00-4474-9e1d-7ecf9ebd4532
|
create my view in explore tab
|
[
{
"id": "ART-1952_KNOWLEDGE_NODE-27",
"text": "bring in data from other sources as well.\\n\\nDiscover\\n--------\\n\\nTo get started, click the \\xe2\\x9a\\xa1 button on a vista. The following options are available:\\n\\n* Create New Report\\n* View Past Reports: Created by me or shared with me\\n\\nYou can also search for reports and find more on the **Explore** page.\\n\\n![]()\\n\\n### Create\\n\\nYou can create your own reports by adding a name, description, and creating widgets. Here, you'll also be able to preview your report and make any necessary",
"title": "Vista Reports | Vistas | Computer by DevRev | DevRev"
},
{
"id": "ART-16615_KNOWLEDGE_NODE-30",
"text": "**Hide columns**: Click on 3 dots next to a column to hide it from the view to reduce clutter\\n7. **Save preferences**: For any change in view preference settings like filter, sort, column, row selection click Save on top to save it as a new view or update the existing view\\n\\nBest practices\\n--------------\\n\\n* **Optimal Setup**: Use Stage or Status as your primary column grouping since these represent natural workflow progression. Reserve swimlanes for secondary attributes like Owner,",
"title": "Board view | Vistas | Computer by DevRev | DevRev"
},
{
"id": "ART-1949_KNOWLEDGE_NODE-25",
"text": "**Tickets**; **Build > Issues** and **Now, Next, Later**; and **Product > Parts**. Depending on the type of object there are different options for querying, sorting, customizing, and grouping.\\n\\n\\xf0\\x9f\\x8e\\xa5 Video: Applying filters to Vistas\\n\\nCreate a vista\\n--------------\\n\\n1. Select the object you want to make a list of, for example, tickets.\\n2. Make a change to the default view of the object by applying a filter, sorting, grouping, or customizing. A **Save as** button appears in the",
"title": "Vistas | Computer by DevRev | DevRev"
},
{
"id": "ART-1949_KNOWLEDGE_NODE-26",
"text": "upper-right corner after you make a change.\\n You can toggle on **Show groups** in **Group by** dropdown to open up a side panel showing the groups.\\n\\n![]()\\n\\n![]()\\n\\nYou can also apply **Actions** > **Smart Clustering** if the number of tickets or issues is under 10,000. Clustering isn't available for conversations.\\n\\n1. Click **Save as**. You can give the list a name, and description and save it which causes it to show up in the **My list** section at the bottom of the left-side nav",
"title": "Vistas | Computer by DevRev | DevRev"
}
] |
a2e491ac-7bc7-49d0-92ba-a55e9cc2fbca
|
output of for each node
|
[
{
"id": "ART-12393_KNOWLEDGE_NODE-25",
"text": "with their timestamp, execution time, and the status.\\n\\n If you don't see your latest run, click the refresh button on the top right of the runs view table.\\n4. Click the run. The workflow overview of that specific run is shown.\\n5. Click any of the nodes to see the input values and the output values of that particular step.\\n\\n Click the star button to get an AI-generated actionable explanation of the error.\\n\\n[PreviousWorkflow",
"title": "Troubleshooting | Workflows | Computer by DevRev | DevRev"
},
{
"id": "ART-1976_KNOWLEDGE_NODE-25",
"text": "and effective resolution. Users can design workflows tailored to various scenarios; the example below illustrates a basic routing use case.\\n\\n| NODE | ACTIVITY |\\n| --- | --- |\\n| Trigger | Ticket created |\\n| Action | Pick user by group |\\n| Action | Update ticket |\\n| | ID: Ticket created > Output > ID |\\n| | Group > Output > ID |\\n| | Owned by > Set: Pick user > Output > User |\\n\\nOrgs can set up pull-based routing by updating the group instead of the user ID in the workflow illustrated",
"title": "Routing | Computer for Support Teams | DevRev"
},
{
"id": "ART-15345_KNOWLEDGE_NODE-1",
"text": "<token>\" |\\n```\\n\\n[Try it](/api-reference/customization/stage-diagrams-list?explorer=true)\\n\\n200Retrieved\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"result\": [ |\\n| 3 | { |\\n| 4 | \"id\": \"string\", |\\n| 5 | \"stages\": [ |\\n| 6 | { |\\n| 7 | \"is_deprecated\": true, |\\n| 8 | \"is_start\": true, |\\n| 9 | \"stage\": { |\\n| 10 | \"id\": \"string\", |\\n| 11 | \"display_id\": \"string\", |\\n| 12 | \"name\": \"string\" |\\n| 13 | }, |\\n| 14 | \"transitions\": [ |\\n| 15 | { |\\n| 16 | \"target_stage\": { |\\n| 17 | \"id\":",
"title": "List Stage Diagrams | DevRev | Docs"
},
{
"id": "ART-1972_KNOWLEDGE_NODE-27",
"text": "by Channel**\\n\\n Number of tickets where SLA was breached for each source channel.\\n* **SLA breaches by Subtype**\\n\\n Number of tickets where SLA was breached for each ticket subtype.\\n* **SLA breaches by Owner**\\n\\n Number of Tickets with SLA breaches for ticket owners.\\n* **Avg CSAT by SLA status**\\n\\n Average CSAT rating of tickets w.r.t. their SLA status and severity.\\n* **Unassigned Tickets with SLA breaches per Customer**\\n\\n Number of Unassigned Tickets with SLA breaches for each",
"title": "Ticket-SLA Analytics | Support analytics | Computer for Support Teams | DevRev"
}
] |
2142d866-1912-4393-9cb8-21144082e6ca
|
What about agents in DevRev?
|
[
{
"id": "ART-15792_KNOWLEDGE_NODE-3",
"text": "and coordinating across teams while syncing actions back to existing systems.DevRev\\'s AI Agents\\n\\nDevRev sells the following AI agents:CX Agent (Customer Experience Agent)What is DevRev\\'s CX Agent?\\n\\nAI agent to improve customer experience by resolving up to 85% of support tickets without human intervention.\\n\\nKey Features:\\n\\nIntegrates with every data source seamlessly:Connect to all your systems without complicated workflows. CX agent automatically processes structured and unstructured",
"title": "DevRev Products and Agents"
},
{
"id": "ART-15792_KNOWLEDGE_NODE-2",
"text": "structured around two critical business dimensions: Products (Dev) and Customers (Rev). This architectural approach ensures that AI agents have comprehensive context when making decisions or taking actions.\\n\\nAgentic AI capabilities: DevRev provides both out-of-the-box agents and an Agent Studio to build, customize, deploy and manage agents. Users can instruct these agents in plain language to execute complex workflows autonomously, with agents capable of creating tickets, updating records,",
"title": "DevRev Products and Agents"
},
{
"id": "ART-15643_KNOWLEDGE_NODE-5",
"text": "called DevRev Airdrop.\\n\\nWe then organize your information into a patented Knowledge Graph - a living network of data built around what matters most: your Products (Dev) and your Customers (Rev).\\n\\nThis graph powers our agentic AI. It doesn't just find information; it takes autonomous action. You give our agents instructions in plain language, and they can execute complex workflows on your behalf. Or, build your own agents with our agent builder - no coding required.\\n\\nFor example, when a",
"title": "DevRev Corp Narrative - for PLuG on website"
},
{
"id": "ART-13178_KNOWLEDGE_NODE-52",
"text": "the gap between cutting-edge AI capabilities and existing enterprise infrastructure.\\n\\n### AgentOS: The unified platform\\n\\nAt the core of DevRev\\xe2\\x80\\x99s approach is AgentOS, a unified system connecting humans and AI agents in one seamless environment. This platform provides autonomous agents with essential tools and data while offering humans an intuitive interface to define agent capabilities and collaborate in real-time.\\n\\n### Complete data integration\\n\\nUnlike solutions that pull",
"title": "Understanding Agentic AI: Capabilities and Implications for the Future"
},
{
"id": "ART-13178_KNOWLEDGE_NODE-53",
"text": "information at runtime, DevRev employs continuous synchronization across systems. Its platform indexes data from over 30 integrations into a knowledge graph that meaningfully connects products, work processes, and customers.\\n\\n### Rich contextual intelligence\\n\\nDevRev\\xe2\\x80\\x99s approach ensures AI agents operate with robust context. The system creates relationships between disparate information sources, enabling agents to understand complex business situations and take appropriate actions",
"title": "Understanding Agentic AI: Capabilities and Implications for the Future"
},
{
"id": "ART-12459_KNOWLEDGE_NODE-10",
"text": "Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise Search?](https://devrev.ai/what-is-enterprise-search)\\n * [What is Conversational AI?](https://devrev.ai/what-is-conversational-ai)\\n\\n[](https://devrev.ai)\\n\\n[](https://www.linkedin.com/company/devrev)[](https://medium.com/devrev)[](https://twitter.com/devrev)\\n\\n[System Status](https://devrev.ai/status)\\n\\n\\xc2\\xa9 2025 DevRev",
"title": "Migration guide — DevRev | Docs"
},
{
"id": "ART-4097_KNOWLEDGE_NODE-7",
"text": "Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise Search?](https://devrev.ai/what-is-enterprise-search)\\n * [What is Conversational AI?](https://devrev.ai/what-is-conversational-ai)\\n\\n[](https://devrev.ai)\\n\\n[](https://www.linkedin.com/company/devrev)[](https://medium.com/devrev)[](https://twitter.com/devrev)\\n\\n[System Status](https://devrev.ai/status)\\n\\n\\xc2\\xa9 2025 DevRev",
"title": "Delete Rev User — DevRev | Docs"
},
{
"id": "ART-12997_KNOWLEDGE_NODE-13",
"text": "Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise Search?](https://devrev.ai/what-is-enterprise-search)\\n * [What is Conversational AI?](https://devrev.ai/what-is-conversational-ai)\\n\\n[](https://devrev.ai)\\n\\n[](https://www.linkedin.com/company/devrev)[](https://medium.com/devrev)[](https://twitter.com/devrev)\\n\\n[System Status](https://devrev.ai/status)\\n\\n\\xc2\\xa9 2025 DevRev",
"title": "Create Directory — DevRev | Docs"
},
{
"id": "ART-15792_KNOWLEDGE_NODE-5",
"text": "automatically. Our self-learning system updates your knowledge base without manual intervention.\\n\\nSource: [DevRev CX Agent](https://devrev.ai/cx-agent)Search AgentWhat is DevRev Search Agent?\\n\\nBuilt on a secure, permission-aware knowledge graph, DevRev Search allows you to find all your company\\'s information in one place, regardless of where or how it\\'s stored, saving employees valuable time.\\n\\nKey Features:\\n\\nApp Integration: With DevRev you can integrate with all of your apps",
"title": "DevRev Products and Agents"
},
{
"id": "ART-15643_KNOWLEDGE_NODE-8",
"text": "enough.\\n\\nDevRev\\xe2\\x80\\x99s Agentic AI is fully integrated, which means our agents can Create, Read, Update, and Delete. So our AI doesn\\xe2\\x80\\x99t just answer questions or summarize information; it creates tickets, updates records, and coordinates across teams, syncing those actions back to your existing systems of record.\\n\\nAnd finally, we\\xe2\\x80\\x99re a partner who understands your needs - because we\\xe2\\x80\\x99ve been there, too. Our founders built Nutanix and lived the problems that",
"title": "DevRev Corp Narrative - for PLuG on website"
},
{
"id": "ART-15618_KNOWLEDGE_NODE-15",
"text": "behavior\\n\\nDevRev : AI-native architecture offering outcome-driven workflows and intuitive, conversational agents User Experience\\n\\nAgentforce : Multiple tabs, nested screens, fragmented multi-stage agent creation process\\n\\nDevRev : Consolidated actions, modern agent-first UX, single cohesive screen for agent building Learning Capabilities\\n\\nAgentforce : Manual improvements, no learning from real usage or customer interactions\\n\\nDevRev : Auto-learning by identifying knowledge gaps",
"title": "SF Agentforce - Competitive - for the PLuG on website"
},
{
"id": "ART-15621_KNOWLEDGE_NODE-9",
"text": "engineering)\\n\\nEach agent requiring individual configuration\\n\\nOperational complexity through multiple specialized systems\\n\\nSeparate prompt library and agent library adding user complexity\\n\\nDevRev Approach : Unified agent architecture\\n\\nSingle interface with dynamic skill loading per user requests\\n\\nEliminates operational overhead through centralized management\\n\\nPredictable performance model with coupled AI agent-LLM architecture\\n\\nConsistent reasoning patterns ensuring reliable",
"title": "Glean - Competitive - for the PLuG on website"
},
{
"id": "ART-13178_KNOWLEDGE_NODE-38",
"text": "understanding. DevRev\\xe2\\x80\\x99s platform leverages multiple models for optimal performance across diverse tasks.\\n\\nThese large language models serve as the \\xe2\\x80\\x9cbrain\\xe2\\x80\\x9d of agentic AI systems, enabling them to process natural language, understand context, and generate appropriate responses or actions based on their training.\\n\\n### 2\\\\. Specialized capabilities\\n\\nPlatforms offer industry-specific AI agents designed for particular business functions. Healthcare-focused",
"title": "Understanding Agentic AI: Capabilities and Implications for the Future"
},
{
"id": "ART-1032_KNOWLEDGE_NODE-7",
"text": "every major update is closely monitored using DevRev PLuG's agentic AI capabilities, a proven effective practice in identifying and fixing numerous issues through intelligent automation. For instance, after updating the video-playing control feature, the team's agentic AI agents detected through (Computer, for User Insights) that users struggled to locate the control buttons. The intelligent system automatically flagged this usability issue, enabling the team to react swiftly and revert to the",
"title": "Optimizing user experience: ShemarooMe's success with DevRev"
},
{
"id": "ART-17649_KNOWLEDGE_NODE-10",
"text": "DevRev the single source of truth for customer support - enhancing efficiency, cutting costs, and providing a more unified experience for both agents and customers.\\n\\nBenefits\\n--------\\n\\n* Support agents quickly access information relevant to each platform section\\n* Customers receive consistent, contextually relevant support\\n* Teams maintain separation between different support instances\\n* Support grows smoothly with the company's expanding platform\\n* AI assistance becomes more accurate",
"title": "Leading APAC fintech transforms support with multi-instance AI solution"
},
{
"id": "ART-1442_KNOWLEDGE_NODE-23",
"text": "[Privacy Policy](https://devrev.ai/legal/privacy-policy)\\n * [Terms of Service](https://devrev.ai/legal/terms-of-service)\\n\\nLearn\\n\\n * [What are AI Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise Search?](https://devrev.ai/what-is-enterprise-search)\\n * [What is Conversational",
"title": "Get Work — DevRev | Docs"
},
{
"id": "ART-12982_KNOWLEDGE_NODE-15",
"text": "Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise Search?](https://devrev.ai/what-is-enterprise-search)\\n * [What is Conversational AI?](https://devrev.ai/what-is-conversational-ai)\\n\\n[](https://devrev.ai)\\n\\n[](https://www.linkedin.com/company/devrev)[](https://medium.com/devrev)[](https://twitter.com/devrev)\\n\\n[System Status](https://devrev.ai/status)\\n\\n\\xc2\\xa9 2025 DevRev Inc.\\n\\n'",
"title": "Create Command — DevRev | Docs"
},
{
"id": "ART-1457_KNOWLEDGE_NODE-14",
"text": "Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise Search?](https://devrev.ai/what-is-enterprise-search)\\n * [What is Conversational AI?](https://devrev.ai/what-is-conversational-ai)\\n\\n[](https://devrev.ai)\\n\\n[](https://www.linkedin.com/company/devrev)[](https://medium.com/devrev)[](https://twitter.com/devrev)\\n\\n[System Status](https://devrev.ai/status)\\n\\n\\xc2\\xa9 2025 DevRev Inc.\\n\\n'",
"title": "Get SLA Tracker — DevRev | Docs"
},
{
"id": "ART-4172_KNOWLEDGE_NODE-4",
"text": "automated and human-assisted service aims to improve response times, reduce workload on human agents, and enhance customer satisfaction.\\n\\nOur AI Support Agent is active on many DevRev surfaces ([www.DevRev.ai](http://www.devrev.ai/) | [https://app.DevRev.ai](https://app.devrev.ai/) | [www.support.DevRev.ai](http://www.support.devrev.ai/)) for your convenience.To have a better idea of what the DevRev Customer Support Experience is like, please reference the following:\\n\\n![]()\\n\\n### DevRev",
"title": "DevRev Service Level Agreement"
},
{
"id": "ART-1408_KNOWLEDGE_NODE-8",
"text": "Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise Search?](https://devrev.ai/what-is-enterprise-search)\\n * [What is Conversational AI?](https://devrev.ai/what-is-conversational-ai)\\n\\n[](https://devrev.ai)\\n\\n[](https://www.linkedin.com/company/devrev)[](https://medium.com/devrev)[](https://twitter.com/devrev)\\n\\n[System Status](https://devrev.ai/status)\\n\\n\\xc2\\xa9 2025 DevRev Inc.\\n\\n'",
"title": "Delete Part — DevRev | Docs"
},
{
"id": "ART-1406_KNOWLEDGE_NODE-7",
"text": "Agents?](https://devrev.ai/what-are-ai-agents)\\n * [What is Agentic AI?](https://devrev.ai/what-is-agentic-ai)\\n * [What is Enterprise Search?](https://devrev.ai/what-is-enterprise-search)\\n * [What is Conversational AI?](https://devrev.ai/what-is-conversational-ai)\\n\\n[](https://devrev.ai)\\n\\n[](https://www.linkedin.com/company/devrev)[](https://medium.com/devrev)[](https://twitter.com/devrev)\\n\\n[System Status](https://devrev.ai/status)\\n\\n\\xc2\\xa9 2025 DevRev Inc.\\n\\n'",
"title": "Product components — DevRev | Docs"
},
{
"id": "ART-15792_KNOWLEDGE_NODE-9",
"text": "information sharing and reporting by converging support, product and user data in one shared view.\\n\\nAutomated knowledge base management: AI agents remember successful resolutions and instantly apply them to future issues, reducing customer wait time.\\n\\nSource: [DevRev Support](https://devrev.ai/support)BuildWhat is DevRev Build?\\n\\nDevRev Build is a full-featured product development platform built for modern businesses and trusted by leading organizations\\n\\nKey Features:\\n\\nAuto-generate",
"title": "DevRev Products and Agents"
},
{
"id": "ART-15627_KNOWLEDGE_NODE-7",
"text": "session record)\\n\\nWhat\\'s included in PLuG Ultimate?\\n\\nAll Pay-as-you-go features\\n\\nAdvanced functionality for scale\\n\\nVolume discounting\\n\\nUnderstanding users wherever they are\\n\\nDevRev AgentOS Pricing For detailed pricing and to get started: \\xc2\\xa0 https://devrev.ai/pricing/agentos How is AgentOS priced? AgentOS is available only through custom pricing. Contact sales for a quote. What\\'s included in AgentOS?\\n\\nFlexible pricing models: usage-based or predictable fixed pricing\\n\\nFull",
"title": "DevRev Pricing - for the PLuG on the website"
}
] |
d761b291-3018-4f6b-810d-87d1bfbf7986
|
how to start using Computer in DevRev
|
[
{
"id": "ART-16789_KNOWLEDGE_NODE-10",
"text": "dots.\\n\\nYou can also access Computer on your browser inside the DevRev app on the URL https://app.devrev.ai/<your-org-name>/computerQ: How do I use the Computer desktop app?\\n\\nAlternative questions: \"Desktop app shortcuts\" \"Computer keyboard shortcuts\"\\n\\nAnswer: The Computer desktop app provides quick access via keyboard shortcuts: \\xe2\\x8c\\x98+. on Mac or Ctrl+. on Windows. We call it \"Command dot\" or \"Control dot\" - because Computer connects the dots. This gives you instant access to your",
"title": "Computer General FAQs"
},
{
"id": "ART-16789_KNOWLEDGE_NODE-11",
"text": "AI teammate from anywhere on your computer.Q: How do I use the Computer on my browser?\\n\\nAnswer: You can access Computer on your browser inside the DevRev app on the URL https://app.devrev.ai/<your-org-name>/computerComputer CapabilitiesQ: What can Computer do?\\n\\nAlternative questions: \"Computer features\" \"Computer capabilities\" \"What are Computer\\'s abilities?\"\\n\\nAnswer: Computer can search across all your data, answer questions with full business context, generate content, automate routine",
"title": "Computer General FAQs"
},
{
"id": "ART-1988_KNOWLEDGE_NODE-25",
"text": "Computer for Builders supports both activities and offers integrations with other systems.\\n\\n\\xf0\\x9f\\x8e\\xa5 Video: Build overview\\n\\n\\xf0\\x9f\\x91\\x89 Getting started\\n-----------------\\n\\nThe most important first step in getting started with any DevRev app is to describe the structure of your product in [Trails](./parts). Because all work is associated with a part, you need to define the parts of your product.\\n\\n[Vistas](./vistas) are lists of objects that can be sorted, grouped,",
"title": "Computer for Builders | DevRev"
},
{
"id": "ART-1969_KNOWLEDGE_NODE-25",
"text": "and development teams, driving product decisions through a precise understanding of customers' voices.\\n\\nComputer for Support Teams is an AI-powered tool for live chat and ticket management that fosters a *culture of support* in your company.\\n\\n\\xf0\\x9f\\x8e\\xa5 Video: Support Overview\\n\\n\\xf0\\x9f\\x91\\x89 Getting started\\n-----------------\\n\\nThe most important first step in getting started with any DevRev app is to describe the structure of your product in\\xc2\\xa0[Trails](./parts). Because",
"title": "Computer for Support Teams | DevRev"
},
{
"id": "ART-4176_KNOWLEDGE_NODE-8",
"text": "interested. Sign up for the waitlist. Then never look back.\\n\\nSIGN UP\\n\\nComputer\\n\\n[Meet Computer](/meet-computer)[How Computer works](/how-computer-works)\\n\\nApps\\n\\n[For support teams](/for-support-teams)[For your customers](/for-customers)[For builders](/for-builders)[For user insights](/for-user-insights)\\n\\nResources\\n\\n[Blog](/blog)[Marketplace](https://marketplace.devrev.ai/)[DevRevU training](/docs/DevRevU)[Documentation](/docs)[API",
"title": "Computer by DevRev | Your New Conversational AI Teammate"
},
{
"id": "ART-1995_KNOWLEDGE_NODE-26",
"text": "identity.\\n* Install [Slash commands](https://marketplace.devrev.ai/slash-commands-snapin) to access specific actions quickly and use Computer to perform the functions.\\n* Install [Converge support and build snap-in](/marketplace/convergence_sot6yu88) to ensure that customer conversations, support tickets, product enhancements, and development issues are always in sync.\\n\\nManage development work\\n-----------------------\\n\\n* [Create issues](./issues#create-an-issue) for your developers to work",
"title": "Build best practices | Computer for Builders | DevRev"
},
{
"id": "ART-1969_KNOWLEDGE_NODE-28",
"text": "engineers. To get a list of the available commands, type / in a conversation response text box.\\n\\n\\xf0\\x9f\\x8e\\xab Tickets\\n---------\\n\\nThe benefit of Computer by DevRev is that conversations can be linked to support [tickets](../product/tickets), and tickets can be linked to build issues. This [linkage](../product/apps) means that all work can be traced back to customer concerns or requests.\\n\\nSlash commands are available in tickets to provide AI assistance to customer experience engineers.",
"title": "Computer for Support Teams | DevRev"
},
{
"id": "ART-2000_KNOWLEDGE_NODE-32",
"text": "an account, go to **Account** > **Workspace** and select **New workspace**.\\n\\n[PreviousComputer for Growth Teams](/docs/product/grow)[NextOpportunities](/docs/product/opportunity)\\n\\n#### On this page\\n\\n* [Create an account](#create-an-account)\\n* [Using the DevRev app](#using-the-devrev-app)\\n* [Bulk import accounts](#bulk-import-accounts)\\n* [Using DevRev APIs](#using-devrev-apis)\\n* [Account attributes](#account-attributes)\\n* [External reference](#external-reference)\\n* [Add a",
"title": "Accounts | Computer for Growth Teams | DevRev"
},
{
"id": "ART-4177_KNOWLEDGE_NODE-4",
"text": "DevRev\\n\\nGet started with activating conversational AI in DevRev to enhance customer interactions](https://youtu.be/PWJ4eUQO2Tw?feature=shared)[![]()\\n\\nMastering Semantic Search in DevRev\\n\\nDiscover how to master semantic search in DevRev and transform your workflow](https://youtu.be/yWhEBcsLR60?feature=shared)[![]()\\n\\nContinue Your Journey: The Full Playlist\\n\\nExplore the full 'Getting started with DevRev' playlist to begin your journey](https://devrev.navattic.com/bv10lxn)\\n\\nSupport",
"title": "DevRev University - DevRev for Startups"
},
{
"id": "ART-4165_KNOWLEDGE_NODE-11",
"text": "here, so don\\xe2\\x80\\x99t try telling us you\\xe2\\x80\\x99re not interested. Sign up for the waitlist. Then never look back.\\n\\nSIGN UP\\n\\nComputer\\n\\n[Meet Computer](/meet-computer)[How Computer works](/how-computer-works)\\n\\nApps\\n\\n[For support teams](/for-support-teams)[For your customers](/for-customers)[For builders](/for-builders)[For user insights](/for-user-insights)\\n\\nResources\\n\\n[Blog](/blog)[Marketplace](https://marketplace.devrev.ai/)[DevRevU",
"title": "Computer by DevRev: AI Infrastructure for Connected Enterprise Data | DevRev"
},
{
"id": "ART-4162_KNOWLEDGE_NODE-11",
"text": "here, so don\\xe2\\x80\\x99t try telling us you\\xe2\\x80\\x99re not interested. Sign up for the waitlist. Then never look back.\\n\\nSIGN UP\\n\\nComputer\\n\\n[Meet Computer](/meet-computer)[How Computer works](/how-computer-works)\\n\\nApps\\n\\n[For support teams](/for-support-teams)[For your customers](/for-customers)[For builders](/for-builders)[For user insights](/for-user-insights)\\n\\nResources\\n\\n[Blog](/blog)[Marketplace](https://marketplace.devrev.ai/)[DevRevU",
"title": "Computer by DevRev: AI Infrastructure for Connected Enterprise Data | DevRev"
}
] |
940924bf-210d-41df-8218-a4acb8e67d96
|
SAML 2.0 OAuth 2.0 external authentication integration
|
[
{
"id": "ART-15267_KNOWLEDGE_NODE-1",
"text": "or Okta.\\n\\n\\xf0\\x9f\\x93\\x8c For more information for about authentication connections, refer to [External identity provider setup](https://docs.devrev.ai/product/sso-saml).\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/api-reference/artifacts/versions-prepare)[#### Create Dev Orgs Auth Connection\\n\\nNext](/api-reference/auth-connections/dev-org-auth-connections-create)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)'",
"title": "Identity provider | DevRev | Docs"
},
{
"id": "ART-1691_KNOWLEDGE_NODE-3",
"text": "credentials:** During development, you\\xe2\\x80\\x99ll provide your developer keyring of type `oauth-secret` which contains client ID and client secret for the chosen service within the keyring definition. These credentials are securely stored and not distributed with your published snap-in.\\n\\n 3. **OAuth 2.0 flow:** When your snap-in needs to access user data from the external service, it initiates the OAuth flow. This typically involves redirecting the user to the service\\xe2\\x80\\x99s login",
"title": "OAuth 2.0 configuration: Securely storing access tokens — DevRev | Docs"
},
{
"id": "ART-1687_KNOWLEDGE_NODE-2",
"text": "DevRev snap-in) without needing to share their passwords directly. This approach enhances security and user convenience.\\n\\nFor comprehensive information about the OAuth specification, refer to the official documentation: [OAuth 2.0](https://oauth.net/2/).\\n\\nUsing OAuth 2.0 keyrings\\n------------------------\\n\\n1. **Define the keyring:** Within your snap-in manifest, define a keyring specifically for OAuth credentials. DevRev offers pre-defined keyring types for popular services like Slack or",
"title": "OAuth 2.0 configuration: Securely storing access tokens | DevRev | Docs"
},
{
"id": "ART-4052_KNOWLEDGE_NODE-1",
"text": "authentication connections, refer to [External identity provider setup](https://docs.devrev.ai/product/sso-saml).\\n\\nWas this page helpful?YesNo\\n\\n[Security tokensUp Next](/public/api-reference/auth-tokens/security-tokens)\\n\\n[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)\\n\\n[Enterprise grade security to protect customer dataLearn more about it.](https://devrev.ai/blog/soc-compliance)\\n\\nProduct\\n\\n *",
"title": "Identity provider — DevRev | Docs"
},
{
"id": "ART-1966_KNOWLEDGE_NODE-32",
"text": "external identity provider.\\n\\n![]()\\n\\nBefore proceeding, ensure you have the following:\\n\\n* A Personal Access Token (PAT) with admin permissions.\\n* Connection details from your identity provider setup.\\n* Your dev\\\\_oid and organization slug from the previous steps.\\n\\n### Step 1: Create the authentication connection\\n\\nAn authentication connection is a configuration object that tells DevRev how to communicate with your identity provider. Use the [auth connections create",
"title": "External identity provider setup | Computer by DevRev | DevRev"
},
{
"id": "ART-1966_KNOWLEDGE_NODE-29",
"text": "are some common examples:\\n\\nAzure ADGoogle WorkspaceJump CloudOkta\\n\\n1. Log in to Azure Active Directory and select **Enterprise applications > + New application**.\\n2. Search for \"Azure AD SAML Toolkit\" in the **Browse Azure AD Gallery** and select it.\\n3. Enter DevRev as the name and click **Create**.\\n4. Select **Single sign-on > SAML**.\\n5. Edit the **Basic SAML Configuration** and enter the following parameters.\\n\\n * **Identifier** (Entity ID):",
"title": "External identity provider setup | Computer by DevRev | DevRev"
},
{
"id": "ART-16086_KNOWLEDGE_NODE-4",
"text": "connection post-creation via a toggle.\\n\\nProvides contextual guidance and error handling throughout the setup flow.\\n\\n4. Architecture\\n\\nPlease refer the below attachment\\n\\n5. Detailed Design\\n\\nPlease refer the below attachment\\n\\n6.API Endpoints\\n\\nEndpoint\\n\\nMethod\\n\\nInclude Internal\\n\\nDescription\\n\\n/auth-tokens.create\\n\\nPost\\n\\nNo\\n\\nCreates an auth token\\n\\n/auth-connections.create\\n\\nPost\\n\\nNo\\n\\nCreates a new SSO connection (SAML or",
"title": "Single Sign On Configuration 3P Node"
},
{
"id": "ART-1966_KNOWLEDGE_NODE-30",
"text": "urn:auth0:tf-devrev-prod:<connection\\\\_name>\\n * **Reply URL** (Assertion Consumer Service URL): https://auth.devrev.ai/login/callback?connection=<connection\\\\_name>\\n * **Sign on URL**: https://app.devrev.ai/<DEV\\\\_ORG\\\\_SLUG>\\n\\n ![]()\\n\\n The <connection\\\\_name> must be the same in both parameters and follow the naming pattern described earlier.\\n6. Go to **Copy > SAML Certificates** and save the **App Federation Metadata URL**.\\n7. In the Azure portal, go to the application named",
"title": "External identity provider setup | Computer by DevRev | DevRev"
},
{
"id": "ART-1966_KNOWLEDGE_NODE-33",
"text": "API](https://developer.devrev.ai/public/api-reference/auth-connections/dev-org-auth-connections-create) to create this connection.\\n\\nChoose the appropriate protocol based on your identity provider:\\n\\nSAML 2.0OpenID Connect\\n\\n**For SAML-based identity providers (Azure AD, Okta, etc.):**\\n\\n```\\n```\\n1 curl --location --request POST \\'https://api.devrev.ai/dev-orgs.auth-connections.create\\' \\\\\\n\\n\\n\\n2 --header \\'Authorization: Bearer <your PAT>\\' \\\\\\n\\n\\n\\n3 --header \\'Content-Type:",
"title": "External identity provider setup | Computer by DevRev | DevRev"
},
{
"id": "ART-1966_KNOWLEDGE_NODE-42",
"text": "process from your identity provider\\'s portal. The latter is not supported on DevRev.\\n\\nA workaround for supporting IDP-initiated SSO is to bookmark your DevRev workspace URL (that is https://app.devrev.ai/<DEV\\\\_ORG\\\\_SLUG>) in your IDP. With only SSO Auth connection enabled, the experience would be as seamless as SP-initiated SSO.\\n\\n### Parameter reference\\n\\n* <your PAT>: Your Personal Access Token with admin permissions\\n* <dev\\\\_oid>: Your DevRev organization ID (from the initial API",
"title": "External identity provider setup | Computer by DevRev | DevRev"
},
{
"id": "ART-1549_KNOWLEDGE_NODE-169",
"text": "an OIDC authentication connection.\\n\\nShow 5 properties\\nOR\\nSamlp\\n\\nObject encapsulating the configuration parameters for a SAML authentication connection.\\n\\nShow 4 properties\\nOR\\nWaad\\n\\nObject encapsulating the configuration parameters for an Azure AD authentication connection.\\n\\nShow 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\n\\nConnection object that specifies the configuration for an authentication connection that is set up for a Dev",
"title": "List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1543_KNOWLEDGE_NODE-169",
"text": "an OIDC authentication connection.\\n\\nShow 5 properties\\nOR\\nSamlp\\n\\nObject encapsulating the configuration parameters for a SAML authentication connection.\\n\\nShow 4 properties\\nOR\\nWaad\\n\\nObject encapsulating the configuration parameters for an Azure AD authentication connection.\\n\\nShow 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\n\\nConnection object that specifies the configuration for an authentication connection that is set up for a Dev",
"title": "Metric Definitions List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1562_KNOWLEDGE_NODE-169",
"text": "an OIDC authentication connection.\\n\\nShow 5 properties\\nOR\\nSamlp\\n\\nObject encapsulating the configuration parameters for a SAML authentication connection.\\n\\nShow 4 properties\\nOR\\nWaad\\n\\nObject encapsulating the configuration parameters for an Azure AD authentication connection.\\n\\nShow 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\n\\nConnection object that specifies the configuration for an authentication connection that is set up for a Dev",
"title": "Get (Beta) — DevRev | Docs"
},
{
"id": "ART-1566_KNOWLEDGE_NODE-169",
"text": "an OIDC authentication connection.\\n\\nShow 5 properties\\nOR\\nSamlp\\n\\nObject encapsulating the configuration parameters for a SAML authentication connection.\\n\\nShow 4 properties\\nOR\\nWaad\\n\\nObject encapsulating the configuration parameters for an Azure AD authentication connection.\\n\\nShow 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\n\\nConnection object that specifies the configuration for an authentication connection that is set up for a Dev",
"title": "Transition (Beta) — DevRev | Docs"
},
{
"id": "ART-1560_KNOWLEDGE_NODE-169",
"text": "an OIDC authentication connection.\\n\\nShow 5 properties\\nOR\\nSamlp\\n\\nObject encapsulating the configuration parameters for a SAML authentication connection.\\n\\nShow 4 properties\\nOR\\nWaad\\n\\nObject encapsulating the configuration parameters for an Azure AD authentication connection.\\n\\nShow 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\n\\nConnection object that specifies the configuration for an authentication connection that is set up for a Dev",
"title": "Assign (Beta) — DevRev | Docs"
},
{
"id": "ART-1545_KNOWLEDGE_NODE-169",
"text": "an OIDC authentication connection.\\n\\nShow 5 properties\\nOR\\nSamlp\\n\\nObject encapsulating the configuration parameters for a SAML authentication connection.\\n\\nShow 4 properties\\nOR\\nWaad\\n\\nObject encapsulating the configuration parameters for an Azure AD authentication connection.\\n\\nShow 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\n\\nConnection object that specifies the configuration for an authentication connection that is set up for a Dev",
"title": "Create (Beta) — DevRev | Docs"
},
{
"id": "ART-1551_KNOWLEDGE_NODE-169",
"text": "an OIDC authentication connection.\\n\\nShow 5 properties\\nOR\\nSamlp\\n\\nObject encapsulating the configuration parameters for a SAML authentication connection.\\n\\nShow 4 properties\\nOR\\nWaad\\n\\nObject encapsulating the configuration parameters for an Azure AD authentication connection.\\n\\nShow 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\n\\nConnection object that specifies the configuration for an authentication connection that is set up for a Dev",
"title": "Update (Beta) — DevRev | Docs"
},
{
"id": "ART-16086_KNOWLEDGE_NODE-2",
"text": "and back-and-forth coordination The absence of a guided experience adds unnecessary friction to an otherwise smooth onboarding process. The proposed agentic skill aims to eliminate these barriers with a step-by-step SSO setup flow embedded directly within DevRev.\\n\\n3.System Specifications\\n\\nSupports both SAML and OIDC connection types.\\n\\nInteractive, step-by-step setup via agent conversation.\\n\\nCollects essential inputs from the user based on the selected connection type:-For SAML: sign-in",
"title": "Single Sign On Configuration 3P Node"
},
{
"id": "ART-1966_KNOWLEDGE_NODE-34",
"text": "application/json\\' \\\\\\n\\n\\n\\n4 --data-raw \\'{\\n\\n\\n\\n5 \"type\": \"samlp\",\\n\\n\\n\\n6 \"sign_in_endpoint\": \"<sign_in_endpoint>\",\\n\\n\\n\\n7 \"signing_cert\": \"<signing_cert>\",\\n\\n\\n\\n8 \"connection_name\": \"<connection_name>\",\\n\\n\\n\\n9 \"display_name\": \"<display_name>\"\\n\\n\\n\\n10 }\\'\\n```\\n\\nShow more\\n```\\n\\n**Expected successful response:**\\n\\n```\\n```\\n1 {\\n\\n\\n\\n2 \"auth_connection\": {\\n\\n\\n\\n3 \"id\": \"con_12345678\",\\n\\n\\n\\n4 \"display_name\": \"<display_name>\",\\n\\n\\n\\n5 \"enabled\":",
"title": "External identity provider setup | Computer by DevRev | DevRev"
},
{
"id": "ART-16086_KNOWLEDGE_NODE-6",
"text": "bases\\n\\n8. Conclusion\\n\\nThe SSO Setup Agent offers a fully guided, interactive setup for configuring SSO, with support for both SAML and OIDC. It includes validation, previews, and uses workflow-based skills to automate the process with minimal user intervention.'",
"title": "Single Sign On Configuration 3P Node"
},
{
"id": "ART-1966_KNOWLEDGE_NODE-28",
"text": "alphanumeric characters or hyphens, without consecutive or trailing hyphens.\\n* Be unique within your organization.\\n* Follow the pattern of: <dev\\\\_oid>-<CUSTOM-STRING>.\\n\\nThe API call to create the connection fails if this pattern is not followed.\\n\\nSetup DevRev as service provider on identity provider\\n-----------------------------------------------------\\n\\nYou can register DevRev as a service provider in any identity provider that supports SAML 2.0 or OpenID Connect (OIDC). The following",
"title": "External identity provider setup | Computer by DevRev | DevRev"
},
{
"id": "ART-1283_KNOWLEDGE_NODE-18",
"text": "is_optional : true 14 scope_delimiter : \" , \" # Delimiter used to separate scopes in the authorization request 15 oauth_secret : custom-oauth-credentials # Developer keyring that contains OAuth2 client ID and client secret. Shall be of keyring type `oauth-secret`. 16 authorize : # Configuration for the authorization request 17 type : \" config \" 18 grant_type : \" authorization_code \" 19 auth_url : \" https://example.com/oauth/authorize \" 20 token_url : \" https://example.com/oauth/token \" 21",
"title": "Keyrings — DevRev | Docs"
},
{
"id": "ART-1491_KNOWLEDGE_NODE-18",
"text": "is_optional : true 14 scope_delimiter : \" , \" # Delimiter used to separate scopes in the authorization request 15 oauth_secret : custom-oauth-credentials # Developer keyring that contains OAuth2 client ID and client secret. Shall be of keyring type `oauth-secret`. 16 authorize : # Configuration for the authorization request 17 type : \" config \" 18 grant_type : \" authorization_code \" 19 auth_url : \" https://example.com/oauth/authorize \" 20 token_url : \" https://example.com/oauth/token \" 21",
"title": "Keyrings — DevRev | Docs"
},
{
"id": "ART-15369_KNOWLEDGE_NODE-4",
"text": "SAML\\nauthentication connection.\\n\\nShow 6 properties\\n\\nOR\\n\\nwaadobjectRequired\\n\\nObject encapsulating the configuration parameters for an Azure AD\\nauthentication connection.\\n\\nShow 5 properties\\n\\n### Response\\n\\nResponse for the request to create a new enterprise authentication\\nconnection.\\n\\nauth\\\\_connectionobject\\n\\nConnection object that specifies the configuration for an\\nauthentication connection that is set up for a Dev organization.\\n\\nShow 6 variants\\n\\n### Errors\\n\\n400\\n\\nBad",
"title": "Create Dev Orgs Auth Connection | DevRev | Docs"
},
{
"id": "ART-16086_KNOWLEDGE_NODE-3",
"text": "endpoint and signing certificate (with optional metadata URL parsing).-For OIDC: issuer URL, client ID, and client secret.\\n\\nAllows users to provide a display name and choose to enter a connection name or auto-generate one based on DevRev org ID.\\n\\nValidates all mandatory fields and ensures completeness before proceeding.\\n\\nDisplays a summary of the configuration for user confirmation before connection creation.\\n\\nCreates the SSO connection using DevRev APIs.\\n\\nOptionally enables the",
"title": "Single Sign On Configuration 3P Node"
},
{
"id": "ART-1829_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1801_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1653_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1633_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1654_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1821_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1303_KNOWLEDGE_NODE-108",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Export Post — DevRev | Docs"
},
{
"id": "ART-1588_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1802_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1837_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-15716_KNOWLEDGE_NODE-25",
"text": "not working, try resending the code or using a different phone number.\\n\\nIf the problem continues, escalate with the user\\xe2\\x80\\x99s phone number, timestamp, and any error messages for backend review.\\n\\nOkta Integration and Forcing SSO\\n\\nYes, DevRev integrates with Okta for Single Sign-On (SSO). You can enforce SSO for your organization, ensuring all users authenticate via Okta. DevRev also supports SCIM for automated user provisioning and deprovisioning 12.\\n\\nTo set this up:\\n\\nGo to",
"title": "Support queries related playbook"
},
{
"id": "ART-1825_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1655_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1832_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1590_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1803_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1609_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1824_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1833_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1607_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1823_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1605_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1834_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1804_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Self — DevRev | Docs"
},
{
"id": "ART-1597_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1822_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1835_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1595_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1836_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1593_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1818_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Sla Trackers Get Post — DevRev | Docs"
},
{
"id": "ART-1305_KNOWLEDGE_NODE-110",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-4052_KNOWLEDGE_NODE-0",
"text": "b'[](/public/api-reference/auth-connections/identity-provider)\\n\\nPublic\\n\\n[API Reference](/public/api-reference/getting-started)[auth-connections](/public/api-reference/auth-connections/identity-provider)\\n\\n#\\n\\nIdentity provider\\n\\n`auth-connection` endpoint\\n\\n\\xe2\\x84\\xb9\\xef\\xb8\\x8f An authentication connection enables users to log in to DevRev through an external identity provider such as Azure AD, Google Workspace, Jump Cloud, or Okta.\\n\\n\\xf0\\x9f\\x93\\x8c For more information for about",
"title": "Identity provider — DevRev | Docs"
},
{
"id": "ART-1509_KNOWLEDGE_NODE-105",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Prepare — DevRev | Docs"
},
{
"id": "ART-1828_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1575_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1641_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1830_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1782_KNOWLEDGE_NODE-105",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1805_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1591_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1826_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1649_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1838_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1806_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Self Post — DevRev | Docs"
},
{
"id": "ART-1639_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Export Post — DevRev | Docs"
},
{
"id": "ART-1577_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1306_KNOWLEDGE_NODE-108",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1651_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1652_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1691_KNOWLEDGE_NODE-11",
"text": "token. \\n 30| authorize: # The authorize section is used to get the authorization code from the user and exchange it for an access token. \\n 31| type: \"config\" \\n 32| auth_url: <auth_url> # The URL to which the user is redirected to authorize the connection. \\n 33| token_url: <token_url> # The URL to which the authorization code is sent to get the access token. \\n 34| grant_type: \"authorization_code\" \\n 35| auth_query_parameters: \\n",
"title": "OAuth 2.0 configuration: Securely storing access tokens — DevRev | Docs"
},
{
"id": "ART-1636_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1637_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1831_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1650_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1592_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1643_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1787_KNOWLEDGE_NODE-107",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1579_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1827_KNOWLEDGE_NODE-103",
"text": "the user will need to explicitly enable this. Keep in mind that at a time, only one authentication connection can be enabled for a Dev organization. At present, only 5 enterprise connections can be created by an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\nGoogle Apps Show 5 properties\\nOR\\nOidc Show 5 properties\\nOR\\nSamlp Show 4 properties\\nOR\\nWaad Show 5 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nauth_connection object\\nConnection object that specifies the",
"title": "Update — DevRev | Docs"
}
] |
621a49aa-6eff-4209-a2b0-0c36fb43c8ce
|
arrange articles by customer type
|
[
{
"id": "ART-1982_KNOWLEDGE_NODE-26",
"text": "parts are distinct entities. Collections categorize articles on the Customer Portal, while parts represent the structure and components of a product or service.\\n\\nYou can nest multiple collections within a single collection to create a well-structured framework for your customer support portal and Plug widget by DevRev.\\n\\nVisibility of articles and collections\\n--------------------------------------\\n\\nThe accessibility of a collection and its articles to customers depends on their combined",
"title": "Collections | Knowledge Base | Computer for Support Teams | DevRev"
},
{
"id": "ART-1985_KNOWLEDGE_NODE-36",
"text": "verified (signed-in) customers can view the article.\\n* **Verified Customers**: Limits visibility to customers signed in to the customer portal.\\n* **Customer Admins**: Restricts access to a subset of verified customers in the **Customer Admin** group. Membership in this group is managed through [**Settings** > **Customer Management** > **Segments**](https://app.devrev.ai/?setting=segments)\\\\*.\\n\\n ![]()\\n\\n If an article is for internal use only, leave the **Visible to** field blank.\\n\\n###",
"title": "Articles | Knowledge Base | Computer for Support Teams | DevRev"
},
{
"id": "ART-1980_KNOWLEDGE_NODE-29",
"text": "by customers through the Plug widget and customer portal.\\n\\nIn the Plug widget, articles are available in two places: the search bar and the Help section.\\n\\n**Search bar**\\n\\n![]()\\n\\n**Help section**\\n\\n![]()\\n\\nUsers can also view articles grouped into collections by visiting your help center hosted on your website. The visibility of collections and articles depends on the **Visible to** settings configured.\\n\\n[### Articles](/docs/product/articles)[###",
"title": "Knowledge Base | Computer for Support Teams | DevRev"
},
{
"id": "ART-1982_KNOWLEDGE_NODE-25",
"text": "Base](/docs/product/knowledge-base)\\n[Collections](/docs/product/collection)\\n\\nCollections\\n===========\\n\\nCollections serve as the parent categories for articles within your Customer Portal, establishing a hierarchical structure for organizing and presenting content to customers. By designating a collection as the parent, you create a top-level category. If you prefer to relocate this collection to another directory, you can change its parent directory accordingly.\\n\\n![]()\\n\\nCollections and",
"title": "Collections | Knowledge Base | Computer for Support Teams | DevRev"
},
{
"id": "ART-1985_KNOWLEDGE_NODE-35",
"text": "and no longer required can be removed by archiving them.\\n\\nVisibility settings\\n-------------------\\n\\n### Article visibility\\n\\nTo control who can view the articles, open the **Visible to** menu. This displays all external groups that the article can be shared with. By default, the following groups are available:\\n\\n* **Customers**: Allows public access without verification.\\n\\n ![]()\\n\\n Public access requires the public portal to be enabled. If the public portal is not enabled, only",
"title": "Articles | Knowledge Base | Computer for Support Teams | DevRev"
},
{
"id": "ART-1308_KNOWLEDGE_NODE-43",
"text": "list of objects Optional\\nFilter for articles based on intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\narticles list of objects\\nThe article entries matching the request.\\nShow 19 properties\\ntotal integer\\nTotal number of article items for the request.\\nnext_cursor string Optional\\nThe cursor used to iterate subsequent results in accordance to the sort order. If not set, then no later elements exist.\\nprev_cursor string Optional\\nThe cursor used to iterate",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1302_KNOWLEDGE_NODE-46",
"text": "list of objects Optional\\nFilter for articles based on intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\narticles list of objects\\nThe article entries matching the request.\\nShow 19 properties\\ntotal integer\\nTotal number of article items for the request.\\nnext_cursor string Optional\\nThe cursor used to iterate subsequent results in accordance to the sort order. If not set, then no later elements exist.\\nprev_cursor string Optional\\nThe cursor used to iterate",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1301_KNOWLEDGE_NODE-46",
"text": "list of objects Optional\\nFilter for articles based on intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\narticles list of objects\\nThe article entries matching the request.\\nShow 19 properties\\ntotal integer\\nTotal number of article items for the request.\\nnext_cursor string Optional\\nThe cursor used to iterate subsequent results in accordance to the sort order. If not set, then no later elements exist.\\nprev_cursor string Optional\\nThe cursor used to iterate",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1835_KNOWLEDGE_NODE-38",
"text": "Optional\\nFilters for articles owned by any of the provided users.\\nscope list of longs Optional\\nFilter for the scope of the articles. If this is not provided, then only external articles are returned.\\nshared_with list of objects Optional\\nFilter for articles based on intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\narticles list of objects\\nThe article entries matching the request.\\nShow 19 properties\\ntotal integer\\nTotal number of article items for the",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1982_KNOWLEDGE_NODE-28",
"text": "collection is **Public** but all the articles within it are intended for internal use only, the collection itself won\\xe2\\x80\\x99t be visible to the public in the help center.\\n\\nCollection management\\n---------------------\\n\\n### Create a collection\\n\\n1. Go to **Settings > Support > Article Collections**.\\n2. Click **+Collection** and fill in the following details:\\n\\n * Title\\n * Description\\n * Parent\\n3. Enable the **Publish Collection** option if you want your customers to see the",
"title": "Collections | Knowledge Base | Computer for Support Teams | DevRev"
},
{
"id": "ART-1783_KNOWLEDGE_NODE-38",
"text": "Optional\\nFilters for articles owned by any of the provided users.\\nscope list of longs Optional\\nFilter for the scope of the articles. If this is not provided, then only external articles are returned.\\nshared_with list of objects Optional\\nFilter for articles based on intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\narticles list of objects\\nThe article entries matching the request.\\nShow 19 properties\\ntotal integer\\nTotal number of article items for the",
"title": "Locate — DevRev | Docs"
},
{
"id": "ART-1779_KNOWLEDGE_NODE-38",
"text": "Optional\\nFilters for articles owned by any of the provided users.\\nscope list of longs Optional\\nFilter for the scope of the articles. If this is not provided, then only external articles are returned.\\nshared_with list of objects Optional\\nFilter for articles based on intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\narticles list of objects\\nThe article entries matching the request.\\nShow 19 properties\\ntotal integer\\nTotal number of article items for the",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1824_KNOWLEDGE_NODE-38",
"text": "Optional\\nFilters for articles owned by any of the provided users.\\nscope list of longs Optional\\nFilter for the scope of the articles. If this is not provided, then only external articles are returned.\\nshared_with list of objects Optional\\nFilter for articles based on intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\narticles list of objects\\nThe article entries matching the request.\\nShow 19 properties\\ntotal integer\\nTotal number of article items for the",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1830_KNOWLEDGE_NODE-38",
"text": "Optional\\nFilters for articles owned by any of the provided users.\\nscope list of longs Optional\\nFilter for the scope of the articles. If this is not provided, then only external articles are returned.\\nshared_with list of objects Optional\\nFilter for articles based on intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\narticles list of objects\\nThe article entries matching the request.\\nShow 19 properties\\ntotal integer\\nTotal number of article items for the",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1788_KNOWLEDGE_NODE-38",
"text": "Optional\\nFilters for articles owned by any of the provided users.\\nscope list of longs Optional\\nFilter for the scope of the articles. If this is not provided, then only external articles are returned.\\nshared_with list of objects Optional\\nFilter for articles based on intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\narticles list of objects\\nThe article entries matching the request.\\nShow 19 properties\\ntotal integer\\nTotal number of article items for the",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1801_KNOWLEDGE_NODE-38",
"text": "Optional\\nFilters for articles owned by any of the provided users.\\nscope list of longs Optional\\nFilter for the scope of the articles. If this is not provided, then only external articles are returned.\\nshared_with list of objects Optional\\nFilter for articles based on intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\narticles list of objects\\nThe article entries matching the request.\\nShow 19 properties\\ntotal integer\\nTotal number of article items for the",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1838_KNOWLEDGE_NODE-38",
"text": "Optional\\nFilters for articles owned by any of the provided users.\\nscope list of longs Optional\\nFilter for the scope of the articles. If this is not provided, then only external articles are returned.\\nshared_with list of objects Optional\\nFilter for articles based on intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\narticles list of objects\\nThe article entries matching the request.\\nShow 19 properties\\ntotal integer\\nTotal number of article items for the",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1633_KNOWLEDGE_NODE-38",
"text": "Optional\\nFilters for articles owned by any of the provided users.\\nscope list of longs Optional\\nFilter for the scope of the articles. If this is not provided, then only external articles are returned.\\nshared_with list of objects Optional\\nFilter for articles based on intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\narticles list of objects\\nThe article entries matching the request.\\nShow 19 properties\\ntotal integer\\nTotal number of article items for the",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1590_KNOWLEDGE_NODE-38",
"text": "Optional\\nFilters for articles owned by any of the provided users.\\nscope list of longs Optional\\nFilter for the scope of the articles. If this is not provided, then only external articles are returned.\\nshared_with list of objects Optional\\nFilter for articles based on intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\narticles list of objects\\nThe article entries matching the request.\\nShow 19 properties\\ntotal integer\\nTotal number of article items for the",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1597_KNOWLEDGE_NODE-38",
"text": "Optional\\nFilters for articles owned by any of the provided users.\\nscope list of longs Optional\\nFilter for the scope of the articles. If this is not provided, then only external articles are returned.\\nshared_with list of objects Optional\\nFilter for articles based on intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\narticles list of objects\\nThe article entries matching the request.\\nShow 19 properties\\ntotal integer\\nTotal number of article items for the",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-15293_KNOWLEDGE_NODE-12",
"text": "users.\\n\\nowned\\\\_bylist of stringsOptional\\n\\nFilters for articles owned by any of the provided users.\\n\\nparentlist of stringsOptional\\n\\nFilters for articles with the provided parent directories.\\n\\nscopelist of longsOptional\\n\\nFilter for the scope of the articles.\\n\\nshared\\\\_withlist of objectsOptional\\n\\nFilter for articles based on intended audience.\\n\\nShow 2 properties\\n\\ntagslist of stringsOptional\\n\\nFilters for article with any of the provided tags.\\n\\n### Response\\n\\nList articles",
"title": "List Articles (POST) | DevRev | Docs"
},
{
"id": "ART-1785_KNOWLEDGE_NODE-38",
"text": "Optional\\nFilters for articles owned by any of the provided users.\\nscope list of longs Optional\\nFilter for the scope of the articles. If this is not provided, then only external articles are returned.\\nshared_with list of objects Optional\\nFilter for articles based on intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\narticles list of objects\\nThe article entries matching the request.\\nShow 19 properties\\ntotal integer\\nTotal number of article items for the",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1805_KNOWLEDGE_NODE-38",
"text": "Optional\\nFilters for articles owned by any of the provided users.\\nscope list of longs Optional\\nFilter for the scope of the articles. If this is not provided, then only external articles are returned.\\nshared_with list of objects Optional\\nFilter for articles based on intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\narticles list of objects\\nThe article entries matching the request.\\nShow 19 properties\\ntotal integer\\nTotal number of article items for the",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1828_KNOWLEDGE_NODE-38",
"text": "Optional\\nFilters for articles owned by any of the provided users.\\nscope list of longs Optional\\nFilter for the scope of the articles. If this is not provided, then only external articles are returned.\\nshared_with list of objects Optional\\nFilter for articles based on intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\narticles list of objects\\nThe article entries matching the request.\\nShow 19 properties\\ntotal integer\\nTotal number of article items for the",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1575_KNOWLEDGE_NODE-38",
"text": "Optional\\nFilters for articles owned by any of the provided users.\\nscope list of longs Optional\\nFilter for the scope of the articles. If this is not provided, then only external articles are returned.\\nshared_with list of objects Optional\\nFilter for articles based on intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\narticles list of objects\\nThe article entries matching the request.\\nShow 19 properties\\ntotal integer\\nTotal number of article items for the",
"title": "Delete — DevRev | Docs"
}
] |
5191bbf7-0259-4c41-a942-2a0aaa6ff514
|
API to customize DevRev agent colors branding
|
[
{
"id": "ART-12456_KNOWLEDGE_NODE-13",
"text": "DevRev SDK allows you to configure the theme dynamically based on the system appearance, or use the theme configured on the DevRev portal. By default, the theme will be dynamic and follow the system appearance.\\n\\n[code]\\n\\n 1| DevRev.setPrefersSystemTheme(value: boolean) \\n ---|---\\n[/code] \\n \\n## Analytics\\n\\n#####\\n\\nThis feature requires the SDK to be configured and the user to be identified, whether they are unverified or anonymous.\\n\\nThe DevRev SDK allows you to send custom",
"title": "Features — DevRev | Docs"
},
{
"id": "ART-15509_KNOWLEDGE_NODE-6",
"text": "and more. It must be a valid hex color code, such as `#f0f0f0`. | String |\\n| `session_recording_options` | Options for recording observability sessions. | Refer to [Session recording options](https://devrev.ai/docs/plug/session-recording) |\\n| `accent_color` | The accent color of the Plug affects the launcher, new ticket and conversation buttons, conversation user text, and more. | String |\\n| `custom_launcher_selector` | A CSS selector string is used to match the element to which the widget",
"title": "Methods | DevRev | Docs"
},
{
"id": "ART-2897_KNOWLEDGE_NODE-7",
"text": "button text for new tickets and conversations, conversation user text, and more. It must be a valid hex color code, such as `#f0f0f0`.| String \\n`session_recording_options`| Options for recording observability sessions.| Refer to [Session recording options](https://devrev.ai/docs/plug/session-recording) \\n`accent_color`| The accent color of the PLuG affects the launcher, new ticket and conversation buttons, conversation user text, and more.| String \\n`custom_launcher_selector`| A CSS",
"title": "Methods — DevRev | Docs"
},
{
"id": "ART-2900_KNOWLEDGE_NODE-2",
"text": "theme](/public/sdks/web/customize#lightdark-theme)\\n\\n[SDKs](/public/sdks)[PLuG Web SDK](/public/sdks/web/installation)\\n\\n#\\n\\nCustom implementation\\n\\nPLuG has a completely [no-code way](https://docs.devrev.ai/plug/customize#branding-style-and-layout) of changing the look and interaction of your widget. In case you wish to make your PLuG widget more interactive and customized to how your app is structured, you can use these customization properties to set up your widget.\\n\\n#####\\n\\nIf you",
"title": "Custom implementation — DevRev | Docs"
},
{
"id": "ART-12470_KNOWLEDGE_NODE-0",
"text": "b'Update Brand | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nBeta\\n\\nBeta\\n\\nBeta\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/beta/api-reference/accounts/create)[brands](/beta/api-reference/brands/create)\\n\\nUpdate Brand\\n============\\n\\nBeta\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/brands.update\\n\\nPOST\\n\\n/brands.update\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/brands.update \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -H",
"title": "Update Brand | DevRev | Docs"
},
{
"id": "ART-12464_KNOWLEDGE_NODE-0",
"text": "b'Create Brand | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nBeta\\n\\nBeta\\n\\nBeta\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/beta/api-reference/accounts/create)[brands](/beta/api-reference/brands/create)\\n\\nCreate Brand\\n============\\n\\nBeta\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/brands.create\\n\\nPOST\\n\\n/brands.create\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/brands.create \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -H",
"title": "Create Brand | DevRev | Docs"
},
{
"id": "ART-15496_KNOWLEDGE_NODE-1",
"text": "SDK](/sdks/web/installation)\\n\\nCustom implementation\\n=====================\\n\\nCopy page\\n\\nPlug has a completely [no-code way](https://docs.devrev.ai/plug/customize#branding-style-and-layout) of changing the look and interaction of your widget. In case you wish to make your Plug widget more interactive and customized to how your app is structured, you can use these customization properties to set up your widget.\\n\\n##### \\n\\nIf you have customized these properties of the widget through the",
"title": "Custom implementation | DevRev | Docs"
},
{
"id": "ART-1466_KNOWLEDGE_NODE-9",
"text": "Identifies the user interacting with your app. | String | \\n| The color of the launcher, button text for new tickets and conversations, conversation user text, and more. It must be a valid hex color code, such as",
"title": "Methods — DevRev | Docs"
}
] |
f6163a4c-568e-4118-b087-d62500942928
|
Slack Integration bidirectional case management within Slack workspaces
|
[
{
"id": "ART-2035_KNOWLEDGE_NODE-37",
"text": "synchronized between DevRev and Slack.\\n\\nWork management using Slack\\n---------------------------\\n\\n### DevRev Tickets and Slack\\n\\nThe Slack snap-in allows users to create tickets directly from Slack. There are multiple ways to initiate ticket creation from any channel:\\n\\n* **Use the command:** Run /devrev create-ticket.\\n* **Message action:** Select **Create a new ticket** from the message actions.\\n* **Convert a Conversation:** Transform an ongoing conversation into a ticket. This is",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-10697_KNOWLEDGE_NODE-27",
"text": "bidirectional synchronization between DevRev objects and Slack channels.\\n* A workflow node has been added to create a Slack channel and automatically invite specified users.\\n* A random wait time (1-20 seconds) has been added before creating a conversation to prevent duplicate conversations on WhatsApp when messages are sent rapidly.\\n* Customer identification in Slack has been enhanced by resolving users via their Slack ID when their email is hidden.\\n* An optional field has been added to the",
"title": "February 2025 | Changelog | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-55",
"text": "Set up 2 way message synchronization between a complete Slack channel and DevRev object discussion. | - Slack connection - DevRev object ID - Slack channel ID | N/A |\\n\\nAdditional capabilities and limitations\\n---------------------------------------\\n\\n### 2-way sync between DevRev and Slack\\n\\n* If two-way sync is enabled on an object, new messages received from non-Slack source channels will appear in DevRev but won't sync to the Slack thread.\\n* By default, messages from bots, service",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-46",
"text": "**Auto-create incidents from Slack channels**, which automatically creates an incident for every direct message posted in specified Slack channels.\\n\\nThe first two options will open a pop-up modal with a new incident form, with some fields pre-populated based on the context.\\n\\n### Sync options\\n\\nIncidents support syncing messages both within a dedicated Slack thread and across an entire Slack channel, including all associated threads. The sync target is determined by the **Sync for new",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-40",
"text": "channel determines the sync location in DevRev:\\n\\n* **External/Connect channels:** Syncs with the **Customer Messages** panel.\\n* **Internal channels:** Syncs with the **Internal Discussions** panel.\\n\\nSyncing different panels to separate Slack threads is not supported.\\n\\n![]()\\n\\nOnly shared tickets are synchronized between DevRev and Slack.\\n\\n### Follow-up and merged Tickets\\n\\nThe Slack snap-in supports follow-up and merged tickets.\\n\\n* When two tickets merge, and both have syncing",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-54",
"text": "given DevRev user - Can be used to later send direct messages to the user on the Slack using Send message to Slack node. | - Slack connection - DevRev user id | - Slack user id |\\n| Start Thread Sync | - Set up 2 way message synchronization between a Slack thread and a DevRev object discussion. | - Slack connection - DevRev Object ID - Slack channel ID - Slack thread ID (message ID of parent message, returned by send message to Slack workflow node) | N/A |\\n| Start Channel Sync | -",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-58",
"text": "private or a DM.\\n\\n> In such cases, the object can still be created, but without two-way sync.\\n\\nDevRev object customization support\\n-----------------------------------\\n\\nThe Slack snap-in honors DevRev\\xe2\\x80\\x99s object customizations, including:\\n\\n* Custom fields and subtypes\\n* Stock field overrides\\n* Slack-specific client overrides\\n* Summary view card\\n\\nThe summary view card of all objects can be customized.\\n\\n* Only fields marked with **Show in Summary = true** in object",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-33",
"text": "DevRev app.\\n\\nIf a message is sent to a Slack thread belonging to an archived conversation, the Slack snap-in creates a new follow-up conversation, and all messages sync to this new conversation.\\n\\n![]()\\n\\nA Slack channel can be linked to only one DevRev account workspace, and vice versa.\\n\\nConversation roll window\\n------------------------\\n\\nTo avoid multiple conversations for related customer messages, a **conversation roll window** is used.\\n\\n* The roll window remains active for five",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-6174_KNOWLEDGE_NODE-30",
"text": "there.\\n\\n![]()\\n\\nSlack end-user experience\\n-------------------------\\n\\nWhen a conversation is converted to a ticket in Slack:\\n\\n* Ticket information appears within the same thread.\\n* All subsequent messages sync with the newly created ticket.\\n* The transition is seamless for the end user.\\n\\nConversation conversion scenarios\\n---------------------------------\\n\\nConsider converting a conversation to a ticket in these scenarios:\\n\\n* Complex issues requiring in-depth investigation\\n*",
"title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-43",
"text": "update** snap-in configuration.\\n* Applies only to tickets syncing with Slack threads.\\n* If enabled, the Slack snap-in will send notifications to the syncing thread whenever the ticket state changes.\\n\\n### Ticket digest\\n\\nTo see all open and in-progress tickets in Slack, use the /devrev ticket-digest command. This opens a modal with a paginated list of all open and in-progress tickets.\\n\\nDevRev Issues and Slack\\n-----------------------\\n\\nThe Slack snap-in allows issues to be created",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-44",
"text": "directly from Slack:\\n\\n* Using the /devrev create-issue command.\\n* Using the **Create a new issue** message action.\\n\\nBoth the options open a new pop-up modal with a new issue form. Some of the fields are pre-populated based on the messages in the thread.\\n\\n* The **Share with everyone** functionality operates identically to ticket creation. Only shared issues are synchronized between the platforms.\\n* The messages are always synced in the **Internal Discussions** panel with Slack thread.\\n*",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-41",
"text": "Slack threads, all the messages from both Slack threads reach only the primary ticket in DevRev, while messages from DevRev only sync to the primary ticket\\xe2\\x80\\x99s Slack thread.\\n* If only one ticket has a syncing Slack thread, that thread syncs with the primary ticket.\\n* No messages from the duplicate ticket sync to Slack.\\n* If a ticket is immutable but receives a new customer message in its Slack thread, a follow-up ticket is automatically created for future discussions.\\n\\n### New",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-39",
"text": "fields will auto-fill based on the messages.\\n\\n### Ticket sharing options\\n\\nThe new ticket modal in Slack includes a **Share with everyone** checkbox at the bottom:\\n\\n* **Enabled:** Shares the ticket details with the Slack channel via a summary card.\\n* **Disabled:** Keeps the ticket internal with no updates to the Slack channel.\\n\\nRegardless of sharing, the ticket details are visible to the creator in the submission modal.\\n\\n### Syncing details\\n\\nIf sharing is enabled, the type of Slack",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-49",
"text": "platform.\\n\\n1. **Ask while creating incident**\\n\\n* Only applicable for incidents created from Slack.\\n* This option adds a dropdown at the end of the incident form, letting the user choose the sync target for each incident individually.\\n\\n1. **Do not sync**\\n\\n* Incidents remain internal to DevRev without syncing to a new Slack channel or thread from which it was created.\\n\\nFor incidents that sync with dedicated Slack channels, you can configure automatic channel archiving when an incident",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-48",
"text": "channel.\\n\\n1. **Sync messages with the thread (for incidents created from Slack)**\\n\\n* Works only for incidents created from Slack.\\n* It syncs messages with the originating thread, similar to ticket and issue work items.\\n\\n1. **Sync messages with the notification thread**\\n\\n* Syncs with the thread of the incident notification sent on the channel mentioned in the **Channel ID to send incident notifications** configuration.\\n* Works for all incidents irrespective of source channel or",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-4199_KNOWLEDGE_NODE-27",
"text": "message.channels.\\n7. Add this custom app and the **DevRev Slack Bot** into the Slack channel from which you want to create the DevRev object.\\n\\nConfigure DevRev\\n----------------\\n\\n1. Add the Slack Signing Secret and Slack Bot Token copied from the custom Slack bot app.\\n2. Add the channel IDs for either incidents, tickets or issues.\\n3. Click the respective buttons to enable the sync between threads.\\n4. Select the part ID to associate a particular part.\\n5. Click **Save** and copy the",
"title": "Slack message agent | Automate | Snap-ins | DevRev"
},
{
"id": "ART-4271_KNOWLEDGE_NODE-28",
"text": "PLuG widget:\\n\\n * The ticket number and basic details appear in the same conversation pane.\\n * Users can click **Details** to view complete ticket information.\\n * If the **Tickets** tab is enabled in PLuG, users can track their ticket status there.\\n\\n### Slack experience\\n\\nWhen a conversation is converted to a ticket in Slack:\\n\\n * Ticket information is sent within the same thread.\\n * All subsequent messages sync with the newly created ticket.\\n * The transition is seamless for the",
"title": "Convert Conversations to Tickets | Conversations | Support | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-42",
"text": "ticket notifications\\n\\n* Enable through the **Notify on new ticket creation** snap-in configuration.\\n* Provide a Slack channel ID in the **Channel ID to send ticket notifications** configuration.\\n* Snap-in will send notifications to the target channel whenever a new ticket is created, regardless of the source channel or platform.\\n* Notification message threads are **not** synced between platforms.\\n\\n### Notifications for ticket state update\\n\\n* Enable through **Notify on ticket state",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-38",
"text": "recommended if you already have a conversation in progress. Configure the snap-in to send or not send a ticket summary card to the Slack thread using the **Notify on conversation to ticket conversion** setting. Regardless, the Slack thread will sync with the new ticket instead of the ongoing conversation.\\n\\n![]()\\n\\nSlack does not support slash commands in threads.\\n\\nChoosing one of the first two options will open a pop-up modal with the new ticket form. Complete the required fields; some",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-34",
"text": "minutes after a conversation is created.\\n* Any new message sent directly in the channel within this time frame is appended to the existing conversation.\\n* A new direct message from the customer resets the roll window timer.\\n* Any message sent from DevRev will be synced to the thread of the first message that initiated the conversation.\\n* Only messages within the thread of the originating message of the conversation are synced.\\n* Messages within Slack threads of follow-ups sent directly to",
"title": "Slack | Integrate | Snap-ins | DevRev"
}
] |
3776772f-e6d3-4629-a713-8c5ddfd3a1e2
|
articles not showing after connection
|
[
{
"id": "ART-15726_KNOWLEDGE_NODE-1",
"text": "is private (i.e., if the article is not shared with everyone in the external system).\\n\\nThis most frequently occurs if you're a customer success employee who helped a customer do an import and you're verifying the imported data. In that case consult the Airdrop import report:\\n\\nIf it says that all the extracted articles were created or updated in DevRev, then you can be reasonably sure that that was the case\\n\\nIf you're still skeptical you can ask the customer to verify that they see the",
"title": "Visibility of Airdrop-imported articles"
},
{
"id": "ART-15161_KNOWLEDGE_NODE-0",
"text": "b\"Articles and other help center items from Zendesk are intentionally extracted only during manual syncs (tier 2 sync) due to performance considerations. Including article extraction in periodic automatic syncs (tier 1) would significantly impact sync performance and time. Symptoms\\n\\nCollections with zero articles in DevRev while the same collections in Zendesk contain articles\\n\\nIncomplete article migration after initial integration setup\\n\\nArticles not updating in DevRev despite changes in",
"title": "Zendesk Articles are Extracted Only During Manual Sync"
},
{
"id": "ART-15726_KNOWLEDGE_NODE-0",
"text": "b\"If you just imported a bunch of articles from your favorite external system, but can't see them in DevRev, the most important question to ask yourself is whether that article was shared with you in the external system. Airdrop is permission-aware for articles, so if an article (or document, or page, whatever gets imported as an Airdrop article) was not shared with you in the external system, then you won't have access to it in DevRev (even if you're an admin), assuming the default visibility",
"title": "Visibility of Airdrop-imported articles"
},
{
"id": "ART-1985_KNOWLEDGE_NODE-39",
"text": "customers, the article should be visible to customers. If the **Visible to** option is set to **Verified Customers**, only signed-in customers are able to view the article.\\n* When sharing an external link with customers, the article status should be *Published*. If it is in *Draft* mode, they won\\xe2\\x80\\x99t be able to view it.\\n\\nArticle Formatting\\n------------------\\n\\nWhen you\\xe2\\x80\\x99re creating a new article or editing an existing article, formatting options are displayed. While",
"title": "Articles | Knowledge Base | Computer for Support Teams | DevRev"
},
{
"id": "ART-15726_KNOWLEDGE_NODE-2",
"text": "articles\\n\\nAs a last resort, you can ask the Airdrop team to check whether the articles are indeed in DevRev's database\"",
"title": "Visibility of Airdrop-imported articles"
},
{
"id": "ART-15161_KNOWLEDGE_NODE-1",
"text": "Zendesk Common Scenarios\\n\\nInitial sync failure : If there's a failure during the initial sync (which is tier 2/manual), the subsequent periodic syncs (tier 1) won't complete the article extraction process.\\n\\nNew articles added in Zendesk : Articles added to Zendesk after the initial integration will not appear in DevRev until a manual sync is performed. Resolution\\n\\nTo import or update Zendesk articles in DevRev:\\n\\nTrigger a manual sync from Zendesk to DevRev through the integration",
"title": "Zendesk Articles are Extracted Only During Manual Sync"
},
{
"id": "ART-15716_KNOWLEDGE_NODE-19",
"text": "DevRev documentation or contact support for CSV-specific workflows.\\n\\nTroubleshooting Missing Migrated Articles\\n\\nIf you can\\xe2\\x80\\x99t find your migrated articles:\\n\\nDouble-check the knowledge base section in your DevRev workspace.\\n\\nConfirm with your admin or implementation team which articles were migrated and to which workspace or project.\\n\\nSometimes, articles may be in draft/unpublished state or linked to a different part of the product.\\n\\nIf you still can\\xe2\\x80\\x99t locate",
"title": "Support queries related playbook"
},
{
"id": "ART-15161_KNOWLEDGE_NODE-2",
"text": "settings\\n\\nWait for the sync to complete\\n\\nVerify that all articles are now showing in DevRev collections Notes\\n\\nArticle creation dates should be preserved from the original Zendesk articles\\n\\nAll accessible Zendesk articles should be imported during a successful manual sync\\n\\nEnsure the account used for integration has sufficient permissions to access all articles in Zendesk\"",
"title": "Zendesk Articles are Extracted Only During Manual Sync"
},
{
"id": "ART-1980_KNOWLEDGE_NODE-29",
"text": "by customers through the Plug widget and customer portal.\\n\\nIn the Plug widget, articles are available in two places: the search bar and the Help section.\\n\\n**Search bar**\\n\\n![]()\\n\\n**Help section**\\n\\n![]()\\n\\nUsers can also view articles grouped into collections by visiting your help center hosted on your website. The visibility of collections and articles depends on the **Visible to** settings configured.\\n\\n[### Articles](/docs/product/articles)[###",
"title": "Knowledge Base | Computer for Support Teams | DevRev"
},
{
"id": "ART-15716_KNOWLEDGE_NODE-11",
"text": "Answers\\n\\nMake sure your articles are published and accessible to PluG, and that \\xe2\\x80\\x9cAI Answers\\xe2\\x80\\x9d is enabled in settings. It may take a few minutes for new articles to be indexed. Try reloading the widget or clearing cache. If it still doesn\\xe2\\x80\\x99t work, contact DevRev support.\\n\\nInstalling the PluG SDK\\n\\nFor web, you only need the JavaScript snippet. For mobile, check DevRev\\xe2\\x80\\x99s documentation for SDKs. For React Native, follow the release process and update",
"title": "Support queries related playbook"
},
{
"id": "ART-1985_KNOWLEDGE_NODE-35",
"text": "and no longer required can be removed by archiving them.\\n\\nVisibility settings\\n-------------------\\n\\n### Article visibility\\n\\nTo control who can view the articles, open the **Visible to** menu. This displays all external groups that the article can be shared with. By default, the following groups are available:\\n\\n* **Customers**: Allows public access without verification.\\n\\n ![]()\\n\\n Public access requires the public portal to be enabled. If the public portal is not enabled, only",
"title": "Articles | Knowledge Base | Computer for Support Teams | DevRev"
},
{
"id": "ART-4215_KNOWLEDGE_NODE-31",
"text": "pages, update the access manually:\\n\\n1. Go to **Notion Home**.\\n2. Click **Settings** (bottom-left panel).\\n3. Under **Accounts > Connections**, find the DevRev integration.\\n4. Click the menu (\\xe2\\x80\\xa2\\xe2\\x80\\xa2\\xe2\\x80\\xa2) > **Access selected pages**.\\n5. Select additional pages and **Save**.\\n\\nYou can use the same connection in DevRev to import more Notion pages.\\n\\n![]()\\n\\nWhen setting up a new connection for the same workspace, reselect all pages that were linked in the previous",
"title": "Notion AirSync | AirSync | Snap-ins | DevRev"
},
{
"id": "ART-2040_KNOWLEDGE_NODE-44",
"text": "will be added, and the article status will be switched to *draft*. While our converter supports Zendesk's native editor tags, we cannot guarantee compatibility with all user-added HTML, potentially resulting in rendering issues and disruptions to the editing experience.\\n* The ordering of articles and collections during the initial import and subsequent syncs is not assured. This is because of limitations in how Zendesk transmits positions in its response and how we internally store the rank of",
"title": "Zendesk AirSync | AirSync | Snap-ins | DevRev"
},
{
"id": "ART-1985_KNOWLEDGE_NODE-38",
"text": "and **Public Portal**.\\n\\n### Share an article\\n\\nOnce you've created an article, you have two options to share it:\\n\\n* Use **Copy external link** to share with your customers, allowing them to access the article directly.\\n* Use **Copy internal link** to share with your internal organizational team members.\\n\\nThe ability to view the article depends on the settings for **Visible to** and **Status** that have been configured.\\n\\n* If you are sharing an external link with non-signed-in",
"title": "Articles | Knowledge Base | Computer for Support Teams | DevRev"
},
{
"id": "ART-16263_KNOWLEDGE_NODE-34",
"text": "Token** \\xe2\\x80\\x93 the token you generated from Atlassian\\n7. After establishing the connection, select the Confluence spaces you want to import.\\n8. Map them to the appropriate DevRev parts.\\n9. Review the auto-configured field mappings and proceed through each screen.\\n10. Once the extraction is complete, view the report showing imported objects:\\n\\n * Pages\\n * Blogs\\n * Users\\n * Attachments\\n * Folders\\n\\nPost-import options\\n-------------------\\n\\nAfter a successful",
"title": "Confluence Datacenter AirSync | AirSync | Snap-ins | DevRev"
},
{
"id": "ART-1985_KNOWLEDGE_NODE-31",
"text": "verified customers.\\n4. Click **Create** and select whether you want to **Create** an article in draft mode, **Submit for review**, or **Publish**.\\n\\nTo ensure that the article is visible to your users, the **Status** of the article must be *Published* and the user group must be indicated in the **Visible to** field.\\n\\n### Edit article content and settings\\n\\nTo update the content or settings of an existing article, do the following:\\n\\n1. Go to [**Settings** > **Support** > **Knowledge",
"title": "Articles | Knowledge Base | Computer for Support Teams | DevRev"
}
] |
4972efdc-e74b-4022-8408-6b7b12fb218f
|
set stage or status of a ticket when a reminder expires
|
[
{
"id": "ART-2012_KNOWLEDGE_NODE-27",
"text": "will be created, and the previous ticket stage will remain unchanged.\\n\\n## Prerequisities\\n\\n * Before you install this snap-in, you need to set the **Stage** in closed state as a terminal stage or permanently closed stage. That is, once the ticket is moved to this stage, it cannot be reopened.\\n\\nNone of the default stages are terminal stages.\\n\\n * To create a new terminal stage, contact DevRev via the PLuG widget (chat bubble) on the bottom left of your home screen of the DevRev app. Just",
"title": "Follow-up ticket | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2012_KNOWLEDGE_NODE-24",
"text": "customer comments on permanently closed tickets. It allows you to configure the time after which a ticket stage should be marked as closed and creates a new follow-up ticket along with all the attachments and a custom message to let the customers know that the ticket is permanently closed automatically if required.\\n\\nFor more information, refer to the [Follow-up ticket snap-in](https://marketplace.devrev.ai/followup?) on the DevRev marketplace.\\n\\nLet\\xe2\\x80\\x99s say your ticket has the",
"title": "Follow-up ticket | Automate | Snap-ins | DevRev"
},
{
"id": "ART-12390_KNOWLEDGE_NODE-39",
"text": "to update * subtype: (Optional) Ticket subtype * apps: (Optional) Related apps * app\\\\_custom\\\\_fields: (Optional) Custom fields * stage: (Optional) New stage | Updated ticket object |\\n\\nObject links\\n------------\\n\\n| Operation | Description | Input Parameters | Output |\\n| --- | --- | --- | --- |\\n| LinkConversationWithTicket | Creates a link between a conversation and a ticket. | * source: Conversation ID * link\\\\_type: Type of link (usually \"is\\\\_related\\\\_to\") * target: Ticket ID | Empty",
"title": "Workflow action library | Workflows | Computer by DevRev | DevRev"
}
] |
a451837f-dfc9-45cf-89ef-13921a59bcbd
|
personal access token for API calls to DevRev
|
[
{
"id": "ART-1175_KNOWLEDGE_NODE-4",
"text": "a DevRev API must include a PAT. After you create your account, [generate a personal access token](/about/authentication) and store it in a safe place.\\n\\nIn this guide, you\\xe2\\x80\\x99ll make a call to the [`dev-users.self`](/api-reference/dev-users/self) API which gets the authenticated user\\xe2\\x80\\x99s information. You will retrieve the user object created for your account on DevRev. This user object contains information such as a unique identifier, full name, display name, and profile",
"title": "Getting started | DevRev | Docs"
},
{
"id": "ART-1371_KNOWLEDGE_NODE-4",
"text": "must include a PAT. After you create your account, [generate a personal access token](/public/about/authentication) and store it in a safe place.\\n\\nIn this guide, you\\xe2\\x80\\x99ll make a call to the [`dev-users.self`](/public/api-reference/dev-users/self) API which gets the authenticated user\\xe2\\x80\\x99s information. You will retrieve the user object created for your account on DevRev. This user object contains information such as a unique identifier, full name, display name, and profile",
"title": "Getting started — DevRev | Docs"
},
{
"id": "ART-1362_KNOWLEDGE_NODE-4",
"text": "customer). The application uses its own AAT to authenticate to the STS to obtain a session token for a customer and then uses that session token to access DevRev APIs. The lifetime of a session token is usually minutes. The subject of the session token is set to the DON of the corresponding customer (for example, `don:identity:dvrv-us-1:devo/0:revo/6:revu/131`).\\n\\n * **Personal Access Token (PAT)** : Uniquely identifies a dev user. A PAT can be used by external applications to access DevRev",
"title": "Authentication — DevRev | Docs"
},
{
"id": "ART-1362_KNOWLEDGE_NODE-7",
"text": "token is valid at [jwt.io](https://jwt.io/).\\n\\n## Generate a personal access token (PAT)\\n\\n 1. In the DevRev app, go to the relevant dev org.\\n 2. Go to **Settings** > **Account** > **Personal Access Token**.\\n 3. Click **New token** and follow the workflow to create your PAT.\\n\\n#####\\n\\nAs the token value isn\\xe2\\x80\\x99t retrievable later, using descriptive names for PATs is recommended as it can help you differentiate between multiple PATs.\\n\\n \\n\\n 1. Copy the PAT and store it",
"title": "Authentication — DevRev | Docs"
},
{
"id": "ART-1170_KNOWLEDGE_NODE-5",
"text": "DevRev APIs on behalf of the corresponding dev user. The lifetime of a PAT is usually in days. The subject of the PAT is set to the corresponding dev users DON (for example, `don:identity:dvrv-us-1:devo/0:devu/30`).\\n\\nPersonal access token usage\\n---------------------------\\n\\nAuthentication to DevRev APIs requires a personal access token (PAT). A PAT is used to uniquely identify a dev user in context of a dev org and can be used by external third-party applications to access DevRev APIs on",
"title": "Authentication | DevRev | Docs"
},
{
"id": "ART-1312_KNOWLEDGE_NODE-0",
"text": "b'\\xf0\\x9f\\x91\\x89 Getting started\\nIf you are new to DevRev, we would recommend learning about our core concepts before getting started.\\nOnce you have a DevRev account, you can access the APIs with a personal access token (PAT) that you create in the DevRev app.\\nA brief tutorial shows you how to access the APIs.\\n\\xf0\\x9f\\xa7\\xac Methods\\nSpecifications covering the supported APIs are based on OpenAPI Specification 3.0. You can download the specs to use an OpenAPI 3.0-compliant tool to",
"title": "For Developers – DevRev | Docs"
},
{
"id": "ART-1362_KNOWLEDGE_NODE-5",
"text": "APIs on behalf of the corresponding dev user. The lifetime of a PAT is usually in days. The subject of the PAT is set to the corresponding dev users DON (for example, `don:identity:dvrv-us-1:devo/0:devu/30`).\\n\\n## Personal access token usage\\n\\nAuthentication to DevRev APIs requires a personal access token (PAT). A PAT is used to uniquely identify a dev user in context of a dev org and can be used by external third-party applications to access DevRev APIs on behalf of the corresponding dev",
"title": "Authentication — DevRev | Docs"
},
{
"id": "ART-1170_KNOWLEDGE_NODE-4",
"text": "customer (or customer). The application uses its own AAT to authenticate to the STS to obtain a session token for a customer and then uses that session token to access DevRev APIs. The lifetime of a session token is usually minutes. The subject of the session token is set to the DON of the corresponding customer (for example, `don:identity:dvrv-us-1:devo/0:revo/6:revu/131`).\\n* **Personal Access Token (PAT)**: Uniquely identifies a dev user. A PAT can be used by external applications to access",
"title": "Authentication | DevRev | Docs"
},
{
"id": "ART-1371_KNOWLEDGE_NODE-3",
"text": "find your newly created org in **Orgs**.\\n\\nLogin into your demo org and [obtain the PAT token](/public/about/authentication#generate-a-personal-access-token-pat). Now you can use this PAT token to make test API calls and try building something new.\\n\\nIn this tutorial, you will be able to retrive your account information by using the `dev-users` API. Let\\xe2\\x80\\x99s get started with DevRev APIs.\\n\\n## Prerequisites\\n\\nFirst, create a DevRev account or log in.\\n\\nEvery call to a DevRev API",
"title": "Getting started — DevRev | Docs"
},
{
"id": "ART-1366_KNOWLEDGE_NODE-2",
"text": "Developers\\n\\n## \\xf0\\x9f\\x91\\x89 Getting started\\n\\nIf you are new to DevRev, we would recommend learning about our [core concepts](https://docs.devrev.ai/intro) before getting started.\\n\\nOnce you have a DevRev account, you can access the APIs with a [personal access token](/public/about/authentication) (PAT) that you create in the DevRev app.\\n\\nA brief [tutorial](/public/api-reference/getting-started) shows you how to access the APIs.\\n\\n## \\xf0\\x9f\\xa7\\xac Methods\\n\\nSpecifications",
"title": "For Developers — DevRev | Docs"
},
{
"id": "ART-1299_KNOWLEDGE_NODE-0",
"text": "b'Beta\\nOn this page\\n\\n\\xf0\\x9f\\x91\\x89 Getting started \\xf0\\x9f\\xa7\\xac Methods \\xf0\\x9f\\xa7\\xa9 Snap-ins \\xf0\\x9f\\x92\\xbb SDKs\\n\\nAbout For Developers.\\n\\n\\xf0\\x9f\\x91\\x89 Getting started.\\n\\nIf you are new to DevRev, we would recommend learning about our core concepts before getting started.\\n\\nOnce you have a DevRev account, you can access the APIs with a personal access token (PAT) that you create in the DevRev app.\\n\\nA brief tutorial shows you how to access the APIs.\\n\\n\\xf0\\x9f\\xa7\\xac",
"title": "For Developers — DevRev | Docs"
},
{
"id": "ART-1170_KNOWLEDGE_NODE-7",
"text": "error, you can check whether the token is valid at [jwt.io](https://jwt.io/).\\n\\nGenerate a personal access token (PAT)\\n--------------------------------------\\n\\n1. In the DevRev app, go to the relevant dev org.\\n2. Go to **Settings** > **Account** > **Personal Access Token**.\\n3. Click **New token** and follow the workflow to create your PAT.\\n\\n![]()\\n\\n##### \\n\\nAs the token value isn\\xe2\\x80\\x99t retrievable later, using descriptive names for PATs is recommended as it can help you",
"title": "Authentication | DevRev | Docs"
},
{
"id": "ART-1175_KNOWLEDGE_NODE-3",
"text": "can find your newly created org in **Orgs**.\\n\\nLogin into your demo org and [obtain the PAT token](/about/authentication#generate-a-personal-access-token-pat).\\nNow you can use this PAT token to make test API calls and try building something new.\\n\\nIn this tutorial, you will be able to retrive your account information by using the `dev-users` API. Let\\xe2\\x80\\x99s get started\\xc2\\xa0with DevRev APIs.\\n\\nPrerequisites\\n-------------\\n\\nFirst, create a DevRev account or log in.\\n\\nEvery call to",
"title": "Getting started | DevRev | Docs"
},
{
"id": "ART-1353_KNOWLEDGE_NODE-1",
"text": "[Mobile](/about/for-developers#mobile)\\n\\n[About](/about/for-developers)\\n\\nFor Developers\\n==============\\n\\nCopy page\\n\\n\\xf0\\x9f\\x91\\x89 Getting started\\n-----------------\\n\\nIf you are new to DevRev, we would recommend learning about our [core concepts](https://docs.devrev.ai/intro) before getting started.\\n\\nOnce you have a DevRev account, you can access the APIs with a [personal access token](/about/authentication) (PAT) that you create in the DevRev app.\\n\\nA brief",
"title": "For Developers | DevRev | Docs"
},
{
"id": "ART-16579_KNOWLEDGE_NODE-12",
"text": "replace the `<AAT>` and `<YOUR_USER_ID>` with the actual values.\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl \\\\ |\\n| > | --location \\'https://api.devrev.ai/auth-tokens.create\\' \\\\ |\\n| > | --header \\'accept: application/json, text/plain, */*\\' \\\\ |\\n| > | --header \\'content-type: application/json\\' \\\\ |\\n| > | --header \\'authorization: <AAT>\\' \\\\ |\\n| > | --data \\'{ |\\n| > | \"rev_info\": { |\\n| > | \"user_ref\": \"<YOUR_USER_ID>\" |\\n| > | } |\\n| > | }\\' |\\n```\\n\\nThe response of the API call",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-1371_KNOWLEDGE_NODE-6",
"text": "issues.\\n\\nNext, you\\xe2\\x80\\x99ll want to set up your development environment to connect and interact with the DevRev API.\\n\\n## Send your first API request\\n\\nTo do this, make a GET request to the DevRev server (\\xe2\\x80\\x9c<https://api.devrev.ai/dev-users.self>[](https://api.devrev.ai/dev-users.self)\\xe2\\x80\\x9d) and include the PAT created in the authorization header of the request.\\n\\nThis guide shows you how to get user information with a GET request using two popular languages as well as",
"title": "Getting started — DevRev | Docs"
},
{
"id": "ART-1175_KNOWLEDGE_NODE-6",
"text": "issues.\\n\\n![]()\\n\\nNext, you\\xe2\\x80\\x99ll want to set up your development environment to connect and interact with the DevRev API.\\n\\nSend your first API request\\n---------------------------\\n\\nTo do this, make a GET request to the DevRev server (\\xe2\\x80\\x9c<https://api.devrev.ai/dev-users.self>\\xe2\\x80\\x9d) and include the PAT created in the authorization header of the request.\\n\\nThis guide shows you how to get user information with a GET request using two popular languages as well as",
"title": "Getting started | DevRev | Docs"
},
{
"id": "ART-1170_KNOWLEDGE_NODE-6",
"text": "behalf of the corresponding dev user. A PAT has the same set of privileges that the owner of the PAT has on the DevRev platform.\\nYou can set the validity duration of a PAT. You can\\xe2\\x80\\x99t renew a PAT; you can only create a new PAT and update your code to use it.\\nFor example, a VS Code plugin that pulls issues from the DevRev platform pertaining to a particular dev user needs to rely on that user\\xe2\\x80\\x99s PAT to authenticate the DevRev APIs.\\nIf you are receiving an `invalid token`",
"title": "Authentication | DevRev | Docs"
},
{
"id": "ART-1362_KNOWLEDGE_NODE-6",
"text": "user. A PAT has the same set of privileges that the owner of the PAT has on the DevRev platform. You can set the validity duration of a PAT. You can\\xe2\\x80\\x99t renew a PAT; you can only create a new PAT and update your code to use it. For example, a VS Code plugin that pulls issues from the DevRev platform pertaining to a particular dev user needs to rely on that user\\xe2\\x80\\x99s PAT to authenticate the DevRev APIs. If you are receiving an `invalid token` error, you can check whether the",
"title": "Authentication — DevRev | Docs"
},
{
"id": "ART-1170_KNOWLEDGE_NODE-8",
"text": "differentiate between multiple PATs.\\n\\n \\n\\n1. Copy the PAT and store it securely. Once you go to another page, you can\\xe2\\x80\\x99t retrieve this PAT again.\\n\\nRevoke a personal access token\\n------------------------------\\n\\n##### \\n\\nOnce a PAT is revoked, it can\\xe2\\x80\\x99t be restored. Never share tokens with other users or applications. Do not publish tokens in public code repositories.\\n\\n1. In the DevRev app, go to the relevant dev org.\\n2. Go to **Settings** > **Account** >",
"title": "Authentication | DevRev | Docs"
},
{
"id": "ART-16803_KNOWLEDGE_NODE-29",
"text": "**Account**](https://app.devrev.ai/?setting=account) and create a **New token** under **Personal Access Tokens**. Add the token here to create a new connection.\\n3. Enter the **URL endpoint** where you want to send or fetch data. The URL can be static or dynamically built using reference outputs from previous steps.\\n4. Select the **HTTP request method**: GET, POST, PUT, or DELETE.\\n5. Configure the **authentication type** for the request.\\n6. Add any required **headers**. Headers carry",
"title": "Workflow nodes | Workflows | Computer by DevRev | DevRev"
},
{
"id": "ART-1175_KNOWLEDGE_NODE-7",
"text": "cURL:\\n\\n### Making a GET request\\n\\ncURLPythonNode JS\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl --location --request GET \\'https://api.devrev.ai/dev-users.self\\' \\\\ |\\n| > | --header \\'Authorization: Bearer <PAT>\\' |\\n```\\n\\nIf everything works, the command line displays the following response for a user named \\xe2\\x80\\x9cJohn Smith Doe\\xe2\\x80\\x9d:\\n\\nResponse\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"dev_user\": { |\\n| 3 | \"display_handle\": \"John Doe\", |\\n| 4 | \"created_date\":",
"title": "Getting started | DevRev | Docs"
},
{
"id": "ART-2046_KNOWLEDGE_NODE-27",
"text": "update the app by navigating to **Apps** > **Manage apps** > **DevRev for Jira**. DevRev will notify administrators of major updates.\\n\\nConfiguration\\n-------------\\n\\nTo configure the app go to **Apps** > **Manage Apps** > **DevRev for Jira**.\\n\\n![]()\\n\\n1. Go to the DevRev app and retrieve the platform access token by clicking **Settings** > **Account** > **New token**.\\n2. Copy both the token and its corresponding token name. Paste them into the appropriate input fields within the app",
"title": "DevRev for Jira app | Jira Software AirSync | AirSync | Snap-ins | DevRev"
}
] |
0db0e70f-0e7a-4272-a95f-d500623a0be2
|
bug conversation turned into ticket ticket message missing conversation ID
|
[
{
"id": "ART-12390_KNOWLEDGE_NODE-39",
"text": "to update * subtype: (Optional) Ticket subtype * apps: (Optional) Related apps * app\\\\_custom\\\\_fields: (Optional) Custom fields * stage: (Optional) New stage | Updated ticket object |\\n\\nObject links\\n------------\\n\\n| Operation | Description | Input Parameters | Output |\\n| --- | --- | --- | --- |\\n| LinkConversationWithTicket | Creates a link between a conversation and a ticket. | * source: Conversation ID * link\\\\_type: Type of link (usually \"is\\\\_related\\\\_to\") * target: Ticket ID | Empty",
"title": "Workflow action library | Workflows | Computer by DevRev | DevRev"
}
] |
211344fe-b4ea-4069-87cf-85bbe4022bca
|
client not receiving messages sent via DevRev but ticket shows delivered
|
[
{
"id": "ART-2027_KNOWLEDGE_NODE-33",
"text": "Transit*: This email is now queued for outbound. DevRev is attempting to send this email, and the process is currently in progress.\\n* *Sent*: DevRev has successfully sent this email. At this point, the email is *on its way* to the intended recipient.\\n* *Delivered*: DevRev has successfully delivered this email to the recipient's email server.\\n\\n ![]()\\n\\n Even if DevRev delivers the email, the recipient's email server may quarantine the email, or it may end up in the recipient's junk or",
"title": "Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-3207_KNOWLEDGE_NODE-55",
"text": "test email to your configured address from the deliverability tool and confirm that a conversation or ticket is created.\\n2. Respond from the test conversation or ticket in DevRev to the address mentioned in the deliverability check tool.\\n\\nYou need to add the address as a contact, which can be done in the email composer page.\\n\\n1. Check the status of the email sent by coming back to the chosen tool.\\n\\nIf the **DMARC Compliance checks** on the tool pass, then DevRev email is",
"title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2027_KNOWLEDGE_NODE-34",
"text": "spam folder. Despite this, DevRev still registers a *Delivered* event, as the email has reached the intended recipient's server.\\n* *Bounce*: The recipient's email server rejects the message, which can happen for several reasons. These may include the email address no longer existing, a typo in the address, or the email failing to meet the recipient server's security policies. The specific reason for the bounce is detailed in the Bounced event. The sender is notified whenever their email",
"title": "Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2027_KNOWLEDGE_NODE-29",
"text": "your communication requirements.\\n\\nThe visibility and interaction capabilities with a ticket in DevRev are determined by the user's role and how they were added to the email thread.\\n\\nEnd users\\n\\n* Original sender\\n\\n *Added to:* **Reported by** or **Email members** field.\\n\\n *Is able to:* View the ticket on the portal and reply via email.\\n* An end user in the same organization\\n\\n *Added to:* **To** or **CC** fields in the email thread; **Reported by** field, **Email members** field,",
"title": "Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-15515_KNOWLEDGE_NODE-43",
"text": "configure your app to receive push notifications from the DevRev SDK. The SDK is designed to handle push notifications and execute actions based on the notification\\xe2\\x80\\x99s content.\\n\\nThe DevRev backend sends push notifications to your app to notify users about new messages in the Plug support chat.\\n\\n### Configuration\\n\\nTo receive push notifications, you need to configure your DevRev organization by following the instructions in the [push notifications](/sdks/push-notifications)",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-12460_KNOWLEDGE_NODE-27",
"text": "12| const messageJson = notificationPayload[\"message\"]; \\n 13| \\n 14| DevRev.processPushNotification(messageJson, function() { \\n 15| \\tconsole.log(\"Push notification processed successfully.\"); \\n 16| }, function(error) { \\n 17| \\tconsole.error(\"Failed to process push notification:\", error); \\n 18| });\\n[/code] \\n \\n#### iOS\\n\\nOn iOS devices, you must pass the received push notification payload to the DevRev SDK for processing. The SDK will then handle the",
"title": "Features — DevRev | Docs"
},
{
"id": "ART-1471_KNOWLEDGE_NODE-1",
"text": "timeline of an object by using the `timeline-entries-create` API. These messages are only visible to the specific users you give access to.\\n\\nThe [timeline entries](/public/api-reference/timeline-entries/create) API is used to create discussions (comments) on the timeline of an object such as a ticket or issue. These messages can be sent by users or by a bot. You can use this to send any information about a customer like their last logged in date and time, the last page they visited, or an",
"title": "Restricted messages on a timeline — DevRev | Docs"
},
{
"id": "ART-1265_KNOWLEDGE_NODE-8",
"text": "\"don:core:dvrv-us-1:devo/<dev-org-id>:conversation/172:comment/xqsvvdwvt6hjw\", |\\n| 17 | \"object\": \"don:core:dvrv-us-1:devo/<dev-org-id>:conversation/172\", |\\n| 18 | \"object_type\": \"conversation\", |\\n| 19 | \"visibility\": \"private\" |\\n| 20 | } |\\n| 21 | } |\\n```\\n\\nYou can check the object to which you sent a message in the UI. It\\xe2\\x80\\x99s visible to the creator and the users you added in `private_to`.\\n![]()\\n\\nSummary\\n-------\\n\\nIn this tutorial, you learned how to post a comment on the",
"title": "Restricted messages on a timeline | DevRev | Docs"
},
{
"id": "ART-12460_KNOWLEDGE_NODE-23",
"text": "require SDK configuration and user identification, whether unverified or anonymous, to ensure delivery to the correct user.\\n\\nThe DevRev SDK offers a method to register your device for receiving push notifications. You can register for push notifications using the following method:\\n\\n[code]\\n\\n 1| DevRev.registerDeviceToken(deviceToken, deviceID, successCallback, errorCallback) \\n ---|---\\n[/code] \\n \\nOn Android devices, the `deviceToken` should be the Firebase Cloud Messaging (FCM)",
"title": "Features — DevRev | Docs"
}
] |
f1f137f9-775d-40e0-90c2-034bffbad0b1
|
how to close a ticket
|
[
{
"id": "ART-1979_KNOWLEDGE_NODE-47",
"text": "validate the fix with the user and then to *resolved*. If the user wants to cancel the ticket then the stage moves to *canceled*.\\n\\n**Closed**\\n\\n* *Canceled* (C)\\n\\n The ticket is determined to be invalid either by the user or the customer experience engineer. In certain scenarios, a ticket may have been created by accident and may be canceled by the creator. In other scenarios, garbage tickets may be created through automation or because of spam. Automation or the customer experience",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-1480_KNOWLEDGE_NODE-1",
"text": "follows:\\n\\n[code]\\n\\n 1| commands: \\n ---|--- \\n 2| - name: close \\n 3| namespace: devrev \\n 4| description: Closes the issue and all of its children issues. \\n 5| surfaces: \\n 6| - surface: discussions \\n 7| object_types: \\n 8| - issue \\n 9| usage_hint: \"[text]\" \\n 10| function: close_issue\\n[/code] \\n \\nThe description of the command\\xe2\\x80\\x99s fields is as follows:\\n\\n * `name`: This is the name of",
"title": "Commands — DevRev | Docs"
}
] |
9c065cf8-1f01-42f4-bdf0-ab30645692ce
|
how to escalate the ticket
|
[
{
"id": "ART-1981_KNOWLEDGE_NODE-28",
"text": "new conversation. Respond within 1 hour to new messages on existing conversations. Change the stage of conversation to *awaiting customer response* as soon as you have responded.\\n* In **Updates**, filter by **Type** > **Mentioned**. Respond to those updates first.\\n* Create a ticket if you aren't able to resolve the conversation in 20 minutes. As soon as the ticket is opened, move it to the *escalate* stage. The owner of the ticket is the owner of the customer org where the conversation",
"title": "Support best practices | Computer for Support Teams | DevRev"
},
{
"id": "ART-985_KNOWLEDGE_NODE-10",
"text": "ServiceCloud, etc.)\\n SRE 1 works with customer to get logs, context, etc. and appends to ticket\\n SRE 1 escalates to engineering on-call by creating an on-call in engineering work system (e.g JIRA)\\n Engineer 1 may not have access to support system as they are commonly licensed on a per-seat basis\\n Engineer 1 asks support to send over detail/context about ticket and customer and attach to on-call\\n Support sends or attaches detail to the on-call\\n Now, say another customer has the same",
"title": "Why Silos Must be Busted"
},
{
"id": "ART-4172_KNOWLEDGE_NODE-14",
"text": "([www.support.DevRev.ai](http://www.support.devrev.ai/))\\n\\nNOTE: Chat is our fastest response channel\\n\\n### 4. Incident communication Protocols:\\n\\n**DevRev Status Page**: <https://status.devrev.ai/>\\n\\nDevRev maintains a services status page that can be referenced for DevRev current status, updates, maintenance information, and performance incidents (current and past).\\n\\n### 5. Escalation:\\n\\nCustomers can directly escalate their own reported problem (ticket) from the DevRev Customer Portal",
"title": "DevRev Service Level Agreement"
},
{
"id": "ART-15643_KNOWLEDGE_NODE-6",
"text": "support ticket from a high-value opportunity comes in, an agent can analyze it, recognize the deal's importance, and suggest escalating the ticket's priority - an action you can approve with a single click.\\n\\nDevRev is different in three fundamental ways:\\n\\nFirst, most AI companies focus only on unstructured data: your documents and conversations. But DevRev is the only platform in the world today that combines your structured data \\xe2\\x80\\x93 like your CRM, product backlogs, or support",
"title": "DevRev Corp Narrative - for PLuG on website"
},
{
"id": "ART-1974_KNOWLEDGE_NODE-32",
"text": "have been completed the stage transitions to *needs response* to bring to the customer experience engineer's attention. Upon review they may put the conversation back on *hold* to re-escalate the item. If the dependencies seem to be resolved the customer experience engineer responds to the customer and the stage transitions to *waiting on user*.\\n\\n**Closed**\\n\\n* *Resolved* (R)\\n\\n The final target stage for conversations. It means that the customer's concerns which led to the conversation",
"title": "Conversations | Computer for Support Teams | DevRev"
}
] |
a8bafc78-f578-44c3-b755-f7b1712d9cd5
|
Send email operation is not enabled for this organization
|
[
{
"id": "ART-3207_KNOWLEDGE_NODE-41",
"text": "to send emails | This is required if workflows or bots are configured to send emails. Keep it enabled unless you intend to turn it off. |\\n\\n### Step 6: Auto-Reply & Threading Features\\n\\nYou can configure DevRev to send automatic responses when new emails are received:\\n\\n* **Auto-reply message**: Acknowledge new requests and provide links or resources.\\n* **Send auto-reply message to**: Choose recipients such as, only customers.\\n\\n> You can include links to help docs, response times, or",
"title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-3207_KNOWLEDGE_NODE-29",
"text": "to send emails to the group and is a member of the group and continue.\\n5. In your Gmail account, go to **Settings** > **Accounts and Import** > **Send mail as** and add your group address.\\n6. Grant DevRev additional access to your Google account. Refer to our [privacy policy](/privacy-policy) for more information.\\n\\nEmail connection\\n\\n1. In DevRev app, go to **Integrations** > **Snap-ins** and click **Connections**.\\n2. In the top-right corner, select **+ Connection**, choose **Email",
"title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-4020_KNOWLEDGE_NODE-24",
"text": "[Documentation](/docs)\\n3. [Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Send customized emails](/docs/automations/send-emails)\\n\\nSend customized emails\\n======================\\n\\nThe [**send customized emails**](https://marketplace.devrev.ai/marketplace/send-emails) snap-in automates email sending. Once activated, this operation becomes available in the Workflow builder, enabling the delivery of personalized messages.\\n\\nConfiguration\\n-------------\\n\\n1. Create a **SendGrid**",
"title": "Send customized emails | Automate | Snap-ins | DevRev"
},
{
"id": "ART-3207_KNOWLEDGE_NODE-34",
"text": "Configure email integration snap-in\\n--------------------------------------\\n\\n1. Go to **Settings** > **Snap-ins**. In the top-right corner, click **Explore Marketplace**.\\n2. Scroll down the page to find the **Email Integration** snap-in and click **Install**.\\n3. In the **Connections** tab, select the connection that you created. You could [create a new connection](#1-create-a-new-connection) here as well.\\n4. Select the options and inputs suitable for your organization in the",
"title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-1953_KNOWLEDGE_NODE-27",
"text": "conversation, ensuring seamless and continuous communication.\\n\\nBy default, notifications are sent from [[email protected]](mailto:[email protected]). However, this setting can be overridden to use the organization\\xe2\\x80\\x99s primary email address as the sender, or notifications can be turned off entirely.\\n\\nTo configure the notifications setting, under [**Settings** > **Snap-ins** > **Email Integration**](https://app.devrev.ai/devrev/settings/snap-ins/email-with-tickets), go to",
"title": "Customer email notifications | Computer by DevRev | DevRev"
},
{
"id": "ART-4020_KNOWLEDGE_NODE-25",
"text": "account.\\n2. Generate an **API key**.\\n3. Create a SendGrid connection:\\n a. Go to **Settings** > **Snap-ins** > **+ Connection**\\n b. Select **SendGrid**.\\n c. Add the **API key** and click **Save**.\\n\\nInstallation\\n------------\\n\\n1. Install the [**send customized emails**](https://marketplace.devrev.ai/marketplace/send-emails) from the DevRev marketplace.\\n2. Open the Workflow Builder and locate the **send customized emails** action node.\\n3. Configure the node by selecting the",
"title": "Send customized emails | Automate | Snap-ins | DevRev"
},
{
"id": "ART-3207_KNOWLEDGE_NODE-28",
"text": "In the top-right corner, select **+ Connection**, choose Google, and enter your connection name and domain name.\\n3. Toggle on **Make public** to make the connection public for your organization and click **Next**.\\n4. Click **Sign in with Google** and add your organization\\xe2\\x80\\x99s Gmail account. If you are already logged in using a different Gmail account select **Use another account** and continue.\\n\\n If you are using Google Groups then use the same Gmail account which has permission",
"title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev"
}
] |
88bc3384-574f-4f7d-a1c7-9e71cdbda5a7
|
attach log file to ticket
|
[
{
"id": "ART-1979_KNOWLEDGE_NODE-38",
"text": "the top-right corner of your screen.\\n3. Add a title and description for your new ticket. You can also attach files related to the ticket in the description.\\n4. Select which part of the company/product this ticket is related to.\\n\\n ![]()\\n5. Enter other attributes for the ticket: change the assignee or accept the default; enter the severity; add any relevant tags to help employees identify any relevant traits of the ticket; select the workspace that the ticket pertains to.\\n6. If there are",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-15716_KNOWLEDGE_NODE-6",
"text": "and reporter), attach files if needed, and submit.\\n\\nFull instructions:\\xc2\\xa0[How to file a new ticket](https://devrev.ai/docs/product/tickets#create-a-ticket)\\n\\n3. Customizing Stages for IssuesYou can customise issue stages by updating the stage diagram by going to settings -> Customisation -> Stage customisation. Else you can use the API to customise the stages for issues.\\n\\n[API Doc](https://developer.devrev.ai/public/api-reference/customization/stage-diagrams-update)\\n\\n4. Creating",
"title": "Support queries related playbook"
},
{
"id": "ART-2027_KNOWLEDGE_NODE-42",
"text": "commands. These can be configured under **Settings > Commands.** |\\n| Attach Files | Attachment icon | Upload files up to 25MB. Optionally shared as links to avoid email rejections. |\\n\\n> If a user doesn\\xe2\\x80\\x99t belong to the organization or is deleted, ensure to remove them from the **Reported By** field to avoid delivery errors.\\n\\n### Email Bounce Prevention Tip\\n\\nIf an email fails to deliver, it may be due to:\\n\\n* A deleted user listed as a reporter\\n* Invalid or unverified",
"title": "Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-1992_KNOWLEDGE_NODE-31",
"text": "on the top right corner of your screen.\\n3. Add a title and description for your new issue. You can also attach files related to the issue in the description.\\n4. Select which part of the company/product this issue is related to.\\n\\n ![]()\\n5. Enter other attributes for the issue: change the assignee or accept the default; enter the severity; add any relevant tags to help employees identify any relevant traits of the issue; select the workspace that the issue pertains to.\\n6. If there are",
"title": "Issues | Computer for Builders | DevRev"
}
] |
8784f283-1b4f-426f-83fa-30068169f471
|
how to create a ticket
|
[
{
"id": "ART-6174_KNOWLEDGE_NODE-28",
"text": "tickets\\n--------------------------------\\n\\n**Manual conversion**\\n\\nGo to the conversation record pane and select **Convert to Ticket** to create a new ticket from the conversation.\\n\\n![]()\\n\\n**Automated conversion via workflows**\\n\\nSet up automated [workflows](./workflow-engine) to convert conversations to tickets based on specific triggers:\\n\\n* When a conversation meets defined criteria\\n* When the AI agent identifies an issue requiring escalation\\n* According to custom business",
"title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev"
},
{
"id": "ART-1979_KNOWLEDGE_NODE-38",
"text": "the top-right corner of your screen.\\n3. Add a title and description for your new ticket. You can also attach files related to the ticket in the description.\\n4. Select which part of the company/product this ticket is related to.\\n\\n ![]()\\n5. Enter other attributes for the ticket: change the assignee or accept the default; enter the severity; add any relevant tags to help employees identify any relevant traits of the ticket; select the workspace that the ticket pertains to.\\n6. If there are",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-1979_KNOWLEDGE_NODE-64",
"text": "internal tickets.\\n\\nTo create an internal ticket, click the **Create Ticket** button. At the bottom of the ticket creation panel, click the dropdown menu on **Create external ticket** and select **Create internal ticket**.\\n\\nYou can convert an internal ticket to an external ticket by clicking **Convert to External** within the **Customer Messages** tab. Once a ticket is converted to external, it cannot be reverted back to internal.\\n\\n[PreviousConversation to ticket",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-1483_KNOWLEDGE_NODE-21",
"text": "devrevSDK.worksCreate({ \\n 17| title: ticketName, \\n 18| body: ticketBody, \\n 19| // The ticket is created in the PROD-1 part. Rename this to match your part. \\n 20| applies_to_part: \"PROD-1\", \\n 21| // The ticket is owned by the DEVU-1 user. Rename this to match the required user. \\n 22| owned_by: [\"DEVU-1\"], \\n 23| type: publicSDK.WorkType.Ticket, \\n 24| }); \\n 25| \\n 26| console.log(response); \\n",
"title": "Using a snap-in to perform a DevRev action — DevRev | Docs"
},
{
"id": "ART-1275_KNOWLEDGE_NODE-18",
"text": "= `Ticket created at ${date.toLocaleString()}`; |\\n| 14 | const ticketBody = `This ticket was created by a snap-in at ${date.toLocaleString()}`; |\\n| 15 | |\\n| 16 | const response = await devrevSDK.worksCreate({ |\\n| 17 | title: ticketName, |\\n| 18 | body: ticketBody, |\\n| 19 | // The ticket is created in the PROD-1 part. Rename this to match your part. |\\n| 20 | applies_to_part: \"PROD-1\", |\\n| 21 | // The ticket is owned by the DEVU-1 user. Rename this to match the required user. |\\n| 22 |",
"title": "Using a snap-in to perform a DevRev action | DevRev | Docs"
},
{
"id": "ART-15716_KNOWLEDGE_NODE-5",
"text": "ticket, selecting the merge option, and choosing the duplicate tickets to merge. Only unclosed tickets with the same reporters can be merged. After merging, duplicate tickets are archived, and all future messages go to the primary ticket.\\n\\nStep-by-step guide:\\xc2\\xa0[How to merge tickets](https://devrev.ai/docs/product/tickets#merging-guidelines)\\n\\n2. Creating Tickets in DevRevYou can create tickets from the app, support portal, Slack, or via API. Fill in required fields (like title, part,",
"title": "Support queries related playbook"
},
{
"id": "ART-1978_KNOWLEDGE_NODE-28",
"text": "eliminating the need for scattered email chains.\\n* **Improved collaboration**: Customer admins can access and manage tickets from their team, enabling seamless collaboration and knowledge sharing.\\n\\nFeatures\\n--------\\n\\n### Ticket creation, tracking, and team collaboration\\n\\n* Customers can create tickets with relevant details, such as issue description, priority, and category.\\n + To create a ticket, go to **+ Ticket**. Enter a title and description for the ticket and click **Submit**.\\n*",
"title": "Customer portal | Computer for Support Teams | DevRev"
},
{
"id": "ART-1979_KNOWLEDGE_NODE-37",
"text": "filters and **Group** conditions across various vistas in DevRev to track specific work, capacity, and more.\\n\\nYou can add custom attributes to tickets to track additional information. For more information on custom attributes, see [object customization](./object-customization).\\n\\nIssues are attached to tickets in order to track efforts with product priorities.\\n\\nCreate a ticket\\n---------------\\n\\n1. Go to **Support** > **Tickets** from the sidebar on the left.\\n2. Click **New Ticket** on",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-1947_KNOWLEDGE_NODE-37",
"text": "Ticket | Open the issue and click **Tickets > + Link tickets**. Either create a new ticket or select an existing ticket. |\\n| Issue \\xe2\\x86\\x92 Issue | Open the issue and click **Issues > + Link issues**. Either create a new issue or select an existing issue. |\\n\\n| Conversation | Ticket | Issue |\\n| --- | --- | --- |\\n| | | > |\\n\\nTo delete a ticket or issue, select the work item in the list view and click the **Delete** icon in the taskbar that appears.\\n\\n![]()\\n\\n[PreviousCore",
"title": "Apps | Computer by DevRev | DevRev"
},
{
"id": "ART-12390_KNOWLEDGE_NODE-29",
"text": "Ticket | Creates a new ticket in DevRev. | * Ticket details like title, body, applies\\\\_to\\\\_part, etc. * subtype: (Optional) Ticket subtype * apps: (Optional) Related apps * app\\\\_custom\\\\_fields: (Optional) Custom fields | Created ticket object |\\n| Convert Conversation To Ticket | Converts a conversation to a ticket. | * conversation\\\\_id: ID of the conversation to convert | ticket\\\\_id: ID of the created ticket |\\n\\nObject retrieval\\n----------------\\n\\n| Operation | Description | Input",
"title": "Workflow action library | Workflows | Computer by DevRev | DevRev"
},
{
"id": "ART-15716_KNOWLEDGE_NODE-6",
"text": "and reporter), attach files if needed, and submit.\\n\\nFull instructions:\\xc2\\xa0[How to file a new ticket](https://devrev.ai/docs/product/tickets#create-a-ticket)\\n\\n3. Customizing Stages for IssuesYou can customise issue stages by updating the stage diagram by going to settings -> Customisation -> Stage customisation. Else you can use the API to customise the stages for issues.\\n\\n[API Doc](https://developer.devrev.ai/public/api-reference/customization/stage-diagrams-update)\\n\\n4. Creating",
"title": "Support queries related playbook"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-37",
"text": "synchronized between DevRev and Slack.\\n\\nWork management using Slack\\n---------------------------\\n\\n### DevRev Tickets and Slack\\n\\nThe Slack snap-in allows users to create tickets directly from Slack. There are multiple ways to initiate ticket creation from any channel:\\n\\n* **Use the command:** Run /devrev create-ticket.\\n* **Message action:** Select **Create a new ticket** from the message actions.\\n* **Convert a Conversation:** Transform an ongoing conversation into a ticket. This is",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2046_KNOWLEDGE_NODE-29",
"text": "Ticket** button to create a ticket in DevRev by filling necessary attributes. You can turn this feature off in the app configuration if you want.\\n* To view comments on the tickets linked to the discussions that support teams had with customers or internally on DevRev, head over to the DevRev activity tab which is present in the same line as the **Comments** tab of Jira.\\n* To send comments from the Jira issue to the DevRev ticket, select the ticket from the dropdown, type in the comment, and",
"title": "DevRev for Jira app | Jira Software AirSync | AirSync | Snap-ins | DevRev"
},
{
"id": "ART-15716_KNOWLEDGE_NODE-7",
"text": "Tickets from Chat ConversationsYes, you can create a ticket from a conversation without leaving the chat. Some fields may be prefilled from the conversation.\\n\\nDetails:\\xc2\\xa0[Conv \\xe2\\x86\\x92 Ticket Creation](https://devrev.ai/docs/product/conversation-ticket)\\n\\n5. Viewing Ticket Activity to Avoid Duplicate Responses\\n\\nCurrently, there\\xe2\\x80\\x99s no direct feature to see who is viewing a ticket in real time. But, we can see if someone is typing on a ticket.\\n\\n6. Generating AI Summaries",
"title": "Support queries related playbook"
},
{
"id": "ART-4271_KNOWLEDGE_NODE-26",
"text": "conversation metadata including: \\n * Source channel\\n * Customer account information\\n * External members added as **reported by** on the ticket\\n * An AI-generated ticket title and description based on customer messages.\\n\\n### How to convert Conversations to Tickets\\n\\n**Manual Conversion**\\n\\nTo manually convert a conversation to a ticket:\\n\\n 1. Open the conversation record pane view.\\n 2. Click **Convert to Ticket** to initiate the conversion.\\n\\n**Automated Conversion",
"title": "Convert Conversations to Tickets | Conversations | Support | DevRev"
},
{
"id": "ART-1947_KNOWLEDGE_NODE-36",
"text": "Conversations can be immediately linked to a ticket, a ticket to an issue and subsequently to a part (product capabilities and features).\\n\\n| Link | Control |\\n| --- | --- |\\n| Conversation \\xe2\\x86\\x92 Ticket | Open the conversation and click **Tickets > + Link tickets**. Either create a new ticket or select an existing ticket. |\\n| Ticket \\xe2\\x86\\x92 Issue | Open the ticket and click **Issues > + Link issues**. Either create a new issue or select an existing issue. |\\n| Issue \\xe2\\x86\\x92",
"title": "Apps | Computer by DevRev | DevRev"
},
{
"id": "ART-1979_KNOWLEDGE_NODE-40",
"text": "a child issue or create a new one by clicking on **+ New issue**.\\nJust update the title of the child issue and click enter. All other fields will be populated automatically by DevRev. You can edit them later.\\n\\nTags\\n----\\n\\n* Stalled\\n* Priority/Escalated\\n* Fast/Slow Moving\\n* Blocked\\n* Resolution: [*value*]\\n* Impact: [*value*]\\n* Reason: [*value*]\\n\\nStages\\n------\\n\\nThe following figure shows the state machine for tickets.\\n\\n```\\nClosed\\n\\n\\n\\nIn",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-1964_KNOWLEDGE_NODE-27",
"text": "the top of the DevRev app main page, and select either **Ticket** or **Issue**.\\n2. Click the template icon next to the **Select Subtype** drop-down menu and select a template. The selected template is applied to the object.\\n\\nUsing article templates\\n-----------------------\\n\\n1. Under [**Settings > Knowledge Base**](https://app.devrev.ai/devrev/settings/knowledge-base/articles), go to **View Templates**. A modal opens, showing a list and preview of the available templates.\\n2. Select a",
"title": "Templates | Computer by DevRev | DevRev"
},
{
"id": "ART-1438_KNOWLEDGE_NODE-0",
"text": "b'[](/public/api-reference/works/create)\\n\\nPublic\\n\\n[API Reference](/public/api-reference/getting-started)[Works](/public/api-reference/works/tickets-and-issues)\\n\\n# Create Work\\n\\nPOST\\n\\nhttps://api.devrev.ai/works.create\\n\\nTry it\\n\\nCreates new work ([issue](https://devrev.ai/docs/product/build), [ticket](https://devrev.ai/docs/product/support)) item. [task](https://devrev.ai/docs/product/tasks) and opportunity work types are supported in the beta version.\\n\\n### Request\\n\\nThis endpoint",
"title": "Create Work — DevRev | Docs"
},
{
"id": "ART-1361_KNOWLEDGE_NODE-0",
"text": "b'Create Work | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[works](/api-reference/works/tickets-and-issues)\\n\\nCreate Work\\n===========\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/works.create\\n\\nPOST\\n\\n/works.create\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/works.create \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -H \"Content-Type:",
"title": "Create Work | DevRev | Docs"
},
{
"id": "ART-1651_KNOWLEDGE_NODE-438",
"text": "Reference works Create.\\n\\nPOST https:// api.devrev.ai / works.create\\n\\nCreates new work ( issue , ticket ) item. task and opportunity work types are supported in the beta version.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nIssue Show 19 properties\\nOR\\nOpportunity Show 21 properties\\nOR\\nTask Show 17 properties\\nOR\\nTicket Show 21 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nwork object\\nShow 4 variants\\nPOST / works.create\\ncURL\\n$ curl -X POST",
"title": "Create — DevRev | Docs"
}
] |
e264b7a8-d44a-4b8e-be4d-5698c2a7c61c
|
pause SLA for other ticket stages Awaiting Customer
|
[
{
"id": "ART-1986_KNOWLEDGE_NODE-38",
"text": "ticket is moved to the Closed state | The ticket was moved to Awaiting Customer Response state | The ticket moves to any state except Closed |\\n\\n**Conversations**\\n\\n| Metric | Default conditions | Start event | End event | Pause event | Resume event |\\n| --- | --- | --- | --- | --- | --- |\\n| First response time | The first message sent by a customer | Conversation created | * The agent replied to the conversation * The conversation is moved to Waiting on User/Resolved * The conversation is",
"title": "Service-level agreement | Computer for Support Teams | DevRev"
},
{
"id": "ART-1986_KNOWLEDGE_NODE-34",
"text": "target defined in the policy.\\n* *Breached*: The time spent by the SLA metric is greater than or equal to the breach target defined in the policy.\\n* *Paused*: The metric is currently paused based on some conditions. For example, when a ticket moves to awaiting customer response.\\n* *Completed*: The conversation or ticket has reached the completion condition.\\n\\nBased on business hours defined for an organization, *Active/Close to breach/Breached* metrics can change schedules. Metrics move out",
"title": "Service-level agreement | Computer for Support Teams | DevRev"
},
{
"id": "ART-2695_KNOWLEDGE_NODE-31",
"text": "additional configuration; it automatically resumes when the issue stage updates to any stage not designated for stopping the timer.\\n5. Click **Save**.\\n\\nAssigning stage values for starting and stopping the timer is mandatory. Ensure that each stage value is unique across the start, pause, and stop options. Any configuration changes will only apply to issues created after the changes are made.\\n\\n![]()\\n\\nUninstalling the snap-in will remove the OLA metric from all active and new issues, which",
"title": "Operational-level agreement | Computer for Support Teams | DevRev"
},
{
"id": "ART-2695_KNOWLEDGE_NODE-30",
"text": "*start*, *pause*, and *stop*. This configuration is available through the **OLA metrics for issues** snap-in. **Issue Resolution Time** is the default metric. For additional metrics, contact our support team.\\n\\n1. Go to **Settings** > **Integrations** > **Snap-ins**.\\n2. Locate and view the **OLA metrics for issues** snap-in.\\n3. Click on **Configure** within the snap-in.\\n4. Select stage values for the **Issue Resolution Timer** to start, pause, and stop. Resuming a paused timer requires no",
"title": "Operational-level agreement | Computer for Support Teams | DevRev"
}
] |
f536db1b-24b2-445d-8eda-6becd6322a79
|
what is DevRev platform overview introduction
|
[
{
"id": "ART-15792_KNOWLEDGE_NODE-0",
"text": "b'What is DevRev?\\n\\nDevRev is an enterprise AI platform that delivers \"Team Intelligence\" by transforming artificial intelligence from a passive tool into an active business teammate. The company addresses a fundamental challenge facing modern organizations: the fragmentation of company knowledge across multiple systems and databases that prevents AI from delivering meaningful business value.Core platform capabilities\\n\\nDevRev\\'s platform centers around three key components that work together",
"title": "DevRev Products and Agents"
},
{
"id": "ART-16607_KNOWLEDGE_NODE-4",
"text": "platform purpose-built for companies, combining support, product, and growth apps to unify end users, sellers, support engineers, product teams, and developers. By reducing dependency on nine disconnected business tools and converging six operational teams, DevRev accelerates product velocity and customer satisfaction.\\n\\nDevRev offers a blank-canvas approach to collaboration, analytics, and AI. Our platform empowers companies to ship faster, resolve smarter, and retain better leveraging",
"title": "DevRev Careers | Partner Solutions Engineer"
},
{
"id": "ART-896_KNOWLEDGE_NODE-5",
"text": "product, and growth teams. It connects end users, sellers, support, product people, and developers, reducing 9 business apps and converging 6 teams onto a common platform. \\nUnlike horizontal CRMs, DevRev takes a blank canvas approach to collaboration, AI, and analytics, enabling SaaS companies to increase product velocity and reduce customer churn. DevRev is used by thousands of companies in search of low latency analytics and customizable LLMs to thrive in this era of GenAI. \\nDevRev was",
"title": "Events"
},
{
"id": "ART-16347_KNOWLEDGE_NODE-4",
"text": "comprises three modern CRM apps for support, product, and growth teams. It connects end users, sellers, support, product people, and developers, reducing 9 business apps and converging 6 teams onto a common platform. \\n \\nUnlike horizontal CRMs, DevRev takes a blank canvas approach to collaboration, AI, and analytics, enabling SaaS companies to increase product velocity and reduce customer churn. DevRev is used by thousands of companies in search of low latency analytics and customizable LLMs",
"title": "DevRev Careers | Account Executive - Startups"
},
{
"id": "ART-12585_KNOWLEDGE_NODE-4",
"text": "three modern CRM apps for support, product, and growth teams. It connects end users, sellers, support, product people, and developers, reducing 9 business apps and converging 6 teams onto a common platform. \\n \\nUnlike horizontal CRMs, DevRev takes a blank canvas approach to collaboration, AI, and analytics, enabling SaaS companies to increase product velocity and reduce customer churn. DevRev is used by thousands of companies in search of low latency analytics and customizable LLMs to thrive",
"title": "DevRev Careers | Forward Deployed Engineer"
},
{
"id": "ART-12589_KNOWLEDGE_NODE-4",
"text": "three modern CRM apps for support, product, and growth teams. It connects end users, sellers, support, product people, and developers, reducing 9 business apps and converging 6 teams onto a common platform. \\n \\nUnlike horizontal CRMs, DevRev takes a blank canvas approach to collaboration, AI, and analytics, enabling SaaS companies to increase product velocity and reduce customer churn. DevRev is used by thousands of companies in search of low latency analytics and customizable LLMs to thrive",
"title": "DevRev Careers | Forward Deployed Architect"
},
{
"id": "ART-1960_KNOWLEDGE_NODE-30",
"text": "customer (rev).\\n: Terms related to\\xc2\\xa0*dev*:\\n\\n * *[rev](#rev)*\\n: dev-users [*API reference*](https://developer.devrev.ai/api-reference/dev-users/)\\n\\nDevRev\\n\\n: A platform that brings developers (devs) closer to customers (revs) by providing a single system of record for development, customer-facing, and product teams.\\n: DevRev\\'s mission is to leverage design, data engineering, and machine intelligence to empower engineers to embrace their customers.\\n: Read more",
"title": "Glossary | Computer by DevRev | DevRev"
},
{
"id": "ART-15792_KNOWLEDGE_NODE-9",
"text": "information sharing and reporting by converging support, product and user data in one shared view.\\n\\nAutomated knowledge base management: AI agents remember successful resolutions and instantly apply them to future issues, reducing customer wait time.\\n\\nSource: [DevRev Support](https://devrev.ai/support)BuildWhat is DevRev Build?\\n\\nDevRev Build is a full-featured product development platform built for modern businesses and trusted by leading organizations\\n\\nKey Features:\\n\\nAuto-generate",
"title": "DevRev Products and Agents"
},
{
"id": "ART-15643_KNOWLEDGE_NODE-4",
"text": "from the soul-crushing work of chasing data. They can stop managing software and start focusing on what truly matters: solving bigger problems, building better products, and creating happier customers.\\n\\nAnd you? You can save time, money, and better allocate your resources.\\n\\nWe started DevRev to deliver this ideal state.\\n\\nWe call it Team Intelligence.\\n\\nWe start by connecting to the systems you already use, like Salesforce, Jira, and Google Workspace with our bidirectional sync engine",
"title": "DevRev Corp Narrative - for PLuG on website"
},
{
"id": "ART-15955_KNOWLEDGE_NODE-1",
"text": "purpose-built for SaaS companies, comprises three modern CRM apps for support, product, and growth teams. It connects end users, sellers, support, product people, and developers, reducing 9 business apps and converging 6 teams onto a common platform. \\n \\nUnlike horizontal CRMs, DevRev takes a blank canvas approach to collaboration, AI, and analytics, enabling SaaS companies to increase product velocity and reduce customer churn. DevRev is used by thousands of companies in search of low",
"title": "DevRev Careers | Applied AI- Echo"
},
{
"id": "ART-1945_KNOWLEDGE_NODE-25",
"text": "product.\\n\\n\\xf0\\x9f\\x94\\x97 Platform\\n----------\\n\\nDevRev's [platform](./product/core) seamlessly connects [identities](./product/groups) (user, developer, support engineer, PM) and [parts](./product/parts) (product, capabilities, features, APIs) by interweaving design and artificial intelligence. This results in intelligent routing, classification, and prioritization of all work, including conversations, tickets, issues, enhancements, and opportunities ([glossary",
"title": "Computer by DevRev | DevRev"
},
{
"id": "ART-13178_KNOWLEDGE_NODE-53",
"text": "information at runtime, DevRev employs continuous synchronization across systems. Its platform indexes data from over 30 integrations into a knowledge graph that meaningfully connects products, work processes, and customers.\\n\\n### Rich contextual intelligence\\n\\nDevRev\\xe2\\x80\\x99s approach ensures AI agents operate with robust context. The system creates relationships between disparate information sources, enabling agents to understand complex business situations and take appropriate actions",
"title": "Understanding Agentic AI: Capabilities and Implications for the Future"
},
{
"id": "ART-15202_KNOWLEDGE_NODE-4",
"text": "interfaces that deliver precise answers, advanced analytics, and workflow automations. Think ChatGPT, but for work, enabled across existing data sources and software. DevRev also provides AI-native apps for customer support, product management, and engineering that can coexist with or replace legacy solutions.\\n\\nHeadquartered in Palo Alto, California, DevRev has offices in seven global locations. We have raised $100 million in funding from investors like Khosla Ventures and Mayfield at a $1.1",
"title": "DevRev Careers | Senior Customer Success Manager"
},
{
"id": "ART-15588_KNOWLEDGE_NODE-1",
"text": "for SaaS companies, comprises three modern CRM apps for support, product, and growth teams. It connects end users, sellers, support, product people, and developers, reducing 9 business apps and converging 6 teams onto a common platform. \\n \\nUnlike horizontal CRMs, DevRev takes a blank canvas approach to collaboration, AI, and analytics, enabling SaaS companies to increase product velocity and reduce customer churn. DevRev is used by thousands of companies in search of low latency analytics",
"title": "DevRev Careers | Account Executive"
},
{
"id": "ART-16687_KNOWLEDGE_NODE-1",
"text": "SaaS companies, comprises three modern CRM apps for support, product, and growth teams. It connects end users, sellers, support, product people, and developers, reducing 9 business apps and converging 6 teams onto a common platform. \\n \\nUnlike horizontal CRMs, DevRev takes a blank canvas approach to collaboration, AI, and analytics, enabling SaaS companies to increase product velocity and reduce customer churn. DevRev is used by thousands of companies in search of low latency analytics and",
"title": "DevRev Careers | Illustrator"
},
{
"id": "ART-15201_KNOWLEDGE_NODE-3",
"text": "October 2020 by Dheeraj Pandey, former co-founder and CEO of Nutanix, and Manoj Agarwal, former SVP of Engineering at Nutanix, DevRev continues to push the boundaries of innovation, helping thousands of companies thrive in the rapidly evolving landscape of AI-driven SaaS.\\n\\nDevRev is conversational AI at work, right now. Patented technology unifies siloed data from legacy tools like Salesforce, Jira, and more into a knowledge graph, powering conversational AI interfaces that deliver precise",
"title": "DevRev Careers | Senior Customer Success Manager"
},
{
"id": "ART-16685_KNOWLEDGE_NODE-1",
"text": "purpose-built for SaaS companies, comprises three modern CRM apps for support, product, and growth teams. It connects end users, sellers, support, product people, and developers, reducing 9 business apps and converging 6 teams onto a common platform. \\n \\nUnlike horizontal CRMs, DevRev takes a blank canvas approach to collaboration, AI, and analytics, enabling SaaS companies to increase product velocity and reduce customer churn. DevRev is used by thousands of companies in search of low",
"title": "DevRev Careers | Customer Success Manager"
},
{
"id": "ART-15201_KNOWLEDGE_NODE-4",
"text": "answers, advanced analytics, and workflow automations. Think ChatGPT, but for work, enabled across existing data sources and software. DevRev also provides AI-native apps for customer support, product management, and engineering that can coexist with or replace legacy solutions.\\n\\nHeadquartered in Palo Alto, California, DevRev has offices in seven global locations. We have raised $100 million in funding from investors like Khosla Ventures and Mayfield at a $1.1 billion valuation. We are also",
"title": "DevRev Careers | Senior Customer Success Manager"
},
{
"id": "ART-15643_KNOWLEDGE_NODE-5",
"text": "called DevRev Airdrop.\\n\\nWe then organize your information into a patented Knowledge Graph - a living network of data built around what matters most: your Products (Dev) and your Customers (Rev).\\n\\nThis graph powers our agentic AI. It doesn't just find information; it takes autonomous action. You give our agents instructions in plain language, and they can execute complex workflows on your behalf. Or, build your own agents with our agent builder - no coding required.\\n\\nFor example, when a",
"title": "DevRev Corp Narrative - for PLuG on website"
},
{
"id": "ART-15627_KNOWLEDGE_NODE-0",
"text": "b'DevRev Pricing Q&A General Pricing Questions For complete pricing overview: \\xc2\\xa0 https://devrev.ai/pricing What products does DevRev offer? DevRev offers four main products:\\n\\nSupport : Customer support and engagement platform\\n\\nBuild : Product development and engineering platform\\n\\nPLuG : In-app engagement, observability, and monitoring\\n\\nAgentOS : Enterprise AI-native platform\\n\\nHow does the pricing structure work? Each product offers a tiered pricing structure with three tiers:",
"title": "DevRev Pricing - for the PLuG on the website"
},
{
"id": "ART-1945_KNOWLEDGE_NODE-28",
"text": "platform makes product teams more efficient and customer-centric and syncs seamlessly with Jira's legacy issues.\\n\\nTo learn about the apps, check out the onboarding page for each app by clicking **Onboarding** located at the bottom of the app.\\n\\n![]()\\n\\n\\xf0\\x9f\\xa7\\xa9 Snap-ins\\n----------\\n\\nAdd-on modules for DevRev, called [snap-ins](./snapins), are available on the [Marketplace](/marketplace). Snap-ins are one of three types. Integrations let you connect DevRev with existing systems",
"title": "Computer by DevRev | DevRev"
},
{
"id": "ART-970_KNOWLEDGE_NODE-83",
"text": "WHOIS Server: whois.nic.ai\\nCreation Date: 2020-06-07T22:25:10.749Z\\n\\n\\nAt its core, DevRev was built to converge the events, products and people (customers, partners and employees) focused around building, operating, supporting, and growing of products. Through the linkage between these objects, we were able to build a powerful knowledge graph that is used to drive every piece of the system.\\n\\nWith the ability to triangulate across these vertices, we can do some really amazing things and",
"title": "The Story"
},
{
"id": "ART-15792_KNOWLEDGE_NODE-1",
"text": "to create comprehensive business intelligence:\\n\\nUnified data integration: The platform connects to existing business systems including Salesforce, Jira, and Google Workspace through their bidirectional synchronization engine called DevRev Airdrop. This eliminates the data silos that typically prevent AI from accessing complete business context.\\n\\nKnowledge graph architecture: DevRev organizes all connected information into a patented Knowledge Graph, which creates a living network of data",
"title": "DevRev Products and Agents"
},
{
"id": "ART-15792_KNOWLEDGE_NODE-2",
"text": "structured around two critical business dimensions: Products (Dev) and Customers (Rev). This architectural approach ensures that AI agents have comprehensive context when making decisions or taking actions.\\n\\nAgentic AI capabilities: DevRev provides both out-of-the-box agents and an Agent Studio to build, customize, deploy and manage agents. Users can instruct these agents in plain language to execute complex workflows autonomously, with agents capable of creating tickets, updating records,",
"title": "DevRev Products and Agents"
},
{
"id": "ART-16076_KNOWLEDGE_NODE-3",
"text": "former SVP of Engineering at Nutanix, DevRev continues to push the boundaries of innovation, helping thousands of companies thrive in the rapidly evolving landscape of AI-driven SaaS.\\n\\nDevRev is conversational AI at work, right now. Patented technology unifies siloed data from legacy tools like Salesforce, Jira, and more into a knowledge graph, powering conversational AI interfaces that deliver precise answers, advanced analytics, and workflow automations. Think ChatGPT, but for work, enabled",
"title": "DevRev Careers | Customer Success Manager"
},
{
"id": "ART-13178_KNOWLEDGE_NODE-52",
"text": "the gap between cutting-edge AI capabilities and existing enterprise infrastructure.\\n\\n### AgentOS: The unified platform\\n\\nAt the core of DevRev\\xe2\\x80\\x99s approach is AgentOS, a unified system connecting humans and AI agents in one seamless environment. This platform provides autonomous agents with essential tools and data while offering humans an intuitive interface to define agent capabilities and collaborate in real-time.\\n\\n### Complete data integration\\n\\nUnlike solutions that pull",
"title": "Understanding Agentic AI: Capabilities and Implications for the Future"
},
{
"id": "ART-1944_KNOWLEDGE_NODE-6",
"text": "product development activities with now/next/later and sprints.\\n\\nGrow.\\n\\nGrow customers, not departments, with a common platform where all teams can collaborate to optimize customer lifetime value.\\n\\nSnap-ins.\\n\\nConnect tools, automate work, and extend your experience with add-on modules provided by DevRev.\\n\\nDeveloper.\\n\\nEnabling developers to create tools for the future with DevRev APIs.\\n\\nEnterprise grade security to protect customer data\\nLearn more about it.\\nProduct\\n\\nBuild",
"title": "DevRev Documentation"
},
{
"id": "ART-1945_KNOWLEDGE_NODE-24",
"text": "Snap-ins](#-snapins)\\n\\n1. [Documentation](/docs)\\n3. [Computer by DevRev](/docs/intro)\\n\\nComputer by DevRev\\n==================\\n\\nDevRev has taken a platform approach to converging business infrastructure, which we call the Computer by DevRev, for the operating system that supports both human agents and AI agents. At the core of this operating system is Memory that brings all people and work (and users and activities) together around two core dimensions \\xe2\\x80\\x94 customer and",
"title": "Computer by DevRev | DevRev"
},
{
"id": "ART-738_KNOWLEDGE_NODE-3",
"text": "graph\\n\\nAt its core, DevRev was built to converge the events, products and people (customers, partners and employees) focused around building, operating, supporting, and growing of products. Through the linkage between these objects, we were able to build a powerful knowledge graph that is used to drive every piece of the system.\\n\\nWith the ability to triangulate across these vertices, we can do some really amazing things and provide much more understanding and insight. This is applicable to",
"title": "DevRev | Built for AI (not by AI... yet)"
},
{
"id": "ART-1945_KNOWLEDGE_NODE-26",
"text": "\\xe2\\x86\\x97\\xef\\xb8\\x8f](https://support.devrev.ai/devrev/article/ART-16784-glossary)), maximizing productivity and minimizing customer churn.\\n\\n\\xf0\\x9f\\x9b\\xa0\\xef\\xb8\\x8f Apps\\n-------\\n\\nDevRev\\xe2\\x80\\x99s platform integrates all departments with a customizable CRM, serverless workflow engine, and a bot-supported collaborative experience comprising two native [apps](./product/apps): Computer for Support Teams and Computer for Builders.\\n\\nStreamline customer support with [product-centric",
"title": "Computer by DevRev | DevRev"
}
] |
e50828d5-fb46-4b71-a96b-0e953940b82a
|
create monthly analytics report for tickets
|
[
{
"id": "ART-15716_KNOWLEDGE_NODE-35",
"text": "filters\\n\\nYou can create a simple report by clicking on the Smart Icon at the top right corner and selecting \\'Create New report.\\' Create a dashboard and a widget by giving a name. Select the dimensions and measures and finalize the visualization of the widget and click on the preview widget to test it out.\\n\\nEach widget can be customized with filters, groupings, and visualizations (charts, tables, etc.)4. Create a dashboard for tracking ticket resolution time\\n\\nCreate a new dashboard in",
"title": "Support queries related playbook"
},
{
"id": "ART-1003_KNOWLEDGE_NODE-23",
"text": "CURRENT_DATE);\\n-- NOTE: Replace @period with 'DAY', 'WEEK', 'MONTH', or 'QUARTER'.\\n\\n\\nTicket Backlog\\n\\n\\n Definition\\n \\n The number of unresolved support tickets at any given time, which can indicate workload and efficiency issues.\\n \\n \\n Calculation\\n \\n (Total number of open tickets) - (Total number of tickets closed during a specific period)\\n \\n \\n\\n\\nSELECT (COUNT(*) - (SELECT COUNT(*) FROM tickets WHERE status = 'closed' AND EXTRACT(@period FROM created_at)",
"title": "Understanding a Support Lead's Pain Points and KPIs"
},
{
"id": "ART-1004_KNOWLEDGE_NODE-9",
"text": "tickets\\nWHERE EXTRACT(@period FROM created_at) = EXTRACT(@period FROM CURRENT_DATE)\\nGROUP BY engineer_id;\\n-- NOTE: Replace @period with 'DAY', 'WEEK', 'MONTH', or 'QUARTER'.\\n\\n\\nIndividual Customer Satisfaction (CSAT) Score\\n\\n\\n Definition\\n \\n A metric that gauges customer satisfaction with the support provided by a specific engineer, typically collected through surveys.\\n \\n \\n Calculation\\n \\n (Number of satisfied responses for the engineer) / (Total number of",
"title": "Understanding a Support Engineer's Pain Points and KPIs"
},
{
"id": "ART-1003_KNOWLEDGE_NODE-24",
"text": "= EXTRACT(@period FROM CURRENT_DATE))) AS TicketBacklog\\nFROM tickets\\nWHERE status != 'closed'\\nAND EXTRACT(@period FROM created_at) = EXTRACT(@period FROM CURRENT_DATE);\\n-- NOTE: Replace @period with 'DAY', 'WEEK', 'MONTH', or 'QUARTER'.\\n\\n\\nEscalation Rate\\n\\n\\n Definition\\n \\n The percentage of support tickets that require escalation to higher-level support or other departments.\\n \\n \\n Calculation\\n \\n (Total number of escalated tickets) / (Total number of tickets)",
"title": "Understanding a Support Lead's Pain Points and KPIs"
},
{
"id": "ART-1952_KNOWLEDGE_NODE-27",
"text": "bring in data from other sources as well.\\n\\nDiscover\\n--------\\n\\nTo get started, click the \\xe2\\x9a\\xa1 button on a vista. The following options are available:\\n\\n* Create New Report\\n* View Past Reports: Created by me or shared with me\\n\\nYou can also search for reports and find more on the **Explore** page.\\n\\n![]()\\n\\n### Create\\n\\nYou can create your own reports by adding a name, description, and creating widgets. Here, you'll also be able to preview your report and make any necessary",
"title": "Vista Reports | Vistas | Computer by DevRev | DevRev"
},
{
"id": "ART-1003_KNOWLEDGE_NODE-25",
"text": "* 100\\n \\n \\n\\n\\nSELECT (COUNT(*) * 100) / (SELECT COUNT(*) FROM tickets WHERE EXTRACT(@period FROM created_at) = EXTRACT(@period FROM CURRENT_DATE)) AS EscalationRate\\nFROM tickets\\nWHERE is_escalated = 1\\nAND EXTRACT(@period FROM created_at) = EXTRACT(@period FROM CURRENT_DATE);\\n-- NOTE: Replace @period with 'DAY', 'WEEK', 'MONTH', or 'QUARTER'.\\n\\n\\nAgent Utilization Rate\\n\\n\\n Definition\\n \\n The percentage of an engineer\\xe2\\x80\\x99s working hours spent on handling customer",
"title": "Understanding a Support Lead's Pain Points and KPIs"
},
{
"id": "ART-15716_KNOWLEDGE_NODE-36",
"text": "the Dashboards section.\\n\\nAdd a widget for \\xe2\\x80\\x9cTicket Resolution Time\\xe2\\x80\\x9d or \\xe2\\x80\\x9cAverage Time to Resolution.\\xe2\\x80\\x9d\\n\\nConfigure the widget to display data by agent, team, or time period.\\n\\nUse filters to focus on specific ticket types, priorities, or customer segments.\\n\\nFor more granular analysis, use a table or chart widget with custom SQL or filters.\\n\\nThis will help you monitor and improve your team\\xe2\\x80\\x99s responsiveness.5. Configuring branding of the",
"title": "Support queries related playbook"
},
{
"id": "ART-1979_KNOWLEDGE_NODE-27",
"text": "also be used to engage customers for feedback/ideas (such as new feature ideas). Scoping is important for broadcast tickets as there needs to be a differentiation between broadcast (all revs) vs. multicast (particular revs).\\n\\nViews of tickets can be found under **Support** in the DevRev app.\\n\\n![]()\\n\\nYou can export views to CSV or JSON by selecting **Actions** in the upper-right corner and choosing the format.\\n\\nAttributes\\n----------\\n\\nTickets have attributes that can be used to filter",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-1003_KNOWLEDGE_NODE-19",
"text": "t.created_at) = EXTRACT(@period FROM CURRENT_DATE);\\n-- NOTE: Replace @period with 'DAY', 'WEEK', 'MONTH', or 'QUARTER'.\\n\\n\\nAverage Resolution Time (ART)\\n\\n\\n Definition\\n \\n The average time it takes to resolve a customer issue from the moment it\\xe2\\x80\\x99s reported.\\n \\n \\n Calculation\\n \\n (Sum of resolution times for all resolved tickets) / (Total number of resolved tickets)\\n \\n \\n\\n\\nSELECT AVG(TIMESTAMPDIFF(MINUTE, t.created_at, t.resolved_at)) AS",
"title": "Understanding a Support Lead's Pain Points and KPIs"
},
{
"id": "ART-15716_KNOWLEDGE_NODE-33",
"text": "are interested in visualizing\\n\\nApply the necessary filters\\n\\nYou can create a simple report by clicking on the Smart Icon at the top right corner and selecting \\'Create New report.\\' Create a dashboard and a widget by giving a name. Select the dimensions and measures and finalize the visualization of the widget and click on the preview widget to test it out.\\n\\nEach widget can be customized with filters, groupings, and visualizations (charts, tables, etc.)2. Customizing CSAT Surveys\\n\\nYes,",
"title": "Support queries related playbook"
}
] |
da34387f-8e64-4bd9-9d92-b14340b734c4
|
issue template settings for bug subtype
|
[
{
"id": "ART-15487_KNOWLEDGE_NODE-47",
"text": "above can be referenced in the *bug* subtype as follows:\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl --location \\'https://api.devrev.ai/schemas.custom.set\\' \\\\ |\\n| > | --header \\'Content-Type: application/json\\' \\\\ |\\n| > | --header \\'Authorization: Bearer <TOKEN>\\' \\\\ |\\n| > | --data \\'{ |\\n| > | \"type\": \"custom_type_fragment\", |\\n| > | \"leaf_type\": \"issue\", |\\n| > | \"subtype\": \"bug\", |\\n| > | \"stage_diagram_id\": \"don:core:dvrv-us-1:devo/test:stages_diagram/1\", |\\n| > | \"fields\": [ |\\n| > |",
"title": "Object customization | DevRev | Docs"
},
{
"id": "ART-1645_KNOWLEDGE_NODE-11",
"text": "\"leaf_type\": \"issue\", \\n >| \"subtype\": \"bug\", \\n >| \"subtype_display_name\": \"Bug\", \\n >| \"fields\": [ \\n >| { \\n >| \"name\": \"impacted_environments\", \\n >| \"field_type\": \"array\", \\n >| \"base_type\": \"enum\", \\n >| \"allowed_values\": [ \"Dev\", \"QA\", \"Prod\" ], \\n >| \"is_filterable\": true, \\n >| \"ui\": { \\n >| \"display_name\": \"Impacted Environments\",",
"title": "Object customization (Beta) — DevRev | Docs"
},
{
"id": "ART-15487_KNOWLEDGE_NODE-24",
"text": "\"custom_type_fragment\", |\\n| > | \"description\": \"Attributes for tracking a bug\", |\\n| > | \"leaf_type\": \"issue\", |\\n| > | \"subtype\": \"bug\", |\\n| > | \"fields\": [ |\\n| > | { |\\n| > | \"name\": \"impacted_environments\", |\\n| > | \"field_type\": \"array\", |\\n| > | \"base_type\": \"enum\", |\\n| > | \"allowed_values\": [ \"Dev\", \"QA\", \"Prod\" ], |\\n| > | \"is_filterable\": true, |\\n| > | \"ui\": { |\\n| > | \"display_name\": \"Impacted Environments\", |\\n| > | } |\\n| > | }, |\\n| > | { |\\n| > | \"name\": \"rca\", |\\n| > |",
"title": "Object customization | DevRev | Docs"
},
{
"id": "ART-15487_KNOWLEDGE_NODE-10",
"text": "\"bug\", |\\n| > | \"subtype_display_name\": \"Bug\", |\\n| > | \"fields\": [ |\\n| > | { |\\n| > | \"name\": \"impacted_environments\", |\\n| > | \"field_type\": \"array\", |\\n| > | \"base_type\": \"enum\", |\\n| > | \"allowed_values\": [ \"Dev\", \"QA\", \"Prod\" ], |\\n| > | \"is_filterable\": true, |\\n| > | \"ui\": { |\\n| > | \"display_name\": \"Impacted Environments\", |\\n| > | } |\\n| > | }, |\\n| > | { |\\n| > | \"name\": \"regression\", |\\n| > | \"field_type\": \"bool\", |\\n| > | \"ui\": { |\\n| > | \"display_name\": \"Regression\", |\\n| > | }",
"title": "Object customization | DevRev | Docs"
},
{
"id": "ART-1964_KNOWLEDGE_NODE-27",
"text": "the top of the DevRev app main page, and select either **Ticket** or **Issue**.\\n2. Click the template icon next to the **Select Subtype** drop-down menu and select a template. The selected template is applied to the object.\\n\\nUsing article templates\\n-----------------------\\n\\n1. Under [**Settings > Knowledge Base**](https://app.devrev.ai/devrev/settings/knowledge-base/articles), go to **View Templates**. A modal opens, showing a list and preview of the available templates.\\n2. Select a",
"title": "Templates | Computer by DevRev | DevRev"
},
{
"id": "ART-1645_KNOWLEDGE_NODE-53",
"text": "\\n >| \"leaf_type\": \"issue\", \\n >| \"subtype\": \"bug\", \\n >| \"fields\": [ \\n >| ... // no changes \\n >| ], \\n >| \"conditions\": [ \\n >| { \\n >| \"expression\": \"stage == \\'don:core:dvrv-us-1:devo/test:stage/5\\'\", \\n >| \"effects\": [ \\n >| { \\n >| \"fields\": [ \"custom_fields.rca\" ], \\n >| \"require\": true \\n >| } \\n >|",
"title": "Object customization (Beta) — DevRev | Docs"
},
{
"id": "ART-1645_KNOWLEDGE_NODE-10",
"text": "(RCA) of the bug\\n\\nFirst, create a schema fragment defining the fields for the _bug_ subtype. Make sure to replace `<TOKEN>` with your API token.\\n\\n[code]\\n\\n $| curl --location \\'https://api.devrev.ai/schemas.custom.set\\' \\\\ \\n ---|--- \\n >| --header \\'Content-Type: application/json\\' \\\\ \\n >| --header \\'Authorization: Bearer <TOKEN>\\' \\\\ \\n >| --data \\'{ \\n >| \"type\": \"custom_type_fragment\", \\n >| \"description\": \"Attributes for tracking a bug\", \\n >|",
"title": "Object customization (Beta) — DevRev | Docs"
},
{
"id": "ART-1645_KNOWLEDGE_NODE-26",
"text": "---|--- \\n >| --header \\'Content-Type: application/json\\' \\\\ \\n >| --header \\'Authorization: Bearer <TOKEN>\\' \\\\ \\n >| --data \\'{ \\n >| \"type\": \"custom_type_fragment\", \\n >| \"description\": \"Attributes for tracking a bug\", \\n >| \"leaf_type\": \"issue\", \\n >| \"subtype\": \"bug\", \\n >| \"fields\": [ \\n >| { \\n >| \"name\": \"impacted_environments\", \\n >| \"field_type\": \"array\", \\n >| \"base_type\":",
"title": "Object customization (Beta) — DevRev | Docs"
},
{
"id": "ART-2053_KNOWLEDGE_NODE-46",
"text": "used. The subtype format is as follows: \\\\_jira\\\\\\\\_{jira\\\\\\\\_site}\\\\\\\\_{jira\\\\\\\\_project\\\\\\\\_name}\\\\\\\\_issues.{type}\\\\_. For example, if you want to sync to a Bug to a Jira project called **Maple** that's served through [https://devrev.atlassian.net](https://devrev.atlassian.net/), this would show as \\\\_jira\\\\\\\\_devrev.atlassian.net\\\\\\\\_maple\\\\\\\\_issues.bug\\\\_.\\n\\nAfter a DevRev work item has been marked for syncing, it's created in the specified Jira project the next time the [Sync from",
"title": "Jira Software AirSync | AirSync | Snap-ins | DevRev"
},
{
"id": "ART-1964_KNOWLEDGE_NODE-26",
"text": "Preset fields based on the selected template type are displayed. You can customize these by adding additional attributes if necessary.\\n\\nEditing templates\\n-----------------\\n\\nTo edit or delete a template, navigate to [**Settings** > **Templates**](https://app.devrev.ai/devrev/settings/record-template). Under the **Action** column, select **Edit** or **Delete**.\\n\\nUsing templates for tickets and issues\\n--------------------------------------\\n\\n1. Click **+** in the record creation panel at",
"title": "Templates | Computer by DevRev | DevRev"
},
{
"id": "ART-15487_KNOWLEDGE_NODE-49",
"text": "\\'https://api.devrev.ai/schemas.custom.set\\' \\\\ |\\n| > | --header \\'Content-Type: application/json\\' \\\\ |\\n| > | --header \\'Authorization: Bearer <TOKEN>\\' \\\\ |\\n| > | --data \\'{ |\\n| > | \"type\": \"custom_type_fragment\", |\\n| > | \"leaf_type\": \"issue\", |\\n| > | \"subtype\": \"bug\", |\\n| > | \"fields\": [ |\\n| > | ... // no changes |\\n| > | ], |\\n| > | \"conditions\": [ |\\n| > | { |\\n| > | \"expression\": \"stage == \\'don:core:dvrv-us-1:devo/test:stage/5\\'\", |\\n| > | \"effects\": [ |\\n| > | { |\\n| > |",
"title": "Object customization | DevRev | Docs"
},
{
"id": "ART-1964_KNOWLEDGE_NODE-25",
"text": "articles at the workspace level.\\n\\nManage templates\\n----------------\\n\\nTo create, edit, use, and delete templates, go to [**Settings** > **Templates**](https://app.devrev.ai/devrev/settings/record-template).\\n\\nCreating templates\\n------------------\\n\\n1. Click **+ Templates**.\\n2. Enter a **Name** (required) and an optional **Description** for the template.\\n3. Select the **Object Type** (*Article*, *Issues*, *Tickets*) under which the template will be categorized.\\n4. Click **Next**.\\n5.",
"title": "Templates | Computer by DevRev | DevRev"
}
] |
fa76510d-2b83-4709-b882-507fdad4ea73
|
workflow to stop stage change to close if specific fields are not populated on ticket
|
[
{
"id": "ART-15716_KNOWLEDGE_NODE-31",
"text": "conditions While creating custom schema\\n\\nThis can be handled by our team. Kindly reach out to us, and we\\xe2\\x80\\x99ll be happy to assist you with setting up a custom schema. Would you like us to create a ticket for this?\\n\\nAPI for stage customizationThis can be handled by our team. Kindly reach out to us, and we\\xe2\\x80\\x99ll be happy to assist you with setting this up. Would you like us to create a ticket for this?\\n\\nStage customization (e.g., customizing workflow stages for tickets,",
"title": "Support queries related playbook"
},
{
"id": "ART-15487_KNOWLEDGE_NODE-48",
"text": "... // no changes |\\n| > | ] |\\n| > | }\\' |\\n```\\n\\nAll objects of the *bug* subtype now adhere to the stage diagram created above.\\n\\nConfigure dependent fields\\n--------------------------\\n\\n##### \\n\\nThe developers in your organization tend to forget to add an RCA when resolving the\\nbugs. You can make the *RCA* field required when a *bug* object is moved to the\\n*completed* stage by adding a dependent field constraint.\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl --location",
"title": "Object customization | DevRev | Docs"
},
{
"id": "ART-1645_KNOWLEDGE_NODE-53",
"text": "\\n >| \"leaf_type\": \"issue\", \\n >| \"subtype\": \"bug\", \\n >| \"fields\": [ \\n >| ... // no changes \\n >| ], \\n >| \"conditions\": [ \\n >| { \\n >| \"expression\": \"stage == \\'don:core:dvrv-us-1:devo/test:stage/5\\'\", \\n >| \"effects\": [ \\n >| { \\n >| \"fields\": [ \"custom_fields.rca\" ], \\n >| \"require\": true \\n >| } \\n >|",
"title": "Object customization (Beta) — DevRev | Docs"
},
{
"id": "ART-15487_KNOWLEDGE_NODE-50",
"text": "\"fields\": [ \"custom_fields.rca\" ], |\\n| > | \"require\": true |\\n| > | } |\\n| > | ] |\\n| > | } |\\n| > | ] |\\n| > | }\\' |\\n```\\n\\nAny attempt to update a *bug* object to the *completed* stage without populating\\nthe *RCA* field is rejected.\\n\\nThe supported operators are `==`, `!=`, `&&`, `||`. The `expression` is a\\nbinary expression that must return a boolean value.\\n\\nThe `effects` array contains the list of effects of the condition. The following effects are supported:\\n\\n* `require`: Whether",
"title": "Object customization | DevRev | Docs"
},
{
"id": "ART-1645_KNOWLEDGE_NODE-54",
"text": "] \\n >| } \\n >| ] \\n >| }\\'\\n[/code] \\n \\nAny attempt to update a _bug_ object to the _completed_ stage without populating the _RCA_ field is rejected.\\n\\nThe supported operators are `==`, `!=`, `>`, `>=`, `<`, `<=`. The `expression` is a boolean expression that must return a boolean value.\\n\\nThe `effects` array contains the list of effects of the condition. The following effects are supported:\\n\\n * `require`: Whether the field must be set for the condition",
"title": "Object customization (Beta) — DevRev | Docs"
},
{
"id": "ART-1645_KNOWLEDGE_NODE-52",
"text": "developers in your organization tend to forget to add an RCA when resolving the bugs. You can make the _RCA_ field required when a _bug_ object is moved to the _completed_ stage by adding a dependent field constraint.\\n\\n[code]\\n\\n $| curl --location \\'https://api.devrev.ai/schemas.custom.set\\' \\\\ \\n ---|--- \\n >| --header \\'Content-Type: application/json\\' \\\\ \\n >| --header \\'Authorization: Bearer <TOKEN>\\' \\\\ \\n >| --data \\'{ \\n >| \"type\": \"custom_type_fragment\",",
"title": "Object customization (Beta) — DevRev | Docs"
},
{
"id": "ART-15487_KNOWLEDGE_NODE-51",
"text": "the field must be set for the condition to be met.\\n* `show`: Whether the field must be shown for the condition to be met.\\n* `allowed_values`: The conditional allowed values for the enum type field.\\n\\n##### \\n\\n`don:core:dvrv-us-1:devo/test:stage/5` is the ID of the *completed* stage. The\\nstage display name is not used in the expression because it is liable to change.\\n\\nConstraints on stock fields can only be strengthened.\\nFor example, a required stock field cannot be made optional, and a",
"title": "Object customization | DevRev | Docs"
},
{
"id": "ART-1645_KNOWLEDGE_NODE-55",
"text": "to be met.\\n * `show`: Whether the field must be shown for the condition to be met.\\n * `allowed_values`: The conditional allowed values for the enum type field.\\n\\n#####\\n\\n`don:core:dvrv-us-1:devo/test:stage/5` is the ID of the _completed_ stage. The stage display name is not used in the expression because it is liable to change.\\n\\nConstraints on stock fields can only be strengthened. For example, a required stock field cannot be made optional, and a hidden stock field cannot be made",
"title": "Object customization (Beta) — DevRev | Docs"
}
] |
f5437017-8214-4299-a1fe-1c1e422defa3
|
change spacing properties bottom side after init plug web chat widget
|
[
{
"id": "ART-2900_KNOWLEDGE_NODE-7",
"text": "* The `bottom` property determines the padding from the bottom of the launcher.\\n\\nThe default value is `10px`.\\n\\n * The `side` property determines the spacing of the widget from the launcher icon.\\n\\nThe default value is `0px`.\\n\\n[code]\\n\\n 1| spacing?:{ \\n ---|--- \\n 2| bottom?: '10px', \\n 3| side?:'10px', \\n 4| }\\n[/code] \\n \\n### Light/dark theme\\n\\nSet the theme of the PLuG widget.\\n\\n[code]\\n\\n 1| theme?: 'dark' | 'light'; \\n ---|---\\n[/code] \\n",
"title": "Custom implementation — DevRev | Docs"
},
{
"id": "ART-15496_KNOWLEDGE_NODE-5",
"text": "boolean; |\\n```\\n\\nThe default value is `true`.\\n\\n### Widget alignment\\n\\nAlign the widget to be placed on the left or right of the launcher.\\n\\nThe widget can be set to open to the left or to the right of the custom launcher.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | widget_alignment?: 'left' | 'right'; |\\n```\\n\\nThe default value is `right`.\\n\\n### Spacing\\n\\nAdjust spacing of the Plug widget.\\n\\nTwo properties are available to apply spacing.\\n\\n* The `bottom` property determines the padding",
"title": "Custom implementation | DevRev | Docs"
},
{
"id": "ART-15496_KNOWLEDGE_NODE-2",
"text": "Plug settings page of DevRev, the values set in the initalization code take priority over those which you have updated in your Plug settings.\\n\\nAll of these properties have to be passed as parameters while initializing the Plug widget using `plugSDK.init()`. For details, refer to the Plug SDK for Web [methods documentation](/sdks/web/methods).\\n\\n| Customization | Description |\\n| --- | --- |\\n| `custom_launcher_selector` | Customize the widget launcher to best fit your website or app. |\\n|",
"title": "Custom implementation | DevRev | Docs"
},
{
"id": "ART-2897_KNOWLEDGE_NODE-9",
"text": "launcher. Side: Spacing from the sides of the launcher| object `{bottom: string; side: string;}` \\n`theme`| The color scheme for the launcher and widget.| `light` or `dark` \\n`widget_alignment`| The PLuG widget can be positioned on either the left or right side of the launcher. You can also adjust the widget alignment through the PLuG settings at app.devrev.ai. If alignment settings are configured in both places, the value from app.devrev.ai will override the launcher setting.| left or right",
"title": "Methods — DevRev | Docs"
},
{
"id": "ART-2900_KNOWLEDGE_NODE-3",
"text": "have customized these properties of the widget through the PLuG settings page of DevRev, the values set in the initalization code take priority over those which you have updated in your PLuG settings.\\n\\nAll of these properties have to be passed as parameters while initializing the PLuG widget using `plugSDK.init()`. For details, refer to the PLuG SDK for Web [methods documentation](/public/sdks/web/methods).\\n\\nCustomization| Description \\n---|--- \\n`custom_launcher_selector`| Customize the",
"title": "Custom implementation — DevRev | Docs"
},
{
"id": "ART-15509_KNOWLEDGE_NODE-7",
"text": "will be attached. You can also set this selector from the Plug settings on app.devrev.ai. If both sources are set, this value will be considered the definitive source. | Boolean (True or False) |\\n| `spacing` | Padding from the launcher: This padding can also be set in the Plug settings on app.devrev.ai. If a value is specified in both places, this value will be considered the definitive source. Bottom: Padding from the bottom of the launcher. Side: Spacing from the sides of the launcher |",
"title": "Methods | DevRev | Docs"
},
{
"id": "ART-1466_KNOWLEDGE_NODE-14",
"text": "are set, this value will be considered the definitive source. | Boolean (True or False) | \\n| Padding from the launcher: This padding can also be set in the PLuG settings on app.devrev.ai. If a value is specified in both places, this value will be considered the definitive source. Bottom: Padding from the bottom of the launcher. Side: Spacing from the sides of the launcher | object | \\n|",
"title": "Methods — DevRev | Docs"
}
] |
51aaecfa-4dc3-4498-aed0-ebd7a101bf0c
|
phone number format error when creating user with leading zero
|
[
{
"id": "ART-15506_KNOWLEDGE_NODE-12",
"text": "\\xe2\\x9d\\x8c | \\xe2\\x9c\\x85 |\\n| `domains` | The attribute must be unique. Use a format like `devrev.ai`. Inputs like `https://devrev.ai` or `www.devrev.ai` are invalid. | array | \\xe2\\x9d\\x8c | \\xe2\\x9c\\x85 |\\n| `phone_numbers` | The phone number associated with the account must be in E.164 format. | array | \\xe2\\x9d\\x8c | \\xe2\\x9d\\x8c |\\n\\n##### \\n\\nEnsure that you follow the specified format when populating phone numbers and domains in the request body.\\n\\nPass custom",
"title": "Identify your users with Plug | DevRev | Docs"
},
{
"id": "ART-4096_KNOWLEDGE_NODE-4",
"text": "a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\n\\nphone_numberslist of stringsOptional\\n\\nPhone numbers, in E.164 format, of the Rev user.\\n\\nrev_orgstringOptional`format: \"id\"`\\n\\nThe ID of the Rev organization to which the created Rev user is associated.\\n\\ncustom_schema_fragmentslist of stringsOptionalDeprecated\\n\\nThe schema fragment IDs associated with the Rev",
"title": "Create Rev User — DevRev | Docs"
},
{
"id": "ART-15443_KNOWLEDGE_NODE-8",
"text": "ref is a mutable unique identifier for a user within the\\nDev organization from your primary customer record. If none is\\navailable, a good alternative is the email address/phone number\\nwhich could uniquely identify the user. If none is specified, a\\nsystem-generated identifier will be assigned to the user.\\n\\nphone\\\\_numberslist of stringsOptional\\n\\nPhone numbers, in E.164 format, of the Rev user.\\n\\nrev\\\\_orgstringOptional`format: \"id\"`\\n\\nThe ID of the Rev organization to which the created",
"title": "Create Rev User | DevRev | Docs"
},
{
"id": "ART-2575_KNOWLEDGE_NODE-30",
"text": "CSV import feature currently supports a maximum of 500 rows per request. For larger datasets, split the CSV into smaller files containing up to 500 rows each.\\n\\nTroubleshooting\\n---------------\\n\\nThe following table describes the errors you may encounter during import and how to troubleshoot them:\\n\\n| Error | Resolution |\\n| --- | --- |\\n| Invalid format for phone numbers | Validate the phone number is in E164 Format. For example, +12014631690. |\\n| Tags not found in organization |",
"title": "Account and contact import | Computer for Growth Teams | DevRev"
},
{
"id": "ART-1566_KNOWLEDGE_NODE-410",
"text": "If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\n\\nphone_numbers list of strings Optional\\n\\nPhone numbers, in E.164 format, of the Rev user.\\n\\nrev_org string Optional\\n\\nThe ID of the Rev organization to which the created Rev user is associated.\\n\\ntags list of objects Optional\\n\\nTags associated with the Rev user.\\n\\nShow 2",
"title": "Transition (Beta) — DevRev | Docs"
},
{
"id": "ART-4102_KNOWLEDGE_NODE-4",
"text": "value of the Rev user.\\n\\nphone_numberslist of stringsOptional\\n\\nThe phone numbers, in E.164 format, of the Rev user.\\n\\n### Response\\n\\nUpdated Rev user object.\\n\\nrev_userobject\\n\\nShow 16 properties\\n\\n### Errors\\n\\n400\\n\\nBad Request Error\\n\\n401\\n\\nUnauthorized Error\\n\\n403\\n\\nForbidden Error\\n\\n404\\n\\nNot Found Error\\n\\n409\\n\\nConflict Error\\n\\n429\\n\\nToo Many Requests Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nPOST\\n\\n/rev-users.update\\n\\n[code]\\n\\n",
"title": "Update Rev User — DevRev | Docs"
},
{
"id": "ART-15506_KNOWLEDGE_NODE-9",
"text": "used for sending email notifications of any support messages. | string | \\xe2\\x9d\\x8c | \\xe2\\x9c\\x85 |\\n| `display_name`\\\\* | The name of the user that\\xe2\\x80\\x99s shown on the widget. If nothing is specified, a system-generated name is assigned to the user. | string | \\xe2\\x9d\\x8c | \\xe2\\x9d\\x8c |\\n| `phone_numbers` | The customer\\xe2\\x80\\x99s mobile number, which must adhere to the E.164 format. | array | \\xe2\\x9d\\x8c | \\xe2\\x9d\\x8c |\\n\\n* While email uniqueness is subjected to organization",
"title": "Identify your users with Plug | DevRev | Docs"
},
{
"id": "ART-1545_KNOWLEDGE_NODE-408",
"text": "If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\n\\nphone_numbers list of strings Optional\\n\\nPhone numbers, in E.164 format, of the Rev user.\\n\\nrev_org string Optional\\n\\nThe ID of the Rev organization to which the created Rev user is associated.\\n\\ntags list of objects Optional\\n\\nTags associated with the Rev user.\\n\\nShow 2",
"title": "Create (Beta) — DevRev | Docs"
},
{
"id": "ART-1651_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1654_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1633_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1305_KNOWLEDGE_NODE-360",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1837_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1825_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1649_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1653_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1826_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1611_KNOWLEDGE_NODE-3",
"text": "email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\n\\nphone_numberslist of stringsOptional\\n\\nPhone numbers, in E.164 format, of the Rev user.\\n\\nrev_orgstringOptional\\n\\nThe ID of the Rev organization to which the created Rev user is associated.\\n\\ntagslist of objectsOptional\\n\\nTags associated with the Rev user.\\n\\nShow 2 properties\\n\\ncustom_schema_fragmentslist of",
"title": "Create Rev User (Beta) — DevRev | Docs"
},
{
"id": "ART-1560_KNOWLEDGE_NODE-410",
"text": "organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\n\\nphone_numbers list of strings Optional\\n\\nPhone numbers, in E.164 format, of the Rev user.\\n\\nrev_org string Optional\\n\\nThe ID of the Rev organization to which the created Rev user is associated.\\n\\ntags list of objects Optional\\n\\nTags associated",
"title": "Assign (Beta) — DevRev | Docs"
},
{
"id": "ART-1558_KNOWLEDGE_NODE-407",
"text": "organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\n\\nphone_numbers list of strings Optional\\n\\nPhone numbers, in E.164 format, of the Rev user.\\n\\nrev_org string Optional\\n\\nThe ID of the Rev organization to which the created Rev user is associated.\\n\\ntags list of objects Optional\\n\\nTags associated",
"title": "Metric Definitions List (Beta) — DevRev | Docs"
},
{
"id": "ART-1597_KNOWLEDGE_NODE-360",
"text": "record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of objects Optional\\nTags associated with the Rev user.\\nShow 2",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1577_KNOWLEDGE_NODE-361",
"text": "record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of objects Optional\\nTags associated with the Rev user.\\nShow 2",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1592_KNOWLEDGE_NODE-358",
"text": "alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of objects Optional\\nTags associated with the Rev user.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-15440_KNOWLEDGE_NODE-8",
"text": "picture.\\n\\nemailstringOptional`format: \"text\"`\\n\\nUpdated email address of the Rev user.\\n\\nexternal\\\\_refstringOptional`format: \"text\"`\\n\\nUpdated external ref value of the Rev user.\\n\\nphone\\\\_numberslist of stringsOptional\\n\\nThe phone numbers, in E.164 format, of the Rev user.\\n\\n### Response\\n\\nUpdated Rev user object.\\n\\nrev\\\\_userobject\\n\\nShow 16 properties\\n\\n### Errors\\n\\n400\\n\\nBad Request Error\\n\\n401\\n\\nUnauthorized Error\\n\\n403\\n\\nForbidden Error\\n\\n404\\n\\nNot Found",
"title": "Update Rev User | DevRev | Docs"
},
{
"id": "ART-1641_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1830_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1833_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1650_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1822_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1838_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1655_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1827_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1303_KNOWLEDGE_NODE-358",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "Export Post — DevRev | Docs"
},
{
"id": "ART-1782_KNOWLEDGE_NODE-355",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1652_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1579_KNOWLEDGE_NODE-354",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1643_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1636_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1828_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1832_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1836_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1831_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1306_KNOWLEDGE_NODE-358",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1835_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1509_KNOWLEDGE_NODE-355",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "Prepare — DevRev | Docs"
},
{
"id": "ART-1824_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1639_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "Export Post — DevRev | Docs"
},
{
"id": "ART-1593_KNOWLEDGE_NODE-361",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1637_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1787_KNOWLEDGE_NODE-357",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1834_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1829_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1609_KNOWLEDGE_NODE-358",
"text": "address of the Rev user.\\nexternal_ref string Optional\\nExternal ref is a mutable unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1805_KNOWLEDGE_NODE-358",
"text": "and mutable.\\nemail string Optional\\nEmail address of the Rev user.\\nexternal_ref string Optional\\nExternal ref is a mutable unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1823_KNOWLEDGE_NODE-353",
"text": "unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1801_KNOWLEDGE_NODE-359",
"text": "and mutable.\\nemail string Optional\\nEmail address of the Rev user.\\nexternal_ref string Optional\\nExternal ref is a mutable unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1791_KNOWLEDGE_NODE-356",
"text": "and mutable.\\nemail string Optional\\nEmail address of the Rev user.\\nexternal_ref string Optional\\nExternal ref is a mutable unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev",
"title": "Self Delete — DevRev | Docs"
},
{
"id": "ART-1575_KNOWLEDGE_NODE-361",
"text": "and mutable.\\nemail string Optional\\nEmail address of the Rev user.\\nexternal_ref string Optional\\nExternal ref is a mutable unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1792_KNOWLEDGE_NODE-359",
"text": "identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of objects Optional\\nTags associated with the Rev user.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_user object\\nShow 22 properties\\nAPI Reference rev-users",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1821_KNOWLEDGE_NODE-358",
"text": "and mutable.\\nemail string Optional\\nEmail address of the Rev user.\\nexternal_ref string Optional\\nExternal ref is a mutable unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1591_KNOWLEDGE_NODE-359",
"text": "and mutable.\\nemail string Optional\\nEmail address of the Rev user.\\nexternal_ref string Optional\\nExternal ref is a mutable unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1780_KNOWLEDGE_NODE-356",
"text": "identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of objects Optional\\nTags associated with the Rev user.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_user object\\nShow 22 properties\\nAPI Reference rev-users",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1806_KNOWLEDGE_NODE-361",
"text": "identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of objects Optional\\nTags associated with the Rev user.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_user object\\nShow 22 properties\\nAPI Reference rev-users",
"title": "Self Post — DevRev | Docs"
},
{
"id": "ART-1789_KNOWLEDGE_NODE-357",
"text": "and mutable.\\nemail string Optional\\nEmail address of the Rev user.\\nexternal_ref string Optional\\nExternal ref is a mutable unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1786_KNOWLEDGE_NODE-356",
"text": "identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of objects Optional\\nTags associated with the Rev user.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_user object\\nShow 22 properties\\nAPI Reference rev-users",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1605_KNOWLEDGE_NODE-357",
"text": "identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of objects Optional\\nTags associated with the Rev user.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_user object\\nShow 22 properties\\nAPI Reference rev-users",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1308_KNOWLEDGE_NODE-358",
"text": "identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of objects Optional\\nTags associated with the Rev user.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_user object\\nShow 22 properties\\nAPI Reference rev-users",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1607_KNOWLEDGE_NODE-361",
"text": "in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of objects Optional\\nTags associated with the Rev user.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_user object\\nShow 22 properties\\nAPI Reference rev-users Delete.\\n\\nPOST https:// api.devrev.ai / rev-users.delete\\nDeletes a Rev user.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of Rev user to",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1300_KNOWLEDGE_NODE-357",
"text": "and mutable.\\nemail string Optional\\nEmail address of the Rev user.\\nexternal_ref string Optional\\nExternal ref is a mutable unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1590_KNOWLEDGE_NODE-358",
"text": "and mutable.\\nemail string Optional\\nEmail address of the Rev user.\\nexternal_ref string Optional\\nExternal ref is a mutable unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1788_KNOWLEDGE_NODE-357",
"text": "and mutable.\\nemail string Optional\\nEmail address of the Rev user.\\nexternal_ref string Optional\\nExternal ref is a mutable unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1781_KNOWLEDGE_NODE-355",
"text": "and mutable.\\nemail string Optional\\nEmail address of the Rev user.\\nexternal_ref string Optional\\nExternal ref is a mutable unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1783_KNOWLEDGE_NODE-355",
"text": "identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of objects Optional\\nTags associated with the Rev user.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_user object\\nShow 22 properties\\nAPI Reference rev-users",
"title": "Locate — DevRev | Docs"
},
{
"id": "ART-4100_KNOWLEDGE_NODE-4",
"text": "set, then \\xe2\\x80\\x9cafter\\xe2\\x80\\x9d is used.\\n\\nAllowed values: afterbefore\\n\\nmodified_date.afterstringOptional`format: \"date-time\"`\\n\\nFilters for objects created after the provided timestamp (inclusive).\\n\\nmodified_date.beforestringOptional`format: \"date-time\"`\\n\\nFilters for objects created before the provided timestamp (inclusive).\\n\\nphone_numberslist of stringsOptional\\n\\nList of phone numbers, in E.164 format, to filter Rev users on.\\n\\nrev_orglist of stringsOptional\\n\\nList of IDs",
"title": "List Rev Users — DevRev | Docs"
},
{
"id": "ART-1802_KNOWLEDGE_NODE-361",
"text": "identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of objects Optional\\nTags associated with the Rev user.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_user object\\nShow 22 properties\\nAPI Reference rev-users",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1304_KNOWLEDGE_NODE-360",
"text": "identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of objects Optional\\nTags associated with the Rev user.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_user object\\nShow 22 properties\\nAPI Reference rev-users",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1595_KNOWLEDGE_NODE-357",
"text": "and mutable.\\nemail string Optional\\nEmail address of the Rev user.\\nexternal_ref string Optional\\nExternal ref is a mutable unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1803_KNOWLEDGE_NODE-358",
"text": "and mutable.\\nemail string Optional\\nEmail address of the Rev user.\\nexternal_ref string Optional\\nExternal ref is a mutable unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1804_KNOWLEDGE_NODE-361",
"text": "identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of objects Optional\\nTags associated with the Rev user.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_user object\\nShow 22 properties\\nAPI Reference rev-users",
"title": "Self — DevRev | Docs"
},
{
"id": "ART-1818_KNOWLEDGE_NODE-358",
"text": "and mutable.\\nemail string Optional\\nEmail address of the Rev user.\\nexternal_ref string Optional\\nExternal ref is a mutable unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev",
"title": "Sla Trackers Get Post — DevRev | Docs"
},
{
"id": "ART-1790_KNOWLEDGE_NODE-356",
"text": "identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of objects Optional\\nTags associated with the Rev user.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_user object\\nShow 22 properties\\nAPI Reference rev-users",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1307_KNOWLEDGE_NODE-358",
"text": "and mutable.\\nemail string Optional\\nEmail address of the Rev user.\\nexternal_ref string Optional\\nExternal ref is a mutable unique identifier for a user within the Dev organization from your primary customer record. If none is available, a good alternative is the email address/phone number which could uniquely identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1301_KNOWLEDGE_NODE-361",
"text": "identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of objects Optional\\nTags associated with the Rev user.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_user object\\nShow 22 properties\\nAPI Reference rev-users",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1779_KNOWLEDGE_NODE-357",
"text": "identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of objects Optional\\nTags associated with the Rev user.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_user object\\nShow 22 properties\\nAPI Reference rev-users",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1302_KNOWLEDGE_NODE-361",
"text": "identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of objects Optional\\nTags associated with the Rev user.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_user object\\nShow 22 properties\\nAPI Reference rev-users",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1785_KNOWLEDGE_NODE-355",
"text": "identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of objects Optional\\nTags associated with the Rev user.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_user object\\nShow 22 properties\\nAPI Reference rev-users",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1620_KNOWLEDGE_NODE-2",
"text": "of the Rev user.\\n\\ndisplay_namestringOptional\\n\\nUpdated display name of the Rev user.\\n\\nemailstringOptional\\n\\nUpdated email address of the Rev user.\\n\\nexternal_refstringOptional\\n\\nUpdated external ref value of the Rev user.\\n\\nphone_numberslist of stringsOptional\\n\\nThe phone numbers, in E.164 format, of the Rev user.\\n\\ntagslist of objectsOptional\\n\\nTags associated with the Rev user.\\n\\nShow 2 properties\\n\\n### Response\\n\\nUpdated Rev user object.\\n\\nrev_userobject\\n\\nShow 22",
"title": "Update Rev User (Beta) — DevRev | Docs"
},
{
"id": "ART-1784_KNOWLEDGE_NODE-355",
"text": "identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of objects Optional\\nTags associated with the Rev user.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_user object\\nShow 22 properties\\nAPI Reference rev-users",
"title": "Locate Post — DevRev | Docs"
},
{
"id": "ART-1819_KNOWLEDGE_NODE-359",
"text": "identify the user. If none is specified, a system-generated identifier will be assigned to the user.\\nphone_numbers list of strings Optional\\nPhone numbers, in E.164 format, of the Rev user.\\nrev_org string Optional\\nThe ID of the Rev organization to which the created Rev user is associated.\\ntags list of objects Optional\\nTags associated with the Rev user.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nrev_user object\\nShow 22 properties\\nAPI Reference rev-users",
"title": "Sla Trackers Get — DevRev | Docs"
},
{
"id": "ART-1302_KNOWLEDGE_NODE-367",
"text": "default is \\'50\\'.\\nmode \"after\" or \"before\" Optional\\nThe iteration mode to use, otherwise if not set, then \"after\" is used.\\nAllowed values: after before\\nmodified_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\nmodified_date.before datetime Optional\\nFilters for objects created before the provided timestamp (inclusive).\\nphone_numbers string Optional\\nList of phone numbers, in E.164 format, to filter Rev users on.\\nrev_org string",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1304_KNOWLEDGE_NODE-366",
"text": "default is \\'50\\'.\\nmode \"after\" or \"before\" Optional\\nThe iteration mode to use, otherwise if not set, then \"after\" is used.\\nAllowed values: after before\\nmodified_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\nmodified_date.before datetime Optional\\nFilters for objects created before the provided timestamp (inclusive).\\nphone_numbers string Optional\\nList of phone numbers, in E.164 format, to filter Rev users on.\\nrev_org string",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1786_KNOWLEDGE_NODE-362",
"text": "default is \\'50\\'.\\nmode \"after\" or \"before\" Optional\\nThe iteration mode to use, otherwise if not set, then \"after\" is used.\\nAllowed values: after before\\nmodified_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\nmodified_date.before datetime Optional\\nFilters for objects created before the provided timestamp (inclusive).\\nphone_numbers string Optional\\nList of phone numbers, in E.164 format, to filter Rev users on.\\nrev_org string",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1804_KNOWLEDGE_NODE-367",
"text": "default is \\'50\\'.\\nmode \"after\" or \"before\" Optional\\nThe iteration mode to use, otherwise if not set, then \"after\" is used.\\nAllowed values: after before\\nmodified_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\nmodified_date.before datetime Optional\\nFilters for objects created before the provided timestamp (inclusive).\\nphone_numbers string Optional\\nList of phone numbers, in E.164 format, to filter Rev users on.\\nrev_org string",
"title": "Self — DevRev | Docs"
},
{
"id": "ART-1819_KNOWLEDGE_NODE-365",
"text": "default is \\'50\\'.\\nmode \"after\" or \"before\" Optional\\nThe iteration mode to use, otherwise if not set, then \"after\" is used.\\nAllowed values: after before\\nmodified_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\nmodified_date.before datetime Optional\\nFilters for objects created before the provided timestamp (inclusive).\\nphone_numbers string Optional\\nList of phone numbers, in E.164 format, to filter Rev users on.\\nrev_org string",
"title": "Sla Trackers Get — DevRev | Docs"
},
{
"id": "ART-1785_KNOWLEDGE_NODE-361",
"text": "default is \\'50\\'.\\nmode \"after\" or \"before\" Optional\\nThe iteration mode to use, otherwise if not set, then \"after\" is used.\\nAllowed values: after before\\nmodified_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\nmodified_date.before datetime Optional\\nFilters for objects created before the provided timestamp (inclusive).\\nphone_numbers string Optional\\nList of phone numbers, in E.164 format, to filter Rev users on.\\nrev_org string",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1779_KNOWLEDGE_NODE-363",
"text": "default is \\'50\\'.\\nmode \"after\" or \"before\" Optional\\nThe iteration mode to use, otherwise if not set, then \"after\" is used.\\nAllowed values: after before\\nmodified_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\nmodified_date.before datetime Optional\\nFilters for objects created before the provided timestamp (inclusive).\\nphone_numbers string Optional\\nList of phone numbers, in E.164 format, to filter Rev users on.\\nrev_org string",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1780_KNOWLEDGE_NODE-362",
"text": "default is \\'50\\'.\\nmode \"after\" or \"before\" Optional\\nThe iteration mode to use, otherwise if not set, then \"after\" is used.\\nAllowed values: after before\\nmodified_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\nmodified_date.before datetime Optional\\nFilters for objects created before the provided timestamp (inclusive).\\nphone_numbers string Optional\\nList of phone numbers, in E.164 format, to filter Rev users on.\\nrev_org string",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1605_KNOWLEDGE_NODE-363",
"text": "default is \\'50\\'.\\nmode \"after\" or \"before\" Optional\\nThe iteration mode to use, otherwise if not set, then \"after\" is used.\\nAllowed values: after before\\nmodified_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\nmodified_date.before datetime Optional\\nFilters for objects created before the provided timestamp (inclusive).\\nphone_numbers string Optional\\nList of phone numbers, in E.164 format, to filter Rev users on.\\nrev_org string",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1790_KNOWLEDGE_NODE-362",
"text": "default is \\'50\\'.\\nmode \"after\" or \"before\" Optional\\nThe iteration mode to use, otherwise if not set, then \"after\" is used.\\nAllowed values: after before\\nmodified_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\nmodified_date.before datetime Optional\\nFilters for objects created before the provided timestamp (inclusive).\\nphone_numbers string Optional\\nList of phone numbers, in E.164 format, to filter Rev users on.\\nrev_org string",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1308_KNOWLEDGE_NODE-364",
"text": "default is \\'50\\'.\\nmode \"after\" or \"before\" Optional\\nThe iteration mode to use, otherwise if not set, then \"after\" is used.\\nAllowed values: after before\\nmodified_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\nmodified_date.before datetime Optional\\nFilters for objects created before the provided timestamp (inclusive).\\nphone_numbers string Optional\\nList of phone numbers, in E.164 format, to filter Rev users on.\\nrev_org string",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1783_KNOWLEDGE_NODE-361",
"text": "default is \\'50\\'.\\nmode \"after\" or \"before\" Optional\\nThe iteration mode to use, otherwise if not set, then \"after\" is used.\\nAllowed values: after before\\nmodified_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\nmodified_date.before datetime Optional\\nFilters for objects created before the provided timestamp (inclusive).\\nphone_numbers string Optional\\nList of phone numbers, in E.164 format, to filter Rev users on.\\nrev_org string",
"title": "Locate — DevRev | Docs"
},
{
"id": "ART-1301_KNOWLEDGE_NODE-367",
"text": "default is \\'50\\'.\\nmode \"after\" or \"before\" Optional\\nThe iteration mode to use, otherwise if not set, then \"after\" is used.\\nAllowed values: after before\\nmodified_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\nmodified_date.before datetime Optional\\nFilters for objects created before the provided timestamp (inclusive).\\nphone_numbers string Optional\\nList of phone numbers, in E.164 format, to filter Rev users on.\\nrev_org string",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1802_KNOWLEDGE_NODE-367",
"text": "default is \\'50\\'.\\nmode \"after\" or \"before\" Optional\\nThe iteration mode to use, otherwise if not set, then \"after\" is used.\\nAllowed values: after before\\nmodified_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\nmodified_date.before datetime Optional\\nFilters for objects created before the provided timestamp (inclusive).\\nphone_numbers string Optional\\nList of phone numbers, in E.164 format, to filter Rev users on.\\nrev_org string",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1806_KNOWLEDGE_NODE-367",
"text": "default is \\'50\\'.\\nmode \"after\" or \"before\" Optional\\nThe iteration mode to use, otherwise if not set, then \"after\" is used.\\nAllowed values: after before\\nmodified_date.after datetime Optional\\nFilters for objects created after the provided timestamp (inclusive).\\nmodified_date.before datetime Optional\\nFilters for objects created before the provided timestamp (inclusive).\\nphone_numbers string Optional\\nList of phone numbers, in E.164 format, to filter Rev users on.\\nrev_org string",
"title": "Self Post — DevRev | Docs"
}
] |
53fcc51d-3606-4333-8f58-71d868c4db28
|
tickets created through plug customer workspace assignment customer account set
|
[
{
"id": "ART-2002_KNOWLEDGE_NODE-32",
"text": "get resolved and matched when the same customer engages with you on the Plug widget for a support interaction.\\n\\nThis is achieved by using the *external reference* provided by you when creating customer identity.\\n\\n**External reference for a customer**\\nA unique identifier for an end user from your primary customer record. The system uses this to resolve a newly created customer with customers already in the system. \\nIf none is available, a good alternative is the email address or phone",
"title": "Contacts | Computer for Growth Teams | DevRev"
},
{
"id": "ART-2000_KNOWLEDGE_NODE-31",
"text": "domain. If none is specified, a system-generated identifier is assigned to the account.\\n\\n![]()\\n\\nFor ingestion channels where providing an external reference isn't possible, the system relies on custom logic to identify and match incoming customer identity.\\n\\n> Example: The Slack and Email integration uses a combination of the customer email and workspace domain\\\\_name values. WhatsApp uses the WhatsApp number and associated name.\\n\\nAdd a workspace\\n---------------\\n\\nTo add a workspace to",
"title": "Accounts | Computer for Growth Teams | DevRev"
},
{
"id": "ART-1976_KNOWLEDGE_NODE-28",
"text": "scenarios\\n----------------------------\\n\\n* Ticket routing based on customer inquiry keywords.\\n* Group-specific routing based on customer account assignments.\\n* Assignment routing based on severity and subtype.\\n* Custom field and tag-based routing.\\n* First responder ticket assignment.\\n\\nSystem requirements\\n-------------------\\n\\n* Administrator privileges are required for workflow deployment and execution.\\n* User status (active/away) is configurable through the profile",
"title": "Routing | Computer for Support Teams | DevRev"
},
{
"id": "ART-3235_KNOWLEDGE_NODE-25",
"text": "one.\\n\\nInstallation\\n------------\\n\\nInstall the [Reported by Enricher](https://marketplace.devrev.ai/ticket-reported-by) from DevRev marketplace.\\n\\nConfiguration\\n-------------\\n\\nIn the **Configuration** tab, the following settings are available:\\n\\n* **Custom Email Field**: Specify the backend name of the custom field where the email is entered when creating a ticket.\\n* **Default Account**: Select the account to which new customers should be linked if they do not already exist in the",
"title": "Reported by enricher | Automate | Snap-ins | DevRev"
},
{
"id": "ART-16264_KNOWLEDGE_NODE-29",
"text": "account.\\n + If both **Reported By** and **Account** fields are initially empty, you can search for and add any contact to the **Reported By** field, which will auto-fill the **Account** and **Workspace** (if applicable).\\n* **Handling multiple users:**\\n\\n + If all selected users within the **Reported By** field belong to the same workspace, the **Workspace** field remains unchanged.\\n + If users are from different workspaces, the **Workspace** field is emptied, while the **Account** field",
"title": "June 2025 | Changelog | DevRev"
},
{
"id": "ART-2039_KNOWLEDGE_NODE-25",
"text": "create DevRev tickets from Marker.io issues, you can configure the\\nsnap-in to use this email to auto-fill the **Reported By** and **Customer\\nWorkspace** fields in tickets. If no contact or accounts match the email, they\\nare automatically created.\\n\\nInstalling the Marker.io integration snap-in\\n--------------------------------------------\\n\\n1. Install the [Marker.io](/marketplace/marker-io) from the\\n DevRev Marketplace.\\n2. Configure the snap-in as needed.\\n\\n * (Optional) Select the",
"title": "Marker.io | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-15506_KNOWLEDGE_NODE-19",
"text": "\\xe2\\x9c\\x85 | If neither exists: System creates the account first, then creates the workspace. User is linked to both. If account exists but workspace doesn\\xe2\\x80\\x99t: System creates the workspace under the existing account. User is linked to both. If workspace exists under different account: System returns an error, as workspaces cannot be a part of 2 accounts. |\\n| \\xe2\\x9c\\x85 | \\xe2\\x9d\\x8c | If workspace doesn\\xe2\\x80\\x99t exist: System creates a new account and workspace (if needed).",
"title": "Identify your users with Plug | DevRev | Docs"
},
{
"id": "ART-15506_KNOWLEDGE_NODE-18",
"text": "doesn\\xe2\\x80\\x99t exist, the system automatically creates the user.\\n\\nThis approach ensures efficient management and integration of objects within the DevOrg.\\n\\n| Workspace Ref | Account Ref | Results |\\n| --- | --- | --- |\\n| \\xe2\\x9d\\x8c | \\xe2\\x9c\\x85 | (Most common Usage) \\\\nIf the account doesn\\xe2\\x80\\x99t exist: An account is created, and the user is linked with the account. |\\n| \\xe2\\x9d\\x8c | \\xe2\\x9d\\x8c | No action on account or workspace. The user is returned. |\\n| \\xe2\\x9c\\x85 |",
"title": "Identify your users with Plug | DevRev | Docs"
},
{
"id": "ART-2895_KNOWLEDGE_NODE-10",
"text": "The mobile number of the customer.| array \\n \\n**Attributes for workspaces**\\n\\nAttributes| Description| Type \\n---|---|--- \\n`workspace_ref`| A unique reference for the user\\xe2\\x80\\x99s workspace. If not provided, and an account reference is passed, the user is directly attached to the account.| string \\n`display_name`| The name of the workspace that\\xe2\\x80\\x99s shown on the widget.| string \\n \\n**Attributes for accounts**\\n\\nAttributes| Description| Type \\n---|---|---",
"title": "Identify your users with PLuG — DevRev | Docs"
},
{
"id": "ART-3235_KNOWLEDGE_NODE-24",
"text": "[Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Reported by enricher](/docs/automations/ticket-reported-by)\\n\\nReported by enricher\\n====================\\n\\nThe [Reported by Enricher](https://marketplace.devrev.ai/ticket-reported-by) snap-in automatically updates the **Reported By** field on tickets created with an email entered in a custom field. It verifies if the email belongs to an existing customer of the configured account and either links to that customer or creates a new",
"title": "Reported by enricher | Automate | Snap-ins | DevRev"
}
] |
25130283-382e-4ee0-9e98-be02d9b70e89
|
slash command from devrev mobile app
|
[
{
"id": "ART-1969_KNOWLEDGE_NODE-28",
"text": "engineers. To get a list of the available commands, type / in a conversation response text box.\\n\\n\\xf0\\x9f\\x8e\\xab Tickets\\n---------\\n\\nThe benefit of Computer by DevRev is that conversations can be linked to support [tickets](../product/tickets), and tickets can be linked to build issues. This [linkage](../product/apps) means that all work can be traced back to customer concerns or requests.\\n\\nSlash commands are available in tickets to provide AI assistance to customer experience engineers.",
"title": "Computer for Support Teams | DevRev"
}
] |
81bb4437-4f69-45dc-80c0-14766089e803
|
Audit trails for all access and modification activities
|
[
{
"id": "ART-2718_KNOWLEDGE_NODE-0",
"text": "b'Fetch Audit Logs | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nBeta\\n\\nBeta\\n\\nBeta\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/beta/api-reference/accounts/create)[compliance](/beta/api-reference/compliance/export-audit-logs)\\n\\nFetch Audit Logs\\n================\\n\\nBeta\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/audit-logs.fetch\\n\\nPOST\\n\\n/audit-logs.fetch\\n\\ncURL\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/audit-logs.fetch \\\\ |\\n| > | -H",
"title": "Fetch Audit Logs | DevRev | Docs"
},
{
"id": "ART-2718_KNOWLEDGE_NODE-1",
"text": "\"Authorization: Bearer <token>\" \\\\ |\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{ |\\n| > | \"from\": \"2023-01-01T12:00:00.000Z\", |\\n| > | \"to\": \"2023-01-01T12:00:00.000Z\" |\\n| > | }\\' |\\n```\\n\\n[Try it](/beta/api-reference/compliance/export-audit-logs?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | {} |\\n```\\n\\nRetrieves audit logs.\\n\\n### Headers\\n\\nAuthorizationstringRequired\\n\\nBearer authentication of the form `Bearer <token>`, where token is your auth",
"title": "Fetch Audit Logs | DevRev | Docs"
},
{
"id": "ART-2718_KNOWLEDGE_NODE-2",
"text": "token.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\nfromstringRequired`format: \"date-time\"`\\n\\nTime from which logs are to be retrieved.\\n\\ntostringRequired`format: \"date-time\"`\\n\\nTime till which logs are to be retrieved.\\n\\ncategorieslist of stringsOptional\\n\\nCategories of the logs to filter by.\\n\\noperation\\\\_typeslist of enumsOptional\\n\\nOperation type to filter the logs by.\\n\\nAllowed values:createdeleteotherreadupdate\\n\\n### Response\\n\\nResponse for the audit logs export",
"title": "Fetch Audit Logs | DevRev | Docs"
},
{
"id": "ART-15792_KNOWLEDGE_NODE-7",
"text": "Import and interact with objects from connected applications, protected by SOC 2 Type 2 compliance and secured with detailed audit trails.\\n\\nSource: [DevRev Search](https://devrev.ai/search)DevRev Products\\n\\nDevRev sells the following products:SupportWhat is DevRev Support?\\n\\nDevRev Support is a full-featured support platform built for modern businesses and trusted by leading organizations\\n\\nKey Features:\\n\\nInstant answers: Provide instant, accurate answers to customer questions wherever",
"title": "DevRev Products and Agents"
},
{
"id": "ART-888_KNOWLEDGE_NODE-7",
"text": "DevRev App, to understand the users\\xe2\\x80\\x99 needs and to make our service better suited to those needs. Such usage data does not identify you personally.The application logs that are corresponding to the activities you do on app.devrev.ai as a logged-in user. These logs will be tracked against your corresponding DevRev identity for auditing and troubleshooting purposes.When you sign up or/ sign in to the app.devrev.ai from an external identity provider, we store a persistence reference to",
"title": "Privacy Policy"
}
] |
349af6dc-1210-43cd-8421-490039d13c00
|
SLA breach calculation and response time policy
|
[
{
"id": "ART-1986_KNOWLEDGE_NODE-26",
"text": "level.\\nSLAs help ensure that your customers receive timely responses and resolutions to inquiries.\\n\\nPolicy users can set SLA breach and warning targets for three metrics: *first response*, *next response*, and *full resolution*. Each metric has its own breach and warning target. You can specify whether the metrics are calculated using calendar hours or business hours while defining breach and warning targets.\\n\\nCreate an SLA\\n-------------\\n\\n1. Go to **Settings > SLA > + Create**.\\n2. In",
"title": "Service-level agreement | Computer for Support Teams | DevRev"
},
{
"id": "ART-1986_KNOWLEDGE_NODE-33",
"text": "calculation\\n----------------------\\n\\nSLA metrics are calculated based on the policy that's applied to the conversation or the ticket. There can be one or more SLA metrics active on a given conversation or a ticket, with each one being tracked separately.\\n\\nSLA metric can be in one of the following stages:\\n\\n* *Active*: The metric is currently being tracked on the conversation or ticket.\\n* *Close to breach*: The time spent by the SLA metric is greater than or equal to the close to breach",
"title": "Service-level agreement | Computer for Support Teams | DevRev"
},
{
"id": "ART-1986_KNOWLEDGE_NODE-35",
"text": "of schedule when they remain at the same stage, but time spent out of schedule isn't included in the calculation.\\n\\n![]()\\n\\nIf the customer account is updated after the ticket is created, all SLA metrics will be recalculated based on the updated customer account information. Any previous SLA breaches or achievements will be discarded, and new calculations will be applied according to the updated SLA.\\n\\nThe following table describes how each metric works for tickets and",
"title": "Service-level agreement | Computer for Support Teams | DevRev"
},
{
"id": "ART-2695_KNOWLEDGE_NODE-27",
"text": "**Metrics**. Install the [OLA metrics for issues](https://marketplace.devrev.ai/ola-metric-on-issues) snap-in as prompted to access the **Issue Resolution Time** metric, see [Defining OLA Metrics](#defining-ola-metrics) for details.\\n3. Click **Continue**.\\n\\nYou can set breach and warning targets for **Issue Resolution Time** by selecting between calendar or business hours for calculation. Multiple policies can be created within an OLA, and they are applied based on priority if an issue meets",
"title": "Operational-level agreement | Computer for Support Teams | DevRev"
},
{
"id": "ART-1986_KNOWLEDGE_NODE-34",
"text": "target defined in the policy.\\n* *Breached*: The time spent by the SLA metric is greater than or equal to the breach target defined in the policy.\\n* *Paused*: The metric is currently paused based on some conditions. For example, when a ticket moves to awaiting customer response.\\n* *Completed*: The conversation or ticket has reached the completion condition.\\n\\nBased on business hours defined for an organization, *Active/Close to breach/Breached* metrics can change schedules. Metrics move out",
"title": "Service-level agreement | Computer for Support Teams | DevRev"
},
{
"id": "ART-2695_KNOWLEDGE_NODE-33",
"text": "meets or exceeds the close-to-breach target set in the policy.\\n* **Breached**: The time spent meets or exceeds the breach target set in the policy.\\n* **Paused**: The metric is paused based on stage conditions in the snap-in.\\n* **Completed**: The *stop* condition has been met.\\n\\nMetrics in the *Active*, *Close to Breach*, or *Breached* stages may follow business hours, moving in and out of schedule without including out-of-schedule time in calculations.\\n\\nIn the **Detailed** view, all",
"title": "Operational-level agreement | Computer for Support Teams | DevRev"
},
{
"id": "ART-4172_KNOWLEDGE_NODE-13",
"text": "24 Business Hours |\\n\\n*Business Days: Monday - Friday (Saturday and Sunday coverage provided for incidents only)* \\n*Response commitments remain void for the region during the holidays mentioned below, except for incidents*\\n\\n*\\\\*No SLA promised on tickets other than BUGS*\\n\\n### 3. Support Channels\\n\\n* Chat ([www.DevRev.ai](http://www.devrev.ai/) | [https://app.DevRev.ai](https://app.devrev.ai/))\\n* Email ([[email protected]](mailto:[email protected]))\\n* Support Portal",
"title": "DevRev Service Level Agreement"
}
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.