query_id
stringlengths 36
36
| query
stringlengths 20
119
| retrievals
listlengths 1
126
|
|---|---|---|
0ae94217-c6a0-4895-83a2-841a95f01637
|
create DevRev ticket from Microsoft Teams
|
[
{
"id": "ART-4216_KNOWLEDGE_NODE-26",
"text": "DevRev Object | Sync to DevRev |\\n| --- | --- | --- |\\n| Plan | Parts | \\xe2\\x9c\\x85 |\\n| User | Identity/DevUser | \\xe2\\x9c\\x85 |\\n| Channel | Chat | \\xe2\\x9c\\x85 |\\n| Attachments in Message/Thread/Task | Artifacts on Article | \\xe2\\x9c\\x85 |\\n| Message | Comment | \\xe2\\x9c\\x85 |\\n| Thread | Comment | \\xe2\\x9c\\x85 |\\n| Task | Issue/Ticket | \\xe2\\x9c\\x85 |\\n\\nImporting from Microsoft Teams\\n------------------------------\\n\\nFollow the steps below to import from Microsoft Teams:\\n\\n1. Go to",
"title": "Microsoft Teams AirSync | AirSync | Snap-ins | DevRev"
},
{
"id": "ART-4216_KNOWLEDGE_NODE-29",
"text": "with many\\nattachments. DevRev honors the Microsoft Graph API rate limits and back-off and resumes automatically.\\n\\nPost import options\\n-------------------\\n\\nAfter a successful import, you have the following options available for the imported account:\\n\\n* **Sync to DevRev** \\n This option allows you to synchronize any modifications made in Microsoft Teams with the corresponding items previously imported into DevRev. It also creates new items in DevRev for any new data in Microsoft Teams",
"title": "Microsoft Teams AirSync | AirSync | Snap-ins | DevRev"
}
] |
d0b209b3-6cea-46d8-bfac-bd0e286ea21b
|
workflow builder auto close ticket after 48 hours no customer response
|
[
{
"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-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"
}
] |
40c1aa6f-cd21-46ab-8f6f-76fdc267b584
|
automated reminder to customer ticket will be closed in 4 days
|
[
{
"id": "ART-3068_KNOWLEDGE_NODE-24",
"text": "[Documentation](/docs)\\n3. [Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Conversation reminder](/docs/automations/conversation-reminder)\\n\\nConversation reminder\\n=====================\\n\\nThe Conversation Reminder Snap-in is designed to automatically send a\\nnotification to the customer who initiated the conversation if it remains in\\n\"Waiting on User\" stage for an extended period, as defined in the configured\\ntime settings. The notification message sent to the customer can be",
"title": "Conversation reminder | Automate | Snap-ins | DevRev"
},
{
"id": "ART-3068_KNOWLEDGE_NODE-25",
"text": "customized\\nduring the installation of the Snap-in, allowing for tailored communication\\naccording to specific requirements.\\n\\n![]()\\n\\nFor more information, refer to the\\n[Conversation Reminder snap-in](https://marketplace.devrev.ai/conversation-reminder)\\non the DevRev marketplace.\\n\\nInstalling the auto parts to conversation snap-in\\n-------------------------------------------------\\n\\n1. In DevRev, go to **Settings** > **Snap-ins** and click **Explore\\n Marketplace** in the top-right",
"title": "Conversation reminder | Automate | Snap-ins | DevRev"
},
{
"id": "ART-1284_KNOWLEDGE_NODE-16",
"text": "false |\\n| 20 | end |\\n| 21 | else false |\\n| 22 | end |\\n```\\n\\nScheduled events\\n----------------\\n\\n`flow-events` are an event source that snap-ins can use to publish or schedule events directly. This event source can then be used to trigger another automation. This capability makes it ideal for building snap-ins that need to act later. For example, sending reminders to issues still in the *Triage* stage.\\n\\nYou create an event source of type `flow-events`, and from your snap-in, you call",
"title": "Event sources | DevRev | Docs"
}
] |
e47d883f-b712-4f98-bd06-14ade143e3c2
|
connect Bitbucket account to DevRev account
|
[
{
"id": "ART-2030_KNOWLEDGE_NODE-27",
"text": "**Explore Marketplace** in the top-right corner.\\n2. In the DevRev marketplace, find **Bitbucket for DevRev** and click **Install**.\\n3. During the snap-in installation, follow the instructions for installing the webhook. The webhook can be installed for an entire Bitbucket org or specific repositories. If you install the webhook successfully, the message \"Webhook installed successfully\" is displayed in the\\xc2\\xa0**Discussions**\\xc2\\xa0tab. If it was not installed correctly, you could see",
"title": "Bitbucket | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2030_KNOWLEDGE_NODE-26",
"text": "IDE.\\n* **Autotrack work**: Automatically track your work in DevRev even without creating an issue ahead of time.\\n* **PR task creation**: Create DevRev tasks for PR reviewers.\\n* **PR reminders**: Automatically remind PR reviewers when a PR goes stale.\\n\\n![]()\\n\\nFor more information, refer to the\\n[Bitbucket for DevRev snap-in](https://marketplace.devrev.ai/bitbucket) on the DevRev marketplace.\\n\\nInstallation\\n------------\\n\\n1. In DevRev, go to **Settings** > **Snap-ins** and click",
"title": "Bitbucket | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2030_KNOWLEDGE_NODE-40",
"text": "to\\xc2\\xa0**Settings**\\xc2\\xa0>\\xc2\\xa0**Account**\\xc2\\xa0>\\xc2\\xa0**External Identities**\\xc2\\xa0and\\xc2\\xa0**Link Bitbucket Account**.\\n\\nPR reminders\\n------------\\n\\nPRs can often go stale and delay the development process. With PR reminders, developers can be automatically notified when a PR has been inactive for a period of time.\\n\\nTo make use of this feature, the following conditions must be met:\\n\\n1. Enable the **Send reminders for inactive PRs** feature in the\\xc2\\xa0snap-in in your",
"title": "Bitbucket | Integrate | Snap-ins | DevRev"
}
] |
2e6f9413-15ac-4974-a380-7aa22fc98a61
|
use of workflows in DevRev
|
[
{
"id": "ART-1961_KNOWLEDGE_NODE-28",
"text": "workflow engine.\\n* **Automations on one schema**: Our AirSync feature automatically transforms data from different sources. It enables you to create workflows natively in DevRev without the need to create fetch nodes or manually transform data.\\n\\nComponents\\n----------\\n\\n* Workflow canvas: The field where you connect and visualize different steps in your workflow.\\n* Steps: The building blocks of your workflow, shown on the canvas.\\n* Variable selector: Used to insert variables into your",
"title": "Workflows | Computer by DevRev | DevRev"
},
{
"id": "ART-1961_KNOWLEDGE_NODE-24",
"text": "[Creating a workflow](#creating-a-workflow)\\n* [Workflow example: Ticket auto-response](#workflow-example-ticket-autoresponse)\\n\\n1. [Documentation](/docs)\\n3. [Computer by DevRev](/docs/intro)\\n[Workflows](/docs/product/workflow-engine)\\n\\nWorkflows\\n=========\\n\\nA workflow is a series of triggers, actions, and conditions designed to achieve a specific goal or outcome. Depicted as a flowchart or diagram, it illustrates how various triggers and actions interconnect.\\n\\nDevRev\\xe2\\x80\\x99s",
"title": "Workflows | Computer by DevRev | DevRev"
},
{
"id": "ART-4179_KNOWLEDGE_NODE-3",
"text": "the DevRev ecosystem.](https://devrevu.reach360.com/share/course/676d4cd1-0520-45bd-813d-8289d0fc8772)[![]()\\n\\nDevRev: Customizations and snap-ins\\n\\nExtend DevRev by building custom experiences for your workflow](https://devrevu.reach360.com/share/course/6dea13c5-5e05-46bd-bf2b-e29f4fca130c)[![]()\\n\\nDevRev: Workflows and automations\\n\\nDesign workflows and automations that drive productivity at",
"title": "DevRev University"
},
{
"id": "ART-2076_KNOWLEDGE_NODE-3",
"text": "the DevRev ecosystem.](https://devrevu.reach360.com/share/course/676d4cd1-0520-45bd-813d-8289d0fc8772)[![]()\\n\\nDevRev: Customizations and snap-ins\\n\\nExtend DevRev by building custom experiences for your workflow](https://devrevu.reach360.com/share/course/6dea13c5-5e05-46bd-bf2b-e29f4fca130c)[![]()\\n\\nDevRev: Workflows and automations\\n\\nDesign workflows and automations that drive productivity at",
"title": "DevRev University"
},
{
"id": "ART-3038_KNOWLEDGE_NODE-9",
"text": "workflows in DevRev to automatically categorize work. They connected GitHub effortlessly, enabling stage changes to update without manual effort. With Dev360, integrated directly into DevRev, they analyze developer productivity and track velocity in real time. They also rely on advanced project tracking inside our app to manage large-scale engineering initiatives with greater visibility.\\n\\nTogether, these integrations and capabilities embody the convergence of Dev + Rev, giving Bolt a single",
"title": "Bolt unifies support and product to deliver seamless commerce"
},
{
"id": "ART-15716_KNOWLEDGE_NODE-32",
"text": "issues, or custom objects) is supported via the DevRev API.\\n\\nYou can use the API to create, update, or reorder stages in your workflow.\\n\\nThe endpoint and payload depend on the object type (ticket, issue, custom object, etc.).\\n\\nIf you share which object\\xe2\\x80\\x99s stages you want to customize, I can provide a sample API call or payload.Analytics and Reporting\\n\\n1. Creating Reports in DevRev\\n\\nYou can create reports in DevRev by building dashboards with widgets:\\n\\nGo to the Vista you",
"title": "Support queries related playbook"
},
{
"id": "ART-16784_KNOWLEDGE_NODE-19",
"text": "[https://devrev.ai/docs/product/core](https://devrev.ai/docs/product/core)vista\\n\\nA list of objects in DevRev that you can sort, categorize, and share.\\n\\nRead more about vista: [https://devrev.ai/docs/product/vistas](https://devrev.ai/docs/product/vistas)workflow\\n\\nA series of triggers, actions, and conditions designed to achieve a specific goal or outcome.\\n\\nDepicted as a flowchart or diagram, a workflow illustrates how various triggers and actions interconnect.\\n\\nRead more about",
"title": "Glossary"
},
{
"id": "ART-1961_KNOWLEDGE_NODE-33",
"text": "account.\\n\\n**Ask AI**\\n\\nWrite your own LLM prompt to generate content that can be used in various contexts. For example, you can request a summary of a ticket based on the title and description.\\n\\nCreating a workflow\\n-------------------\\n\\n1. Go to [**Settings** > **Workflows**](https://app.devrev.ai/devrev/settings/workflows?labels=skill&labelsOp=not_any&status=active). A canvas appears.\\n2. Enter a name for your workflow.\\n3. Select the steps you want to include by selecting them from the",
"title": "Workflows | Computer by DevRev | DevRev"
},
{
"id": "ART-1710_KNOWLEDGE_NODE-9",
"text": "everyone in real time. This transparency has improved decision-making and operational efficiency across the organization. DevRev\\xe2\\x80\\x99s seamless migration and workflow creation have eliminated the need for external automations, Jira connectors, and additional Slack integrations. We now conduct our meetings by screen sharing the DevRev app, sorting and grouping columns, and voila, we have the information we want to present, reducing the time spent on operational tasks.\\n\\n![]()\\n\\nJishnu",
"title": "Yellow.ai uses DevRev to Streamline Processes"
},
{
"id": "ART-16784_KNOWLEDGE_NODE-20",
"text": "workflow: [https://devrev.ai/docs/product/workflow-engine](https://devrev.ai/docs/product/workflow-engine)workspace\\n\\nThe customer of a product or service.\\n\\nRead more about workspace: [https://devrev.ai/docs/product/customers](https://devrev.ai/docs/product/customers)'",
"title": "Glossary"
},
{
"id": "ART-17181_KNOWLEDGE_NODE-8",
"text": "notifications, while going far beyond with advanced workflows, SLA management, automation, and hybrid search functionality. The platform empowered agents to build automations themselves without relying on product teams, with Raj noting that a typical ticket lifecycle requires approximately 15 workflows, which DevRev makes practical and manageable.\\n\\nKey implementation highlights included a Lumary integration that automated customer association in 15 seconds for approximately 30% of APAC ticket",
"title": "Skedulo reduced effort 30% to 5% and unlocked automation at scale"
},
{
"id": "ART-4179_KNOWLEDGE_NODE-2",
"text": "applications](https://rise.articulate.com/share/yTvcdwN0dMgzhiU_Kgbbs2t8lfkpnC5O)[![]()\\n\\nDevRev: Admin management and set-up\\n\\nSet up, manage, and streamline workflows for smooth operations](https://devrevu.reach360.com/share/course/d238d6fd-ab6a-41b3-a99b-44e1d2a8d221)\\n\\nExplore more courses\\n--------------------\\n\\nDiscover more courses to expand your DevRev skills and continue your learning journey\\n\\n[![]()\\n\\nDevRev platform fundamentals\\n\\nYour first step to navigating and mastering",
"title": "DevRev University"
},
{
"id": "ART-2076_KNOWLEDGE_NODE-2",
"text": "applications](https://rise.articulate.com/share/yTvcdwN0dMgzhiU_Kgbbs2t8lfkpnC5O)[![]()\\n\\nDevRev: Admin management and set-up\\n\\nSet up, manage, and streamline workflows for smooth operations](https://devrevu.reach360.com/share/course/d238d6fd-ab6a-41b3-a99b-44e1d2a8d221)\\n\\nExplore more courses\\n--------------------\\n\\nDiscover more courses to expand your DevRev skills and continue your learning journey\\n\\n[![]()\\n\\nDevRev platform fundamentals\\n\\nYour first step to navigating and mastering",
"title": "DevRev University"
},
{
"id": "ART-1945_KNOWLEDGE_NODE-29",
"text": "such as Slack and Jira. Automations perform tasks within DevRev based on events, like responding to customer conversations and linking tickets and issues. [AirSync](./import) helps you bring data from external sources to DevRev and keep them in sync.\\n\\nWhile numerous snap-ins are available and more are in development, you can create your own using [DevRev APIs](https://developer.devrev.ai/about/for-developers).\\n\\n[PreviousIntroduction](/docs)[NextCore concepts](/docs/product/core)\\n\\n#### On",
"title": "Computer by DevRev | DevRev"
},
{
"id": "ART-1027_KNOWLEDGE_NODE-9",
"text": "workflows** that streamline ticket triaging and severity assessment.\\n\\n### AI-powered deflection at scale\\n\\nAI answering has stabilized around 32\\xe2\\x80\\x9340% of all inquiries, with complex queries intelligently routed to human agents. **Computer CX Agents** for free vs. paid customers optimize deflection strategies for each segment, delivering tailored support while maximizing efficiency.\\n\\nDevRev has enabled us to streamline access to technical documentation, automate common developer",
"title": "Descope streamlines support at scale with automation, AI, and unified collaboration"
},
{
"id": "ART-12391_KNOWLEDGE_NODE-27",
"text": "workflow.\\n\\nNow, your workflow runs whenever a conversation or a ticket gets created and it\\nassigns it to an AI agent, which handles the conversation. No brittle rules.\\n\\nFind below a detailed explanation of all the fields needed to configure in the\\n\"Talk to Agent\" Step\\n\\n| Parameter | Type | Description |\\n| --- | --- | --- |\\n| agent | String | ID of the AI agent to use. Use the dropdown to select one. |\\n| object | String | ID of the conversation or ticket where the agent operate.s |\\n|",
"title": "Conversational workflows | Workflows | Computer by DevRev | DevRev"
},
{
"id": "ART-1961_KNOWLEDGE_NODE-30",
"text": "Action: Tasks that modify one or more objects in the system.\\n* Control: Conditional (if-then) blocks to determine which actions to take based on an operand (variable) and an operator.\\n* Delay: Wait to take an action.\\n\\nAI nodes\\n--------\\n\\nWe provide several native AI nodes out of the box to enhance your workflows.\\n\\n**Spam checker**\\n\\nThe spam checker takes the ID of a ticket or object and determines whether the ticket or conversation is spam. You can use this output in your workflows as",
"title": "Workflows | Computer by DevRev | DevRev"
},
{
"id": "ART-15617_KNOWLEDGE_NODE-12",
"text": "systems\\n\\nDevRev : AI-powered search draws on past conversations and external data\\n\\nDevRev : Built-in AI can dedupe, cluster, classify, route, generate, and attribute information\\n\\nPylon : AI agents constrained to internal data only, no external system access\\n\\nCustom Workflows\\n\\nDevRev : AI decision nodes for intelligent workflow routing based on context\\n\\nDevRev : No-code workflow building with simple prompts and easy import capabilities\\n\\nDevRev : Track customer sentiment in",
"title": "Pylon - Competitive - for the PLuG on website"
},
{
"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-1036_KNOWLEDGE_NODE-12",
"text": "\\xe2\\x80\\x93 workflows for automation and sentiment-based prioritization\\n* Computer Memory \\xe2\\x80\\x93 unified knowledge graph\\n* Knowledge base management with Smart Import capabilities\\n* Team inbox for customer conversations\\n* Automated ticket creation and management\\n* Unified platform for conversations, tickets, and issues\\n* Native DevRev-Jira integration\\n* SLA management\\n* Role-based authorization\\n\\nDevRev not just helped implement their Support app but also guided us in improving",
"title": "Shipsy elevates logistics support with AI-powered automation and cross team collaboration"
},
{
"id": "ART-12390_KNOWLEDGE_NODE-25",
"text": "library\\n=======================\\n\\nWhen a workflow starts running, the action steps define which operations or\\nprocesses occur and specify any data that needs to be transferred between\\nblocks. Below is a list the action steps you can use.\\n\\nObject creation\\n---------------\\n\\n| Operation | Description | Input Parameters | Output |\\n| --- | --- | --- | --- |\\n| Create Account | Creates a new account in DevRev. | * Account details like name, description, domains, etc. * subtype: (Optional)",
"title": "Workflow action library | Workflows | Computer by DevRev | DevRev"
},
{
"id": "ART-1960_KNOWLEDGE_NODE-44",
"text": "about\\xc2\\xa0[*vista*](https://docs.devrev.ai/product/vistas)\\n\\nworkflow\\n\\n: A series of triggers, actions, and conditions designed to achieve a specific goal or outcome.\\n: Depicted as a flowchart or diagram, a workflow illustrates how various triggers and actions interconnect.\\n: Read more about\\xc2\\xa0[*workflow*](https://devrev.ai/docs/product/workflow-engine)\\n\\nworkspace\\n\\n: The customer of a product or service.\\n: Read more",
"title": "Glossary | Computer by DevRev | DevRev"
},
{
"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"
}
] |
84fac619-f780-4343-960b-1b6c735f4c1f
|
workflow send email when boolean field set to true
|
[
{
"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"
}
] |
09ff15cd-16ce-457d-ab30-56dc3d9f3f37
|
recorded training session on Ticket-SLA Analytics
|
[
{
"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"
}
] |
f520802b-15ce-461b-a05c-9273a103d7da
|
session missing when user sends video recording
|
[
{
"id": "ART-4186_KNOWLEDGE_NODE-43",
"text": "app.\\n* Unlike web sessions, there is **no time limit** on session length.\\n* A session contains multiple **recordings**:\\n + A **recording** ends when the app is backgrounded.\\n + A **new recording** starts when the app comes to the foreground again.\\n + The **session ends** when the app is killed, or it crashes, or it becomes non-responsive, or after 30 mins of inactivity.\\n + Sessions are **uploaded** the next time the app is launched.\\n\\nSession Analytics: Mobile dashboard consists of",
"title": "Computer for User Insights | Session analytics | Computer for Your Customers | DevRev"
},
{
"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-15513_KNOWLEDGE_NODE-33",
"text": "`DevRev.startRecording()` | Starts the session recording. |\\n| `DevRev.stopRecording()` | Ends the session recording and uploads it to the portal. |\\n| `DevRev.pauseRecording()` | Pauses the ongoing session recording. |\\n| `DevRev.resumeRecording()` | Resumes a paused session recording. |\\n| `DevRev.processAllOnDemandSessions()` | Stops the ongoing user recording and sends all on-demand sessions along with the current recording. |\\n\\nUsing this property returns the status of the session",
"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-15515_KNOWLEDGE_NODE-33",
"text": "|\\n| `DevRev.pauseRecording()` | Pauses the ongoing session recording. |\\n| `DevRev.resumeRecording()` | Resumes a paused session recording. |\\n| `DevRev.processAllOnDemandSessions()` | Stops the ongoing user recording and sends all on-demand sessions along with the current recording. |\\n\\nYou can also check the following flags for session recording:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | // Check if session recording is currently active. |\\n| 2 | let isRecording = DevRev.isRecording |\\n| 3 |",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-12398_KNOWLEDGE_NODE-33",
"text": "enable_session_recording: true,\\n\\n\\n\\n5 session_recording_options: {\\n\\n\\n\\n6 sessionDetails: {\\n\\n\\n\\n7 sessionId: sessionId,\\n\\n\\n\\n8 tabId: tabId,\\n\\n\\n\\n9 },\\n\\n\\n\\n10 },\\n\\n\\n\\n11 });\\n```\\n\\nShow more\\n```\\n\\nYou can leave the tabId empty if you want to track this domain as a separate tab within the same session.\\n\\n![]()\\n\\nIf the session identifiers passed to the Plug method correspond to a session which has already ended, or some invalid identifiers, the SDK",
"title": "Cross-domain session tracking | Session analytics | Computer for Your Customers | DevRev"
},
{
"id": "ART-4255_KNOWLEDGE_NODE-19",
"text": "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.| pauseRecording()| pauseRecording(DevRev.INSTANCE); \\nResumes a paused session recording.| resumeRecording()| resumeRecording(DevRev.INSTANCE); \\n \\n### Session properties\\n\\nYou can add custom properties to the session recording to help you understand the context of the",
"title": "DevRev SDK for Android — 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-4256_KNOWLEDGE_NODE-14",
"text": "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 record user interactions with your app.\\n\\n#####\\n\\nThe session recording feature is opt-out and",
"title": "DevRev SDK for React Native — DevRev | Docs"
},
{
"id": "ART-15507_KNOWLEDGE_NODE-28",
"text": "`DevRev.pauseRecording()` | Pauses the ongoing session recording. |\\n| `DevRev.resumeRecording()` | Resumes a paused session recording. |\\n| `DevRev.processAllOnDemandSessions()` | Stops the ongoing user recording and sends all on-demand sessions along with the current recording. |\\n\\n### Session properties\\n\\nYou can add custom properties to the session recording to help you understand the context of the session. The properties are defined as a map of string values.\\n\\n```\\n| | |\\n| --- |",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-2664_KNOWLEDGE_NODE-27",
"text": "your\\n [website](https://developer.devrev.ai/sdks/web/installation) or\\n [mobile app](https://developer.devrev.ai/sdks/mobile).\\n2. For web applications, configure\\n [user identification](https://developer.devrev.ai/sdks/web/user-identity).\\n3. Enable session recording for your users, go to **Settings** > **PluG and Portal** >\\n **Session Replays** and enable recording for your desired platform.\\n\\n **Note**: Alternatively, you can enable session recording during Plug SDK\\n",
"title": "Session analytics | Computer for Your Customers | DevRev"
},
{
"id": "ART-16579_KNOWLEDGE_NODE-29",
"text": "recording. |\\n| `DevRev.stopRecording()` | Ends the session recording and uploads it to the portal. |\\n| `DevRev.pauseRecording()` | Pauses the ongoing session recording. |\\n| `DevRev.resumeRecording()` | Resumes a paused session recording. |\\n| `DevRev.processAllOnDemandSessions()` | Stops the ongoing session recording and uploads all offline sessions on demand, including the current one. |\\n\\n### Session properties\\n\\nYou can add custom properties to the session recording to help you",
"title": "Features | 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-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-15506_KNOWLEDGE_NODE-28",
"text": "calling the `shutdown()` method will stop the ongoing session recording. Re-initializing with the `init()` method will then start a new session recording. To avoid losing continuity, you can pass the details of the ongoing session recording when re-initializing Plug.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | // Get the ongoing session details |\\n| 2 | const { sessionId, tabId } = window.plugSDK.getSessionDetails(); |\\n| 3 | |\\n| 4 | if (window.plugSDK.isPlugInitialized) { |\\n| 5 |",
"title": "Identify your users with Plug | DevRev | Docs"
},
{
"id": "ART-15506_KNOWLEDGE_NODE-29",
"text": "window.plugSDK.shutdown(); |\\n| 6 | } |\\n| 7 | window.plugSDK.init({ |\\n| 8 | app_id: appId, |\\n| 9 | |\\n| 10 | // Pass the session details |\\n| 11 | session_recording_options: { |\\n| 12 | sessionDetails: { |\\n| 13 | sessionId: sessionId, |\\n| 14 | tabId: tabId, |\\n| 15 | }, |\\n| 16 | }, |\\n| 17 | |\\n| 18 | // With session token |\\n| 19 | session_token: sessionToken, |\\n| 20 | // Or without session token |\\n| 21 | identity: {}, |\\n| 22 | }); |\\n```\\n\\nWas this page",
"title": "Identify your users with Plug | DevRev | Docs"
},
{
"id": "ART-4257_KNOWLEDGE_NODE-20",
"text": "Action \\n---|--- \\n`DevRev.startRecording()`| Starts the session recording. \\n`DevRev.stopRecording()`| Ends the session recording and uploads it to the portal. \\n`DevRev.pauseRecording()`| Pauses the ongoing session recording. \\n`DevRev.resumeRecording()`| Resumes a paused session recording. \\n \\n### Session properties\\n\\nYou can add custom properties to the session recording to help you understand the context of the session. The properties are defined as a dictionary of string",
"title": "DevRev SDK for iOS — DevRev | Docs"
},
{
"id": "ART-15515_KNOWLEDGE_NODE-34",
"text": "|\\n| 4 | // Check if session monitoring is enabled. |\\n| 5 | let isMonitoringEnabled = DevRev.isMonitoringEnabled |\\n| 6 | |\\n| 7 | // Check if on-demand sessions are enabled. |\\n| 8 | let areOnDemandSessionsEnabled = DevRev.areOnDemandSessionsEnabled |\\n```\\n\\n### Session properties\\n\\nYou can add custom properties to the session recording to help you understand the context of the session. The properties are defined as a dictionary of string values.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 |",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-2895_KNOWLEDGE_NODE-2",
"text": "view their past conversations. Identifying your users also enables more personalized engagement.\\n\\nIn this flow, you have to generate a session token for every user who visits your website. The session token identifies the customer when they interact with the widget. The session token is generated using the application access token and customer information. It should be generated on your website\\xe2\\x80\\x99s back end since the app token needs to be kept hidden.\\n\\nTo identify logged-in users,",
"title": "Identify your users with PLuG — DevRev | Docs"
},
{
"id": "ART-15509_KNOWLEDGE_NODE-5",
"text": "(True or False) |\\n| `session_recording_key` | Identifies your session recording account and is required to enable the SDK session recording features. | String |\\n| `enable_session_recording` | Instructs the widget to determine whether to start the session recording. | Boolean (True or False) |\\n| `session_token` | Identifies the user interacting with your app. | String |\\n| `primary_text_color` | The color of the launcher, button text for new tickets and conversations, conversation user text,",
"title": "Methods | DevRev | Docs"
},
{
"id": "ART-12398_KNOWLEDGE_NODE-27",
"text": "method to fetch these ids.\\n\\n```\\n```\\n1 const { sessionId, tabId } = window.plugSDK.getSessionDetails();\\n```\\n```\\n\\n![]()\\n\\nTo ensure that the session recording features are ready before calling getSessionDetails, wait on the ON\\\\_OBSERVABILITY\\\\_READY Plug event. For more information about this event, refer to the [methods reference](https://developer.devrev.ai/public/sdks/web/methods).\\n\\n```\\n```\\n1 window.plugSDK.onEvent(payload => {\\n\\n\\n\\n2 if (payload.type ===",
"title": "Cross-domain session tracking | Session analytics | Computer for Your Customers | DevRev"
},
{
"id": "ART-15506_KNOWLEDGE_NODE-3",
"text": "engagement.\\n\\nTo implement user identification, you need to generate a session token for each user who visits your website. This token is created using your application access token combined with customer information, and must be generated on your backend to keep the application token secure.\\n\\nDevRev\\'s BackendYour BackendYour FrontendYour UserDevRev\\'s BackendYour BackendYour FrontendYour User(1) User is known(via Signup, Login)(2) Send user details(3) auth-tokens.create API call(4) Return",
"title": "Identify your users with Plug | DevRev | Docs"
},
{
"id": "ART-2897_KNOWLEDGE_NODE-24",
"text": "\"Credit Card\", \\n 6| \"expiry_date\" : \"2024-12-12\" \\n 7| } \\n 8| window.plugSDK.trackEvent(\"signed_up\",properties)\\n[/code] \\n \\nTo learn more about tracking events, visit [Track events](/public/sdks/web/track-events).\\n\\n## Restart session recording\\n\\nThe `restartSessionRecording` method is used to restart session recording.\\n\\n[code]\\n\\n 1| window.plugSDK.restartSessionRecording(); \\n ---|---\\n[/code] \\n \\nWas this page helpful?YesNo\\n\\n[Custom implementationUp",
"title": "Methods — DevRev | Docs"
},
{
"id": "ART-2898_KNOWLEDGE_NODE-17",
"text": "DevRev SDK offers session analytics features to help you understand how users interact with your app.\\n\\n### Opt in or out\\n\\nEnd users can opt in or out of the session analytics feature, enabling them to control whether their interactions are tracked for 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",
"title": "Android integration — DevRev | Docs"
},
{
"id": "ART-15506_KNOWLEDGE_NODE-27",
"text": "|\\n| 1 | // Delete the existing Plug instance if it exists |\\n| 2 | if (window.plugSDK.isPlugInitialized) { |\\n| 3 | window.plugSDK.shutdown(); |\\n| 4 | } |\\n| 5 | |\\n| 6 | // Re-initialize Plug |\\n| 7 | window.plugSDK.init({ |\\n| 8 | app_id: appId, |\\n| 9 | |\\n| 10 | // With session token |\\n| 11 | session_token: sessionToken, |\\n| 12 | |\\n| 13 | // Or without session token |\\n| 14 | identity: {}, |\\n| 15 | }); |\\n```\\n\\nIf you\\xe2\\x80\\x99re using the Plug SDK for recording user sessions,",
"title": "Identify your users with Plug | DevRev | Docs"
},
{
"id": "ART-2897_KNOWLEDGE_NODE-6",
"text": "\\n`enable_default_launcher`| Show/hide the default PLuG widget launcher.| Boolean (True or False) \\n`session_recording_key`| Identifies your session recording account and is required to enable the SDK session recording features.| String \\n`enable_session_recording`| Instructs the widget to determine whether to start the session recording.| Boolean (True or False) \\n`session_token`| Identifies the user interacting with your app.| String \\n`primary_text_color`| The color of the launcher,",
"title": "Methods — DevRev | Docs"
}
] |
743b1f32-0db4-4a68-8d8e-c689592f7cca
|
email notifications not received after specific time
|
[
{
"id": "ART-2027_KNOWLEDGE_NODE-45",
"text": "due to mail loops, the email integration has the provision to specify user-specific email limits. By default, the user-specific limit is set to 30 emails per 10 minutes.\\n\\nIf a user sends 30 emails in a 10-minute time frame, this particular user is marked with the tag spammer. Once marked as a spammer, the user can only send 100 emails in a 24-hour period. All of these emails are marked as spam by the system. Any emails beyond the 100 spam email default limit are dropped, and the blocked tag",
"title": "Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-3207_KNOWLEDGE_NODE-56",
"text": "deliverable.\\n\\n5. Events Panel\\n---------------\\n\\nLocated in the top right of the Email Integration page, this opens a side panel with:\\n\\n* **Key Email Events** such as Delivery failures (bounces), Spam flagging (rate-limit violations), etc.\\n* **Internal discussion**: Collaborators can comment on specific events for shared visibility and debugging\\n\\n[PreviousEmail](/docs/integrations/email)[NextExotel](/docs/integrations/exotel)\\n\\n#### On this page\\n\\n* [1. Create a new",
"title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-3068_KNOWLEDGE_NODE-24",
"text": "[Documentation](/docs)\\n3. [Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Conversation reminder](/docs/automations/conversation-reminder)\\n\\nConversation reminder\\n=====================\\n\\nThe Conversation Reminder Snap-in is designed to automatically send a\\nnotification to the customer who initiated the conversation if it remains in\\n\"Waiting on User\" stage for an extended period, as defined in the configured\\ntime settings. The notification message sent to the customer can be",
"title": "Conversation reminder | Automate | Snap-ins | DevRev"
},
{
"id": "ART-16790_KNOWLEDGE_NODE-2",
"text": "to.Preferences\\n\\nHow do I change my timezone?\\n\\nGo to Settings > Preferences and look for the Timezone section. Click on the dropdown menu to search and select your preferred timezone. This affects when you receive reminders, notifications, and emails.Organization Settings\\n\\nWho can access organization settings? Organization settings are typically available to administrators who can manage team information, including the organization name, URL, data location, and member access",
"title": "Computer Settings and Preferences FAQs"
}
] |
0def0eb5-ac35-4294-8376-58f156f3c83c
|
enable sorting by a custom field in ticketing system
|
[
{
"id": "ART-1645_KNOWLEDGE_NODE-36",
"text": "fragments aren\\xe2\\x80\\x99t listed in the response.\\n\\n## Configure UI hints\\n\\nUI hints allow customizing the UI/UX of custom fields. So far, `ui.display_name` has been used to set the display name of a field. Let\\xe2\\x80\\x99s look at the other supported UI hints:\\n\\n * `display_name`: The display name of the field.\\n\\n * `is_hidden`: Whether the field is hidden.\\n\\n * `placeholder`: The placeholder text for the field.\\n\\n * `is_sortable`: Whether the field is sortable. Requires",
"title": "Object customization (Beta) — DevRev | Docs"
},
{
"id": "ART-15487_KNOWLEDGE_NODE-34",
"text": "hints\\n------------------\\n\\nUI hints allow customizing the UI/UX of custom fields. So far, `ui.display_name` has\\nbeen used to set the display name of a field. Let\\xe2\\x80\\x99s look at the other supported UI\\nhints:\\n\\n* `display_name`: The display name of the field.\\n* `is_hidden`: Whether the field is hidden.\\n* `placeholder`: The placeholder text for the field.\\n* `is_sortable`: Whether the field is sortable. Requires `is_filterable` to be true.\\n* `is_groupable`: Whether the field is",
"title": "Object customization | DevRev | Docs"
},
{
"id": "ART-15332_KNOWLEDGE_NODE-4",
"text": "\"group_name\": \"string\", |\\n| 46 | \"is_groupable\": true, |\\n| 47 | \"is_hidden\": true, |\\n| 48 | \"is_sortable\": true, |\\n| 49 | \"order\": 1, |\\n| 50 | \"placeholder\": \"string\", |\\n| 51 | \"tooltip\": \"string\", |\\n| 52 | \"unit\": \"string\", |\\n| 53 | \"use_shorthand_notation\": true |\\n| 54 | }, |\\n| 55 | \"default_value\": true |\\n| 56 | } |\\n| 57 | ], |\\n| 58 | \"description\": \"string\", |\\n| 59 | \"name\": \"string\" |\\n| 60 | } |\\n| 61 | ], |\\n| 62 | \"custom_fields\": [ |\\n| 63 | { |\\n| 64 | \"description\":",
"title": "Get Schemas Aggregated (POST) | DevRev | Docs"
},
{
"id": "ART-1957_KNOWLEDGE_NODE-33",
"text": "text**: Add a placeholder text that will be visible to the users before they enter an input.\\n * **Group name**: You can use a group name to create a group accordion for the chosen attributes.\\n * **Field visibility**: Choose how you want the field to be visible to users.\\n * **Field actionables**: Select actions that you can perform after creating a field such as grouping, filtering, and sorting.\\n * **Tooltip**: Add information about the field which will be visible when hovered",
"title": "Object customization | Computer by DevRev | DevRev"
}
] |
01661e52-e483-435f-aab5-3034a7f6c732
|
internal people can't see KB articles
|
[
{
"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-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-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"
},
{
"id": "ART-16192_KNOWLEDGE_NODE-29",
"text": "permissions in DevRev's articles. Only can read and can contribute permissions are imported from the knowledge base and articles.\\n* **Content & Metadata**: Imports published articles, including content, titles, dates, authors, and source URLs.\\n* **Version History**: Keeps track of published article versions.\\n* **Attachments**: Transfers files attached to articles and links them correctly.\\n* **User Criteria**: Imports users and group rules from ServiceNow.\\n\\n### Limitations\\n\\n* **Access",
"title": "ServiceNow KB AirSync | AirSync | Snap-ins | 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-1985_KNOWLEDGE_NODE-30",
"text": "additional settings for the article:\\n\\n * **Part** (required): Define the feature or capability the article addresses.\\n * **Owned by** (required): Assign a singular point of contact responsible for the article, aiding in management and ownership.\\n * **Status**: Indicate the current stage of the article.\\n * **Collection**: Categorize the article under a topic/theme in your customer portal.\\n * **Visible To**: Decide whether the article should be visible to all customers or only",
"title": "Articles | Knowledge Base | Computer for Support Teams | DevRev"
},
{
"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-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-17233_KNOWLEDGE_NODE-10",
"text": "\"Viewer\" |\\n| 19 | } |\\n| 20 | ] |\\n| 21 | }, |\\n| 22 | \"member_id\": { |\\n| 23 | \"refers_to\": { |\\n| 24 | \"#record:users\": {}, |\\n| 25 | \"#record:groups\": {}, |\\n| 26 | \"#record:platform_groups\": {} |\\n| 27 | } |\\n| 28 | } |\\n| 29 | } |\\n| 30 | } |\\n| 31 | } |\\n```\\n\\nArticle permissions\\n-------------------\\n\\nArticles in DevRev can be shared with individual users or groups, allowing for granular control over who can access what content.\\n\\n### Sharing mechanism\\n\\nThe `shared_with` field",
"title": "Permissions | DevRev | Docs"
},
{
"id": "ART-17230_KNOWLEDGE_NODE-5",
"text": "about products, services, and processes.\\nThey support both Markdown and HTML formats.\\n\\nArticles can include mentions to artifacts and other articles. Inline attachments must map to artifacts,\\nand article links must map to articles.\\n\\n### Managing permissions\\n\\nArticle permissions are managed through the `shared_with` field, which can reference users, groups, and platform groups.\\nRefer to the [permissions](/public/airsync/data-model/permissions) for more details.\\n\\n### Inline",
"title": "Rich text fields | DevRev | Docs"
},
{
"id": "ART-1545_KNOWLEDGE_NODE-23",
"text": "Optional\\n\\nFilters for articles modified by any of the provided users.\\n\\nowned_by string Optional\\n\\nFilters for articles owned by any of the provided users.\\n\\nscope long Optional\\n\\nFilter for the scope of the articles. If this is not provided, then only external articles are returned.\\n\\nshared_with.member string Optional\\n\\nID of the group/member with whom the item is shared.\\n\\nshared_with.role string Optional\\n\\nRole ID of the group/member with whom the item is",
"title": "Create (Beta) — DevRev | Docs"
},
{
"id": "ART-1780_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-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-1609_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-1823_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-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-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-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-1307_KNOWLEDGE_NODE-30",
"text": "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.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data",
"title": "List Post — 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-16192_KNOWLEDGE_NODE-31",
"text": "articles default to English in DevRev, regardless of the original language.\\n If a user in ServiceNow belongs to two different criteria\\xe2\\x80\\x94one allowing read and contribute access, and the other denying it\\xe2\\x80\\x94they may still have access in DevRev. However, if the same criteria appear in both the allow and deny lists for read and contribute access, the user is restricted in DevRev.\\n\\nPost import options\\n-------------------\\n\\nAfter a successful import, you have the following",
"title": "ServiceNow KB AirSync | AirSync | Snap-ins | DevRev"
},
{
"id": "ART-1834_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-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-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-1837_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"
}
] |
6fb80a79-6784-4b96-890b-763959422bbf
|
problem resume conversation with built in bot
|
[
{
"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-4206_KNOWLEDGE_NODE-8",
"text": "\"event\": { |\\n| > | \"input_message\": { |\\n| > | \"message\": \"Your query to the agent\" |\\n| > | } |\\n| > | }, |\\n| > | \"session_object\": \"unique_conversation_identifier\", |\\n| > | \"webhook_target\": { |\\n| > | \"webhook\": \"don:integration:dvrv-us-1:devo/0:webhook/auCJ7By8\" |\\n| > | }, |\\n| > | \"client_metadata\": { |\\n| > | \"user_id\": \"12345\", |\\n| > | \"conversation_id\": \"conv-789\" |\\n| > | } |\\n| > | }\\' |\\n```\\n\\n##### \\n\\nThe session\\\\_object parameter is critical for maintaining conversation",
"title": "Agents async API | DevRev | Docs"
},
{
"id": "ART-2895_KNOWLEDGE_NODE-2",
"text": "view their past conversations. Identifying your users also enables more personalized engagement.\\n\\nIn this flow, you have to generate a session token for every user who visits your website. The session token identifies the customer when they interact with the widget. The session token is generated using the application access token and customer information. It should be generated on your website\\xe2\\x80\\x99s back end since the app token needs to be kept hidden.\\n\\nTo identify logged-in users,",
"title": "Identify your users with PLuG — DevRev | Docs"
},
{
"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-27",
"text": "happens automatically:\\n\\n* The original conversation moves 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 + Equivalent metadata as the conversation, including source channel, customer account information, and external members added as **reported by** on the ticket\\n + An AI-generated ticket title and description based on customer messages\\n\\nConvert conversations to",
"title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev"
},
{
"id": "ART-1974_KNOWLEDGE_NODE-33",
"text": "have been addressed.\\n\\n A conversation set to *resolved* still shows in the end-user's widget. If they respond again, it reopens the conversation and set the status to *needs response*.\\n* *Archived*\\n\\n The final stage for conversation.\\n\\n[PreviousTicket-Team Performance](/docs/dashboards/ticket-team-performance)[NextConversation to ticket conversion](/docs/product/conversation-ticket)\\n\\n#### On this page\\n\\n* [Stages](#stages)\\n\\n[Enterprise grade security to protect customer",
"title": "Conversations | Computer for Support Teams | 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"
}
] |
14cd4d8e-c6b6-4e4f-9b87-a463ebc9efe6
|
PLuG stops responding to clients when they send a photo
|
[
{
"id": "ART-17220_KNOWLEDGE_NODE-10",
"text": "|\\n```\\n\\nDelay response (for rate limiting)\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | await adapter.emit(ExtractorEventType.ExtractionAttachmentsDelay, { |\\n| 2 | delay: \"30\", // Delay in seconds |\\n| 3 | }); |\\n```\\n\\nError response\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | await adapter.emit(ExtractorEventType.ExtractionAttachmentsError, { |\\n| 2 | error: \"Informative error message\", |\\n| 3 | }); |\\n```\\n\\n##### \\n\\nThe snap-in must always emit exactly one response event.\\n\\nWas this page",
"title": "Attachments extraction | DevRev | Docs"
},
{
"id": "ART-17220_KNOWLEDGE_NODE-9",
"text": "console.warn(\\'Failed attachment metadata\\', item); |\\n| 22 | } |\\n| 23 | |\\n| 24 | return { |\\n| 25 | error: { |\\n| 26 | message: `Failed to fetch attachment ${id} from URL.`, |\\n| 27 | }, |\\n| 28 | }; |\\n| 29 | } |\\n| 30 | } |\\n```\\n\\nEmitting responses\\n------------------\\n\\nThe snap-in must send exactly one response to AirSync when extraction is complete:\\n\\nSuccess response\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | await adapter.emit(ExtractorEventType.ExtractionAttachmentsDone);",
"title": "Attachments extraction | DevRev | Docs"
}
] |
59e823a3-bae5-43c1-afc7-a244f05f02cd
|
workflow trigger ticket severity blocker
|
[
{
"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-1549_KNOWLEDGE_NODE-506",
"text": "organizations.\\n\\nticket.severity enum Optional\\n\\nFilters for tickets with any of the provided severities.\\n\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\n\\nFilters for records with any of the provided SLA stages.\\n\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\n\\nFilters for tickets with any of the provided source channels.\\n\\nticket.subtype string Optional\\n\\nFilters for tickets with any of the provided",
"title": "List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1551_KNOWLEDGE_NODE-506",
"text": "organizations.\\n\\nticket.severity enum Optional\\n\\nFilters for tickets with any of the provided severities.\\n\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\n\\nFilters for records with any of the provided SLA stages.\\n\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\n\\nFilters for tickets with any of the provided source channels.\\n\\nticket.subtype string Optional\\n\\nFilters for tickets with any of the provided",
"title": "Update (Beta) — DevRev | Docs"
},
{
"id": "ART-1562_KNOWLEDGE_NODE-507",
"text": "organizations.\\n\\nticket.severity enum Optional\\n\\nFilters for tickets with any of the provided severities.\\n\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\n\\nFilters for records with any of the provided SLA stages.\\n\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\n\\nFilters for tickets with any of the provided source channels.\\n\\nticket.subtype string Optional\\n\\nFilters for tickets with any of the provided",
"title": "Get (Beta) — DevRev | Docs"
},
{
"id": "ART-1564_KNOWLEDGE_NODE-506",
"text": "organizations.\\n\\nticket.severity enum Optional\\n\\nFilters for tickets with any of the provided severities.\\n\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\n\\nFilters for records with any of the provided SLA stages.\\n\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\n\\nFilters for tickets with any of the provided source channels.\\n\\nticket.subtype string Optional\\n\\nFilters for tickets with any of the provided",
"title": "List (Beta) — DevRev | Docs"
},
{
"id": "ART-1543_KNOWLEDGE_NODE-505",
"text": "organizations.\\n\\nticket.severity enum Optional\\n\\nFilters for tickets with any of the provided severities.\\n\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\n\\nFilters for records with any of the provided SLA stages.\\n\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\n\\nFilters for tickets with any of the provided source channels.\\n\\nticket.subtype string Optional\\n\\nFilters for tickets with any of the provided",
"title": "Metric Definitions List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1547_KNOWLEDGE_NODE-507",
"text": "organizations.\\n\\nticket.severity enum Optional\\n\\nFilters for tickets with any of the provided severities.\\n\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\n\\nFilters for records with any of the provided SLA stages.\\n\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\n\\nFilters for tickets with any of the provided source channels.\\n\\nticket.subtype string Optional\\n\\nFilters for tickets with any of the provided",
"title": "Get Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1829_KNOWLEDGE_NODE-463",
"text": "the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the provided types.\\nAllowed values: issue",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1824_KNOWLEDGE_NODE-447",
"text": "the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the provided types.\\nAllowed values: issue",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1607_KNOWLEDGE_NODE-452",
"text": "the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the provided types.\\nAllowed values: issue",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1834_KNOWLEDGE_NODE-447",
"text": "organizations.\\nticket.severity enum Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1641_KNOWLEDGE_NODE-474",
"text": "organizations.\\nticket.severity enum Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1651_KNOWLEDGE_NODE-468",
"text": "Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1651_KNOWLEDGE_NODE-455",
"text": "the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the provided types.\\nAllowed values: issue",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1830_KNOWLEDGE_NODE-476",
"text": "Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1829_KNOWLEDGE_NODE-476",
"text": "Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1564_KNOWLEDGE_NODE-520",
"text": "severities.\\n\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\n\\nFilters for records with any of the provided SLA stages.\\n\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\n\\nFilters for tickets with any of the provided source channels.\\n\\nticket.subtype string Optional\\n\\nFilters for tickets with any of the provided subtypes.\\n\\ntype enum Optional\\n\\nFilters for work of the provided types.\\n\\nAllowed values:",
"title": "List (Beta) — DevRev | Docs"
},
{
"id": "ART-1551_KNOWLEDGE_NODE-520",
"text": "severities.\\n\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\n\\nFilters for records with any of the provided SLA stages.\\n\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\n\\nFilters for tickets with any of the provided source channels.\\n\\nticket.subtype string Optional\\n\\nFilters for tickets with any of the provided subtypes.\\n\\ntype enum Optional\\n\\nFilters for work of the provided types.\\n\\nAllowed values:",
"title": "Update (Beta) — DevRev | Docs"
},
{
"id": "ART-1824_KNOWLEDGE_NODE-460",
"text": "Optional\\nFilters for tickets with any of the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1549_KNOWLEDGE_NODE-520",
"text": "severities.\\n\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\n\\nFilters for records with any of the provided SLA stages.\\n\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\n\\nFilters for tickets with any of the provided source channels.\\n\\nticket.subtype string Optional\\n\\nFilters for tickets with any of the provided subtypes.\\n\\ntype enum Optional\\n\\nFilters for work of the provided types.\\n\\nAllowed values:",
"title": "List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1543_KNOWLEDGE_NODE-519",
"text": "severities.\\n\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\n\\nFilters for records with any of the provided SLA stages.\\n\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\n\\nFilters for tickets with any of the provided source channels.\\n\\nticket.subtype string Optional\\n\\nFilters for tickets with any of the provided subtypes.\\n\\ntype enum Optional\\n\\nFilters for work of the provided types.\\n\\nAllowed values:",
"title": "Metric Definitions List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-2009_KNOWLEDGE_NODE-27",
"text": "ticket is closed or reopened.\\n* Post in the linked conversation when a ticket is linked.\\n* Post in child issue timeline when parent issue is closed.\\n* Post in parent issue timeline when child issue is closed.\\n* Post to issue's timeline when linked ticket's severity is changed.\\n* Post in ticket's timeline when an issue linked to it is closed.\\n* Post in enhancement's timeline when any linked issue is *In Development*.\\n* Update ticket's stage when linked issue's state changes.\\n* Update",
"title": "Convergence | Automate | Snap-ins | DevRev"
},
{
"id": "ART-1301_KNOWLEDGE_NODE-452",
"text": "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 the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1786_KNOWLEDGE_NODE-447",
"text": "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 the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1804_KNOWLEDGE_NODE-452",
"text": "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 the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "Self — DevRev | Docs"
},
{
"id": "ART-1308_KNOWLEDGE_NODE-449",
"text": "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 the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1784_KNOWLEDGE_NODE-446",
"text": "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 the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "Locate Post — DevRev | Docs"
},
{
"id": "ART-1780_KNOWLEDGE_NODE-447",
"text": "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 the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1792_KNOWLEDGE_NODE-450",
"text": "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 the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1790_KNOWLEDGE_NODE-447",
"text": "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 the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1592_KNOWLEDGE_NODE-449",
"text": "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 the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1783_KNOWLEDGE_NODE-446",
"text": "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 the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "Locate — DevRev | Docs"
},
{
"id": "ART-1605_KNOWLEDGE_NODE-448",
"text": "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 the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1806_KNOWLEDGE_NODE-452",
"text": "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 the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "Self Post — DevRev | Docs"
},
{
"id": "ART-1785_KNOWLEDGE_NODE-446",
"text": "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 the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1832_KNOWLEDGE_NODE-455",
"text": "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 the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1779_KNOWLEDGE_NODE-448",
"text": "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 the provided severities.\\nAllowed values: blocker high low medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided",
"title": "Get — DevRev | Docs"
}
] |
4ba07998-0726-46bb-b167-95ca5fecdf72
|
unable to add recipients or CC in email over ticket
|
[
{
"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-2027_KNOWLEDGE_NODE-40",
"text": "Description |\\n| --- | --- | --- |\\n| To/CC Field Management | To / Cc fields | Automatically assigns visibility permissions to added recipients. Warns if invalid users exist. |\\n| Text Formatting & Styling | Toolbar (bold, italics, etc.) | Apply rich text formatting including color highlights and custom styles. |\\n| Change Sender Email | Email icon (top-right) | Select a different From email address from configured options in Email snap-in. |\\n| Enhance Message with AI | Purple wand icon | Use",
"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-1979_KNOWLEDGE_NODE-33",
"text": "members** does not remove them from the **Reported by** field.\\n\\nShadow users can also be subscribers and email members.\\n\\n* **CCed members in email**: The CCed members in emails will be added to reporters if they are contacts in the workspace to which the ticket belongs. They will be added to email members if they are part of the ongoing email thread, without any workspace restriction.\\n* **Shadow users**: Users created for tracking and record-keeping purposes that do not have access to the",
"title": "Tickets | Computer for Support Teams | 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-63",
"text": "support tickets on behalf of customers\\xe2\\x80\\x94without granting customers access to these tickets. This feature enables internal collaboration while keeping the ticket invisible to the customer until explicitly made external.\\n\\nEven if a ticket contains customer-related information (such as the customer workspace or the **Reported by** field), it remains inaccessible to the customer unless it is explicitly converted into an external ticket. The **Customer Messages** tab is unavailable for",
"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-16806_KNOWLEDGE_NODE-27",
"text": "Internal Ticket** from the **Ticket Creation** dropdown.\\n* **Focused UI:** The **Customer Messages** tab is disabled on internal tickets to prevent unintended communication.\\n\\nThis feature supports internal workflows while giving you control over when customer engagement begins.\\n\\n![]()\\xc2\\xa0For more information about *Conversation and Ticket Workflows*, refer to the following articles: \\xe2\\x80\\xa3 [Auto parts to conversation | Automate | Snap-ins](/docs/automations/auto-parts)",
"title": "July 2025 | Changelog | DevRev"
}
] |
19d771bc-215b-4d0a-9a72-2d3da44804b5
|
migration of Tickets Issues Incidents from acme to spd instance preserving original work ID numbers and timestamps
|
[
{
"id": "ART-997_KNOWLEDGE_NODE-26",
"text": "is built upon the core tenancy keys (e.g. dev_org), we have a ton of flexibility, clarity and overlap avoidance.\\n\\nFor example, look at the following 2 IDs from the above examples:\\n\\n\\n don:core:dvrv-us-1:**devo/55**:issues/789\\n don:core:dvrv-us-1:**devo/44**:issues/789\\n\\n\\nThese are issues from 2 different orgs, they have the same issue ID, but because of the devo in the DON they are both globally unique. This allows us to keep the type ids clean but still maintain a globally unique ID",
"title": "How to Write an Object Model That Doesn't Suck"
}
] |
8e4d51df-6adc-4047-9c0d-30ec56e13fc6
|
Knowledge article generation from single cases or case clusters
|
[
{
"id": "ART-1983_KNOWLEDGE_NODE-29",
"text": "on\\xe2\\x80\\x94it learns. It autonomously generates new Q&As based on the resolved conversation, marking them for review under the *Review Needed* status.\\n\\nA Q&A isn't created if it is similar to the existing Q&A to avoid duplication.\\n\\n```\\nSatisfactory answer\\n\\n\\n\\nSimilar Q&A found\\n\\n\\n\\nNo answer or \\ntalk to engineer\\n\\n\\n\\nImproves Turing\\n\\n\\n\\nCustomer query\\n\\n\\n\\nTuring\\n\\n\\n\\nConversation \\nresolved\\n\\n\\n\\nNo new Q&As \\ncreated\\n\\n\\n\\nQ&As created\\n```\\n\\nTo enable automatic",
"title": "Questions & answers | Computer for Support Teams | DevRev"
}
] |
db5bd216-2f02-42a4-a79a-371d88624178
|
parts when creating an issue
|
[
{
"id": "ART-1992_KNOWLEDGE_NODE-26",
"text": "importance of the issue. Priorities can be set to P0, P1, P2, and P3. P0 is the highest priority and P3 is the lowest.\\n* **Stage**: The current state of the issue. The stage attribute is used to track the progress of the issue through its lifecycle. For more information on stages, see [stages](#stages).\\n* **Part**: The part of the company or product that the issue is related to. For more information on parts, see [parts](./parts).\\n* **Created by**: The person who created the issue.\\n*",
"title": "Issues | Computer for Builders | 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"
},
{
"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-1950_KNOWLEDGE_NODE-46",
"text": "or bug fix to include it in the release notes.\\n* **Customer impact**: The impact of the part on the customer.\\n* **Target close date**: The date by which the part is expected to be resolved.\\n* **Target start date**: The date by which the part is expected to start.\\n\\nYou can add custom attributes to issues to track additional information. For more information on custom attributes, see [object customization](./object-customization).\\n\\nSubtypes\\n--------\\n\\nYou can create subtypes of issues to",
"title": "Parts & trails | Computer by DevRev | DevRev"
},
{
"id": "ART-1979_KNOWLEDGE_NODE-29",
"text": "**Severity**: The importance of the ticket. Severity can be set to low, medium, blocker, or high.\\n* **Stage**: The current state of the issue. The stage attribute is used to track the progress of the issue through its lifecycle. For more information on stages, see [stages](#stages).\\n* **Part**: The part of the company or product that the issue is related to. For more information on parts, see [parts](./parts).\\n* **Created by**: The user who created the ticket.\\n* **Created date**: The date",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"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-8441_KNOWLEDGE_NODE-36",
"text": "off if you choose to explicitly create issues and link your GitLab activity or you can enable it either for PR creation or branch creation event.\\n* Select the default part under **Default part for autonomous issues** as a default Part ID if you enable **Track autonomous work**. Autonomous issues originating from GitLab are attributed to a default part. You can configure the default part while setting up your snap-in. Every issue in DevRev must have a part attribution.\\n\\n### Autonomous work",
"title": "GitLab | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2030_KNOWLEDGE_NODE-37",
"text": "disabled if you choose to explicitly create issues and link your Bitbucket activity or you can enable it either for PR creation or branch creation event.\\n* Select the default part under **Default part for autonomous issues** as a default Part ID if you enable **Track autonomous work**. Autonomous issues originating from BitBucket will be attributed to a default part. You can configure the default part while setting up your snap-in. Every issue in DevRev must have a part attribution.\\n\\n###",
"title": "Bitbucket | Integrate | Snap-ins | 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-1992_KNOWLEDGE_NODE-28",
"text": "various vistas in DevRev to track specific work, capacity, and more.\\n\\nYou can add custom attributes to issues to track additional information. For more information on custom attributes, see [object customization](./object-customization).\\n\\nIssues are attached to parts in order to align efforts with product priorities.\\n\\nAs to the size of an issue and the flexibility it offers to manage changes in size, issues offer hierarchy in the form of parent-child relationships and granularity.\\n\\nFrom",
"title": "Issues | Computer for Builders | DevRev"
},
{
"id": "ART-1961_KNOWLEDGE_NODE-31",
"text": "needed. For example, if the ticket is found to be spam, you can automatically add a comment to the ticket.\\n\\n**Suggest part**\\n\\nOften, your integrations create tickets or issues associated with a default part. The suggest part takes the ID of a ticket or issue and suggests a relevant part. You can use this to route your tickets or issues to the most appropriate part of the product. For example, when a ticket is created, you can find a relevant part and update the ticket with the suggested",
"title": "Workflows | Computer by DevRev | DevRev"
},
{
"id": "ART-1651_KNOWLEDGE_NODE-439",
"text": "https://api.devrev.ai/works.create \\\\ > -H \" Authorization: Bearer <token> \" \\\\ > -H \" Content-Type: application/json \" \\\\ > -d \\' { > \"type\": \"issue\", > \"applies_to_part\": \"string\", > \"owned_by\": [ > \"string\" > ], > \"title\": \"string\" > } \\'\\n200 Successful 1 { 2 \" work \" : { 3 \" type \" : \" issue \" , 4 \" actual_start_date \" : \" 2023-01-01T00:00:00Z \" , 5 \" developed_with \" : [ 6 { 7 \" type \" : \" capability \" , 8 \" name \" : \" string \" , 9 \" owned_by \" : [ 10 { 11 \" type \" : \" dev_user \" , 12 \"",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1994_KNOWLEDGE_NODE-33",
"text": "sprint board and click **+Issue**.\\n Create a new issue, assign it to the part, sprint and add the owner.\\n\\n ![]()\\n\\n Sprints are not coordinated with stages.\\n3. Select issues that you would like to assign to **Sprint 1** or **Sprint 2** then click **Move** in the toolbar at the top of the screen and select the sprint.\\n\\n ![]()\\n4. Go to **Sprint 1** or **Sprint 2** to see that issues are displayed.\\n\\n ![]()\\n\\n The sprint is also displayed in (and can be changed from) the",
"title": "Sprint mode | Computer for Builders | DevRev"
},
{
"id": "ART-1957_KNOWLEDGE_NODE-31",
"text": "can select a date in this field. For example, \"Date of bug identified: 19/07/2024\".\\n + **Part**: Select the part to which this object belongs. It could be an enhancement, feature, capability, runnable, linkable, or product.\\n + **Dev user**: Select one or multiple users from the dropdown.\\n + **Customer**: Assign the object to an existing customer workspace.\\n + **Account**: Assign the object to a customer account.\\n + **Workspace**: Assign the object to a workspace.\\n\\n",
"title": "Object customization | Computer by DevRev | DevRev"
},
{
"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-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-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-15989_KNOWLEDGE_NODE-24",
"text": "[Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Automated part update](/docs/automations/automated-part-update)\\n\\nAutomated part update\\n=====================\\n\\nThe Automated part update snap-in streamlines the updating of issue or ticket parts based on the initial part and target field defined in its configuration. It monitors the creation events of issues and tickets, ensuring that new entries match the part specified in the **Initial Part of Issue/Ticket** input field. Upon",
"title": "Automated part update | Automate | Snap-ins | DevRev"
},
{
"id": "ART-1950_KNOWLEDGE_NODE-25",
"text": "be recursively made of smaller parts. Events and work items must be related to parts. In general, parts are the core objects that almost all other objects are linked to, which helps enforce the notion of tying everything back to the product or service.\\n\\n\\xf0\\x9f\\x8e\\xa5 Video: Trails\\n\\n*Trails* is an extensible interface that allows you to view and manage your part hierarchy and related items. Think of it like a graph canvas that\\'s rendering linkages among items\\xe2\\x80\\x94including",
"title": "Parts & trails | Computer by DevRev | DevRev"
},
{
"id": "ART-17231_KNOWLEDGE_NODE-102",
"text": "to which the issue belongs. |\\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| `target_start_date` | timestamp | | Target start date for the object |\\n| `title` | text | \\xe2\\x9c\\x94\\xef\\xb8\\x8e | Title of the work object |\\n\\n#### Enum values\\n\\n**priority**\\n\\n| Value | Name |",
"title": "Supported DevRev object types | DevRev | Docs"
},
{
"id": "ART-17231_KNOWLEDGE_NODE-99",
"text": "User ID of the user that created the object |\\n| `estimated_effort` | float | | Estimated effort to complete the issue |\\n| `fallback_parts` | reference\\xe2\\x86\\x92[#category:part] | | Other values that could serve as part if apples\\\\_to\\\\_part\\\\_id is found to be invalid. |\\n| `item_url_field` | text | | Link to the item in the origin system |\\n| `modified_by_id` | reference\\xe2\\x86\\x92[#category:user] | | User ID of the user that last modified the object |\\n| `owned_by_ids` | reference",
"title": "Supported DevRev object types | DevRev | Docs"
},
{
"id": "ART-1637_KNOWLEDGE_NODE-437",
"text": "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 https://api.devrev.ai/works.create \\\\ > -H \" Authorization: Bearer <token> \" \\\\ > -H \" Content-Type: application/json \" \\\\ > -d \\' { > \"type\": \"issue\", > \"applies_to_part\": \"string\", > \"owned_by\": [ > \"string\" > ], > \"title\": \"string\" > } \\'\\n200",
"title": "Delete — DevRev | Docs"
},
{
"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\",youremail@example.com,PROD-1,frontend,subtype1,Ticket\\n\\n\\n\\n3 APIs returning errors,\"The user.get API is returning 500\",youremail@example.com,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"
}
] |
74ba3430-6056-4c36-b1c2-45ccabb540fa
|
filtering by custom fields in conversation views
|
[
{
"id": "ART-1512_KNOWLEDGE_NODE-1",
"text": "then iteration starts from the beginning.\\n\\ncustom_fieldsmap from strings to anyOptional\\n\\nFilters for custom fields.\\n\\ngroupstringOptional\\n\\nFilters for conversation that belong to the given groups.\\n\\nis_creator_verifiedbooleanOptional\\n\\nFilters for conversations that are created by verified users.\\n\\nis_spambooleanOptional\\n\\nFilters for conversations that are spam.\\n\\nlimitintegerOptional\\n\\nThe maximum number of conversations to return. The default is",
"title": "List Conversations (Beta) — DevRev | Docs"
}
] |
fc419974-3881-40f8-a8ca-a899d411f735
|
Global CDN support for optimal performance worldwide
|
[
{
"id": "ART-992_KNOWLEDGE_NODE-10",
"text": "to k.sni.global.fastly.net instead of your web servers. This means when resolving foo.bar.com it would direct the traffic to hit Fastly\\xe2\\x80\\x99s servers.\\n\\nThis is important for a few key reasons, it enables them to hit a local Fastly point-of-presence (POP) and also allows them to be able to handle DDoS attacks before they hit your origin (if configured correctly, as I will cover).\\n\\nHere you can see an example CNAME resolving to Fastly:\\n\\n; <<>> DiG 9.16.1-Ubuntu <<>> foo.bar.com\\n;;",
"title": "Perimeter security with Fastly edge and AWS — Part I"
},
{
"id": "ART-992_KNOWLEDGE_NODE-13",
"text": "delivery model where we can offload the burden of requests from hitting origin and push more to the edge (more to come here!).\\n\\nIn our case we are using a mix of edge compute (C@E) which allows us to compile and execute RUST code on Fastly\\xe2\\x80\\x99s edge, which can also take advantage of their CDN which can cache content from origin.\\n\\nA quick note on WebAssembly (WASM)\\xe2\\x80\\xa6 this is one thing that is very interesting/exciting and will be one of the core enablers to making clients",
"title": "Perimeter security with Fastly edge and AWS — Part I"
},
{
"id": "ART-12476_KNOWLEDGE_NODE-2",
"text": "access control using DevRev\\xe2\\x80\\x99s Multi-factor Authorization (MFA) system.\\n\\nImproved reliability\\n\\nA platform powered by a team you can count on\\n\\nOmni-channel support: Access our new PLuG widget offering proactive HyperCare support with single-touch deflection across multiple capabilities\\n\\nReal-time updates: Receive live updates on your tickets and track development progress transparently\\n\\nReliable SDK Delivery with Fastly CDN: PLuG SDK is delivered via Fastly CDN which ensures",
"title": "The Future of Sessions - Powered By DevRev"
}
] |
567e8718-9e24-4916-a134-f4756b25a74f
|
ticket portal confirmation message sent to user immediately
|
[
{
"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-1953_KNOWLEDGE_NODE-33",
"text": "[no-reply@devrev.ai](mailto:no-reply@devrev.ai)\\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} [support@yourdomain.com](mailto:support@yourdomain.com)\\n* **Subject**: \"<customer email",
"title": "Customer email notifications | Computer by DevRev | DevRev"
},
{
"id": "ART-1961_KNOWLEDGE_NODE-36",
"text": "\\xe2\\x80\\x9cWe have received your request for help with the following: \\n{{Ask AI > Output > Output string}}. \\nA support agent will review the request and respond within your organization's SLA.\\xe2\\x80\\x9d\\n\\n\\n\\nAsk AI\\n\\n\\n\\nPrompt: \\xe2\\x80\\x9cSummarize the ticket based on \\n{{Ticket Created > Output > Description}}, \\n{{Ticket Created > Output > Title}}, \\n{{Ticket Created > Output > Applies to Part > Name}}, and",
"title": "Workflows | Computer by DevRev | DevRev"
}
] |
722fb588-1b64-4b74-95fd-3ce55ccf6d61
|
Data isolation ensuring customers only see their own data
|
[
{
"id": "ART-738_KNOWLEDGE_NODE-14",
"text": "Rather than physically segmenting tenant data, we built tenancy into the objects using specific attributes which act as partitions\\n This allows us to create macro partitions (e.g., customer) or extremely granular partitions (e.g., user level)\\n This gives us a ton of flexibility as all data is in one place and the granularity can range from macro to micro\\n \\n \\n We designed our services for the cloud\\n \\n Being built in the \\xe2\\x80\\x9cera of cloud\\xe2\\x80\\x9d we had a",
"title": "DevRev | Built for AI (not by AI... yet)"
},
{
"id": "ART-997_KNOWLEDGE_NODE-20",
"text": "tenancy key unique to each tenant (dev_org and rev_org). Using this, we have built-in safeguards to ensure only actors from a certain tenant can access objects of that tenant. Our authorization, mongo-client and other services all leverage this tenancy key and use this for validations.\\n\\nEven if there is a case for physical segmentation, it could still leverage this attribute to define which physical partition it goes to.\\n\\nRemember, you don\\xe2\\x80\\x99t know what you don\\xe2\\x80\\x99t know,",
"title": "How to Write an Object Model That Doesn't Suck"
},
{
"id": "ART-997_KNOWLEDGE_NODE-19",
"text": "There is a time and place for physical separation of data, however, this isn\\xe2\\x80\\x99t always required and logical tenancy will do in most cases. Even if you don\\xe2\\x80\\x99t initially plan for multi-tenancy or need it, it\\xe2\\x80\\x99s never a bad idea to plan ahead for this.\\n\\nRather than partitioning tenant data as the storage layer, which was very inefficient, we built multi-tenancy into every one of our objects. All objects inherit from the root base class (Atom), which includes a",
"title": "How to Write an Object Model That Doesn't Suck"
},
{
"id": "ART-12476_KNOWLEDGE_NODE-1",
"text": "designed to meet GDPR and SOC 2 compliance requirements, with controls in place to support your data privacy needs.\\n\\nAdvanced enterprise login: Seamless SAML compliance for all enterprise logins regardless of your SSO provider.\\n\\nRegional data residency options: We offer data residency options in Europe, Australia, US East (Virginia), and India, with logical data isolation and access control features.\\n\\nSelf-serve user management: Easily add or remove users from your workspace and manage",
"title": "The Future of Sessions - Powered By DevRev"
},
{
"id": "ART-970_KNOWLEDGE_NODE-92",
"text": "built multi-tenancy into the object\\n \\n Rather than physically segmenting tenant data, we built tenancy into the objects using specific attributes which act as partitions\\n This allows us to create macro partitions (e.g., customer) or extremely granular partitions (e.g., user level)\\n This gives us a ton of flexibility as all data is in one place and the granularity can range from macro to micro\\n \\n \\n We designed our services for the cloud\\n \\n Being built in",
"title": "The Story"
},
{
"id": "ART-970_KNOWLEDGE_NODE-102",
"text": "groundwork, ensuring we possessed the requisite keys to partition and segment data effectively. This profound understanding of the structure empowered us to fashion granular and precise authorization mechanisms. By dedicating upfront effort to this aspect, we\\xe2\\x80\\x99ve endowed our system with authorization capabilities that some mature companies can only envision, including support for role-based access control (RBAC), attribute-based access control (ABAC), policy-based access control",
"title": "The Story"
},
{
"id": "ART-16789_KNOWLEDGE_NODE-4",
"text": "insights across previously siloed information.Q: How does Computer handle data privacy and security?\\n\\nAlternative questions: \"Is my data safe?\" \"Data security with Computer\" \"Access controls in Computer\"\\n\\nAnswer: Computer preserves all your existing permissions and access controls. People only see information they\\'re supposed to have access to. We\\'re SOC 2 compliant, GDPR ready, and maintain individual-level access controls for personal data like calendars and emails.About ComputerQ: What",
"title": "Computer General FAQs"
},
{
"id": "ART-970_KNOWLEDGE_NODE-103",
"text": "(PBAC), field-level security, lease-based access, conditional policies, and more.\\n\\nFrom a compliance perspective, our rigorous efforts encompassed adherence to regulations such as SOC2 and ISO-27001. These considerations exerted influence over various facets of our architecture, notably shaping our approach to edge security through our web-application firewall (WAF) and our handling of configuration management.\\n\\nEven within our internal operations, we wholeheartedly embraced the zero-trust",
"title": "The Story"
},
{
"id": "ART-1958_KNOWLEDGE_NODE-30",
"text": "do not, by default, have permission to read any datasets besides their own. Admins are responsible for granting read permissions to all or a subset of datasets, which platform users can then utilize in building dashboards or reports.\\n\\n### Sharing\\n\\nThe share functionality allows dashboard or report editors to grant read or update permissions to other users.\\n\\n1. Select **Share** from the actions drop-down.\\n2. Search for the desired user, assign them a role (Editor or Viewer), then click",
"title": "Access control | Computer by DevRev | DevRev"
},
{
"id": "ART-738_KNOWLEDGE_NODE-13",
"text": "customization in from the start\\n \\n We knew extensibility would be key for any platform\\n Given the simplicity of customization, we can easily extend our object model with new annotations or context that can be used and fed into models\\n This means, that a customer or vendor, can easily extend our object model with new data on objects which can be used by models, new object types, or with the output of a model\\n \\n \\n We built multi-tenancy into the object\\n \\n",
"title": "DevRev | Built for AI (not by AI... yet)"
},
{
"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"
}
] |
e1a58e97-0e67-4f57-997d-3ef109d75a22
|
API to fetch or manage knowledge base content
|
[
{
"id": "ART-1507_KNOWLEDGE_NODE-5",
"text": "https://api.devrev.ai/articles.list \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer <token>\" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{}\\'\\n[/code] \\n \\nTry it\\n\\n200Successful\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"articles\": [ \\n 3| { \\n 4| \"applies_to_parts\": [ \\n 5| { \\n 6| \"type\": \"product\", \\n 7| \"id\": \"applies_to_parts\", \\n 8| \"name\": \"applies_to_parts\", \\n",
"title": "List Articles (POST) (Beta) — DevRev | Docs"
},
{
"id": "ART-15291_KNOWLEDGE_NODE-0",
"text": "b'Get Article (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)[articles](/api-reference/articles/create-article)\\n\\nGet Article (POST)\\n==================\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/articles.get\\n\\nPOST\\n\\n/articles.get\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/articles.get \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -H",
"title": "Get Article (POST) | DevRev | Docs"
},
{
"id": "ART-1307_KNOWLEDGE_NODE-36",
"text": "api.devrev.ai / articles.get\\nGets an article.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the required article.\\nResponse.\\n\\nThis endpoint returns an object.\\narticle object\\nShow 19 properties\\nAPI Reference articles List Articles.\\n\\nGET https:// api.devrev.ai / articles.list\\nLists a collection of articles.\\nQuery parameters.\\n\\napplies_to_parts string Optional\\nFilters for articles belonging to any of the provided parts.\\narticle_type \"article\" or",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-15294_KNOWLEDGE_NODE-0",
"text": "b'Get Article | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[articles](/api-reference/articles/create-article)\\n\\nGet Article\\n===========\\n\\nCopy page\\n\\nGET\\n\\nhttps://api.devrev.ai/articles.get\\n\\nGET\\n\\n/articles.get\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -G https://api.devrev.ai/articles.get \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -d id=ARTICLE-12345 |\\n```\\n\\n[Try",
"title": "Get Article | DevRev | Docs"
},
{
"id": "ART-1300_KNOWLEDGE_NODE-35",
"text": "Post.\\n\\nPOST https:// api.devrev.ai / articles.get\\nGets an article.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the required article.\\nResponse.\\n\\nThis endpoint returns an object.\\narticle object\\nShow 19 properties\\nAPI Reference articles List Articles.\\n\\nGET https:// api.devrev.ai / articles.list\\nLists a collection of articles.\\nQuery parameters.\\n\\napplies_to_parts string Optional\\nFilters for articles belonging to any of the provided",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1504_KNOWLEDGE_NODE-0",
"text": "b'[](/beta/api-reference/articles/get-article-post)\\n\\nBeta\\n\\n[API Reference](/beta/api-reference/accounts/create)[articles](/beta/api-reference/articles/count)\\n\\n# Get Article (POST)\\n\\nPOST\\n\\nhttps://api.devrev.ai/articles.get\\n\\nTry it\\n\\nGets an article.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\nidstringRequired\\n\\nThe ID of the required article.\\n\\n### Response\\n\\nGet article response.\\n\\narticleobject\\n\\nShow 20 properties\\n\\nPOST\\n\\n/articles.get\\n\\ncURL\\n\\n[code]\\n\\n $|",
"title": "Get Article (POST) (Beta) — DevRev | Docs"
},
{
"id": "ART-1316_KNOWLEDGE_NODE-0",
"text": "b'[](/beta/api-reference/articles/get-article)\\n\\nBeta\\n\\n[API Reference](/beta/api-reference/accounts/create)[articles](/beta/api-reference/articles/count)\\n\\n# Get Article\\n\\nGET\\n\\nhttps://api.devrev.ai/articles.get\\n\\nTry it\\n\\nGets an article.\\n\\n### Query parameters\\n\\nidstringRequired\\n\\nThe ID of the required article.\\n\\n### Response\\n\\nGet article response.\\n\\narticleobject\\n\\nShow 20 properties\\n\\nGET\\n\\n/articles.get\\n\\n[code]\\n\\n $| curl -G https://api.devrev.ai/articles.get \\\\",
"title": "Get Article (Beta) — DevRev | Docs"
},
{
"id": "ART-1504_KNOWLEDGE_NODE-1",
"text": "curl -X POST https://api.devrev.ai/articles.get \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer <token>\" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"id\": \"ARTICLE-12345\" \\n >| }\\'\\n[/code] \\n \\nTry it\\n\\n200Successful\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"article\": { \\n 3| \"applies_to_parts\": [ \\n 4| { \\n 5| \"type\": \"product\", \\n 6| \"id\": \"applies_to_parts\", \\n 7|",
"title": "Get Article (POST) (Beta) — DevRev | Docs"
},
{
"id": "ART-4069_KNOWLEDGE_NODE-0",
"text": "b'[](/public/api-reference/articles/list-articles-post)\\n\\nPublic\\n\\n[API Reference](/public/api-reference/getting-started)[Articles](/public/api-reference/articles/create-article)\\n\\n# List Articles (POST)\\n\\nPOST\\n\\nhttps://api.devrev.ai/articles.list\\n\\nTry it\\n\\nLists a collection of articles.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\napplies_to_partslist of stringsOptional\\n\\nFilters for articles belonging to any of the provided parts.\\n\\narticle_typelist of",
"title": "List Articles (POST) — DevRev | Docs"
},
{
"id": "ART-1545_KNOWLEDGE_NODE-378",
"text": "https://api.devrev.ai / question-answers.get\\n\\nGets a question-answer.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\n\\nThe ID of the required question-answer.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nquestion_answer object\\nShow 12 properties\\nAPI Reference question-answers List Question Answers.\\n\\nGET https://api.devrev.ai / question-answers.list\\n\\nLists a collection of question-answers.\\n\\nQuery parameters.\\n\\napplies_to_articles string Optional\\n\\nFilters",
"title": "Create (Beta) — DevRev | Docs"
},
{
"id": "ART-1566_KNOWLEDGE_NODE-380",
"text": "https://api.devrev.ai / question-answers.get\\n\\nGets a question-answer.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\n\\nThe ID of the required question-answer.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nquestion_answer object\\nShow 12 properties\\nAPI Reference question-answers List Question Answers.\\n\\nGET https://api.devrev.ai / question-answers.list\\n\\nLists a collection of question-answers.\\n\\nQuery parameters.\\n\\napplies_to_articles string Optional\\n\\nFilters",
"title": "Transition (Beta) — DevRev | Docs"
},
{
"id": "ART-15295_KNOWLEDGE_NODE-0",
"text": "b'List Articles | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[articles](/api-reference/articles/create-article)\\n\\nList Articles\\n=============\\n\\nCopy page\\n\\nGET\\n\\nhttps://api.devrev.ai/articles.list\\n\\nGET\\n\\n/articles.list\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl https://api.devrev.ai/articles.list \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" |\\n```\\n\\n[Try",
"title": "List Articles | DevRev | Docs"
},
{
"id": "ART-1582_KNOWLEDGE_NODE-1",
"text": "\\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -d id=id |\\n```\\n\\n[Try it](/beta/api-reference/question-answers/get-question-answer?explorer=true)\\n\\n200Retrieved\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"question_answer\": { |\\n| 3 | \"id\": \"string\", |\\n| 4 | \"answer\": \"string\", |\\n| 5 | \"applies_to_parts\": [ |\\n| 6 | { |\\n| 7 | \"display_id\": \"string\", |\\n| 8 | \"id\": \"string\", |\\n| 9 | \"name\": \"string\", |\\n| 10 | \"owned_by\": [ |\\n| 11 | { |\\n| 12 | \"display_id\": \"string\",",
"title": "Get Question Answer | DevRev | Docs"
},
{
"id": "ART-1308_KNOWLEDGE_NODE-34",
"text": "endpoint returns an object.\\narticle object\\nShow 19 properties\\nAPI Reference articles Delete Article.\\n\\nPOST https:// api.devrev.ai / articles.delete\\nDeletes an article.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the article to delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference articles Get Article.\\n\\nGET https:// api.devrev.ai / articles.get\\nGets an article.\\nQuery parameters.\\n\\nid string Required\\nThe ID of the",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-15293_KNOWLEDGE_NODE-0",
"text": "b'List Articles (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)[articles](/api-reference/articles/create-article)\\n\\nList Articles (POST)\\n====================\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/articles.list\\n\\nPOST\\n\\n/articles.list\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/articles.list \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > |",
"title": "List Articles (POST) | DevRev | Docs"
},
{
"id": "ART-4070_KNOWLEDGE_NODE-0",
"text": "b'[](/public/api-reference/articles/update-article)\\n\\nPublic\\n\\n[API Reference](/public/api-reference/getting-started)[Articles](/public/api-reference/articles/create-article)\\n\\n# Update Article\\n\\nPOST\\n\\nhttps://api.devrev.ai/articles.update\\n\\nTry it\\n\\nUpdates an article.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\nidstringRequired`format: \"id\"`\\n\\nThe article\\xe2\\x80\\x99s ID.\\n\\naccess_levelenumOptional\\n\\nAllowed values:",
"title": "Update Article — DevRev | Docs"
},
{
"id": "ART-1500_KNOWLEDGE_NODE-0",
"text": "b'[](/beta/api-reference/articles/update-article)\\n\\nBeta\\n\\n[API Reference](/beta/api-reference/accounts/create)[articles](/beta/api-reference/articles/count)\\n\\n# Update Article\\n\\nPOST\\n\\nhttps://api.devrev.ai/articles.update\\n\\nTry it\\n\\nUpdates an article.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\nidstringRequired\\n\\nThe article\\xe2\\x80\\x99s ID.\\n\\naccess_levelenumOptional\\n\\nAllowed values: externalinternalprivatepublicrestricted\\n\\naliasesobjectOptional\\n\\nShow",
"title": "Update Article (Beta) — DevRev | Docs"
},
{
"id": "ART-1588_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1315_KNOWLEDGE_NODE-1",
"text": "-X POST https://api.devrev.ai/articles.delete \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer <token>\" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"id\": \"ARTICLE-12345\" \\n >| }\\'\\n[/code] \\n \\nTry it\\n\\n200Successful\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"key\": \"value\" \\n 3| }\\n[/code] \\n \\n[Get ArticleUp Next](/beta/api-reference/articles/get-article)\\n\\n[Built",
"title": "Delete Article (Beta) — DevRev | Docs"
},
{
"id": "ART-1643_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1835_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "List — DevRev | Docs"
},
{
"id": "ART-15292_KNOWLEDGE_NODE-0",
"text": "b'Create Article | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[articles](/api-reference/articles/create-article)\\n\\nCreate Article\\n==============\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/articles.create\\n\\nPOST\\n\\n/articles.create\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/articles.create \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -H",
"title": "Create Article | DevRev | Docs"
},
{
"id": "ART-1826_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1308_KNOWLEDGE_NODE-35",
"text": "required article.\\nResponse.\\n\\nThis endpoint returns an object.\\narticle object\\nShow 19 properties\\nAPI Reference articles Get Article Post.\\n\\nPOST https:// api.devrev.ai / articles.get\\nGets an article.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the required article.\\nResponse.\\n\\nThis endpoint returns an object.\\narticle object\\nShow 19 properties\\nAPI Reference articles List Articles.\\n\\nGET https:// api.devrev.ai / articles.list\\nLists a collection of",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1639_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "Export Post — DevRev | Docs"
},
{
"id": "ART-15297_KNOWLEDGE_NODE-0",
"text": "b'Update Article | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[articles](/api-reference/articles/create-article)\\n\\nUpdate Article\\n==============\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/articles.update\\n\\nPOST\\n\\n/articles.update\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/articles.update \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -H",
"title": "Update Article | DevRev | Docs"
},
{
"id": "ART-1579_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1601_KNOWLEDGE_NODE-1",
"text": "https://api.devrev.ai/question-answers.get \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{ |\\n| > | \"id\": \"string\" |\\n| > | }\\' |\\n```\\n\\n[Try it](/beta/api-reference/question-answers/get-question-answer-post?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"question_answer\": { |\\n| 3 | \"id\": \"string\", |\\n| 4 | \"answer\": \"string\", |\\n| 5 | \"applies_to_parts\": [ |\\n| 6 | { |\\n| 7 | \"display_id\":",
"title": "Get Question Answer (POST) | DevRev | Docs"
},
{
"id": "ART-1609_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1782_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1824_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1836_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1507_KNOWLEDGE_NODE-0",
"text": "b'[](/beta/api-reference/articles/list-articles-post)\\n\\nBeta\\n\\n[API Reference](/beta/api-reference/accounts/create)[articles](/beta/api-reference/articles/count)\\n\\n# List Articles (POST)\\n\\nPOST\\n\\nhttps://api.devrev.ai/articles.list\\n\\nTry it\\n\\nLists a collection of articles.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\napplies_to_partslist of stringsOptional\\n\\nFilters for articles belonging to any of the provided parts.\\n\\narticle_typelist of enumsOptional\\n\\nAllowed values:",
"title": "List Articles (POST) (Beta) — DevRev | Docs"
},
{
"id": "ART-1833_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1789_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1837_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1654_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1822_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1787_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1650_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1821_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1314_KNOWLEDGE_NODE-0",
"text": "b'[](/beta/api-reference/articles/create-article)\\n\\nBeta\\n\\n[API Reference](/beta/api-reference/accounts/create)[articles](/beta/api-reference/articles/count)\\n\\n# Create Article\\n\\nPOST\\n\\nhttps://api.devrev.ai/articles.create\\n\\nTry it\\n\\nArticle is an object which can contain a URL or artifacts in the resource. It also contains the data regarding the owner, author, status and published date of the object. This call creates an article.\\n\\n### Request\\n\\nThis endpoint expects an",
"title": "Create Article (Beta) — DevRev | Docs"
},
{
"id": "ART-1781_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1584_KNOWLEDGE_NODE-1",
"text": "https://api.devrev.ai/question-answers.list \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" |\\n```\\n\\n[Try it](/beta/api-reference/question-answers/list-question-answers?explorer=true)\\n\\n200Retrieved\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"question_answers\": [ |\\n| 3 | { |\\n| 4 | \"id\": \"string\", |\\n| 5 | \"answer\": \"string\", |\\n| 6 | \"applies_to_parts\": [ |\\n| 7 | { |\\n| 8 | \"display_id\": \"string\", |\\n| 9 | \"id\": \"string\", |\\n| 10 | \"name\": \"string\", |\\n| 11 | \"owned_by\": [ |\\n| 12 | {",
"title": "List Question Answers | DevRev | Docs"
},
{
"id": "ART-1302_KNOWLEDGE_NODE-37",
"text": "object.\\narticle object\\nShow 19 properties\\nAPI Reference articles Delete Article.\\n\\nPOST https:// api.devrev.ai / articles.delete\\nDeletes an article.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the article to delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference articles Get Article.\\n\\nGET https:// api.devrev.ai / articles.get\\nGets an article.\\nQuery parameters.\\n\\nid string Required\\nThe ID of the required",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1783_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "Locate — DevRev | Docs"
},
{
"id": "ART-15293_KNOWLEDGE_NODE-1",
"text": "-H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{}\\' |\\n```\\n\\n[Try it](/api-reference/articles/list-articles-post?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"articles\": [ |\\n| 3 | { |\\n| 4 | \"id\": \"string\", |\\n| 5 | \"owned_by\": [ |\\n| 6 | { |\\n| 7 | \"display_id\": \"string\", |\\n| 8 | \"id\": \"string\", |\\n| 9 | \"display_name\": \"string\", |\\n| 10 | \"display_picture\": { |\\n| 11 | \"display_id\": \"string\", |\\n| 12 | \"id\": \"string\", |\\n| 13 | \"file\": { |\\n| 14 |",
"title": "List Articles (POST) | DevRev | Docs"
},
{
"id": "ART-1301_KNOWLEDGE_NODE-37",
"text": "object.\\narticle object\\nShow 19 properties\\nAPI Reference articles Delete Article.\\n\\nPOST https:// api.devrev.ai / articles.delete\\nDeletes an article.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the article to delete.\\nResponse.\\n\\nThis endpoint returns a map from strings to any.\\nAPI Reference articles Get Article.\\n\\nGET https:// api.devrev.ai / articles.get\\nGets an article.\\nQuery parameters.\\n\\nid string Required\\nThe ID of the required",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1832_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1830_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1801_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1582_KNOWLEDGE_NODE-0",
"text": "b'Get Question Answer | 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)[question-answers](/beta/api-reference/question-answers/create-question-answer)\\n\\nGet Question Answer\\n===================\\n\\nBeta\\n\\nCopy page\\n\\nGET\\n\\nhttps://api.devrev.ai/question-answers.get\\n\\nGET\\n\\n/question-answers.get\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -G https://api.devrev.ai/question-answers.get",
"title": "Get Question Answer | DevRev | Docs"
},
{
"id": "ART-1802_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1302_KNOWLEDGE_NODE-38",
"text": "article.\\nResponse.\\n\\nThis endpoint returns an object.\\narticle object\\nShow 19 properties\\nAPI Reference articles Get Article Post.\\n\\nPOST https:// api.devrev.ai / articles.get\\nGets an article.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the required article.\\nResponse.\\n\\nThis endpoint returns an object.\\narticle object\\nShow 19 properties\\nAPI Reference articles List Articles.\\n\\nGET https:// api.devrev.ai / articles.list\\nLists a collection of",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1595_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1301_KNOWLEDGE_NODE-38",
"text": "article.\\nResponse.\\n\\nThis endpoint returns an object.\\narticle object\\nShow 19 properties\\nAPI Reference articles Get Article Post.\\n\\nPOST https:// api.devrev.ai / articles.get\\nGets an article.\\nRequest.\\n\\nThis endpoint expects an object.\\nid string Required\\nThe ID of the required article.\\nResponse.\\n\\nThis endpoint returns an object.\\narticle object\\nShow 19 properties\\nAPI Reference articles List Articles.\\n\\nGET https:// api.devrev.ai / articles.list\\nLists a collection of",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1641_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1780_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1597_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-15291_KNOWLEDGE_NODE-1",
"text": "\"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{ |\\n| > | \"id\": \"ARTICLE-12345\" |\\n| > | }\\' |\\n```\\n\\n[Try it](/api-reference/articles/get-article-post?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"article\": { |\\n| 3 | \"id\": \"string\", |\\n| 4 | \"owned_by\": [ |\\n| 5 | { |\\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",
"title": "Get Article (POST) | DevRev | Docs"
},
{
"id": "ART-1831_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1655_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-4070_KNOWLEDGE_NODE-6",
"text": "https://api.devrev.ai/articles.update \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer <token>\" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"id\": \"ARTICLE-12345\" \\n >| }\\'\\n[/code] \\n \\nTry it\\n\\n200articlesUpdateArticleExample\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"article\": { \\n 3| \"id\": \"foo\", \\n 4| \"owned_by\": [ \\n 5| { \\n 6| \"display_id\": \"foo\", \\n 7| \"id\": \"foo\", \\n",
"title": "Update Article — DevRev | Docs"
},
{
"id": "ART-1784_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "Locate Post — DevRev | Docs"
},
{
"id": "ART-1633_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1603_KNOWLEDGE_NODE-1",
"text": "https://api.devrev.ai/question-answers.list \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{}\\' |\\n```\\n\\n[Try it](/beta/api-reference/question-answers/list-question-answers-post?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"question_answers\": [ |\\n| 3 | { |\\n| 4 | \"id\": \"string\", |\\n| 5 | \"answer\": \"string\", |\\n| 6 | \"applies_to_parts\": [ |\\n| 7 | { |\\n| 8 | \"display_id\": \"string\", |\\n| 9 |",
"title": "List Question Answers (POST) | DevRev | Docs"
},
{
"id": "ART-1652_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1637_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1509_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "Prepare — DevRev | Docs"
},
{
"id": "ART-1304_KNOWLEDGE_NODE-42",
"text": "elements exist.\\nAPI Reference articles List Articles Post.\\n\\nPOST https:// api.devrev.ai / articles.list\\nLists a collection of articles.\\nRequest.\\n\\nThis endpoint expects an object.\\napplies_to_parts list of strings Optional\\nFilters for articles belonging to any of the provided parts.\\narticle_type list of \"article\" or \"content_block\" Optional\\nAllowed values: article content_block\\nFilter for the type of articles. If this is not provided, then articles that are not content blocks are",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1590_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1818_KNOWLEDGE_NODE-25",
"text": "intended audience.\\nShow 2 properties\\nResponse.\\n\\nThis endpoint returns an object.\\ncount integer\\nThe total number of articles matching the filter.\\nAPI Reference articles Create Article.\\n\\nPOST https:// api.devrev.ai / articles.create\\nArticle is an object which can contain a URL or artifacts in the 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",
"title": "Sla Trackers Get Post — DevRev | Docs"
}
] |
e119826a-ea9c-4a47-89f7-689de2601f3d
|
operator to check for null value in custom ticket fields in workflow
|
[
{
"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"
}
] |
5ad07830-4b93-44ab-8f7e-3e9a4d92d601
|
Vendor availability impact on day-to-day operations
|
[
{
"id": "ART-738_KNOWLEDGE_NODE-17",
"text": "level\\n Also, some vendors who didn\\xe2\\x80\\x99t grow up in the \\xe2\\x80\\x9cas a service\\xe2\\x80\\x9d era will need to change processes to embrace CI/CD (some may have)\\n A good ask here is how frequently changes are deployed\\n When something new comes out, we can react and enable rapidly; others may be slower to enable, leading to a gap between when something is \\xe2\\x80\\x9cavailable\\xe2\\x80\\x9d and \\xe2\\x80\\x9creally available\\xe2\\x80\\x9d\\n \\n \\n\\n\\nMost of the available",
"title": "DevRev | Built for AI (not by AI... yet)"
},
{
"id": "ART-4172_KNOWLEDGE_NODE-11",
"text": "available. Moderate decline in performance since workaround is available but hampers day-to-day operations.\\n\\n***Medium*** - An inconvenient problem exists, however a workaround is readily available and can be applied. This type of issue may cause inconvenience or delays in certain tasks or processes, but it does not prevent the business from functioning altogether. There is no financial loss and no impact on day to day operations.\\n\\n***Low*** - There is a misleading or unsatisfactory",
"title": "DevRev Service Level Agreement"
},
{
"id": "ART-970_KNOWLEDGE_NODE-95",
"text": "as you need to build things at a much more macro level\\n Also, some vendors who didn\\xe2\\x80\\x99t grow up in the \\xe2\\x80\\x9cas a service\\xe2\\x80\\x9d era will need to change processes to embrace CI/CD (some may have)\\n A good ask here is how frequently changes are deployed\\n When something new comes out, we can react and enable rapidly; others may be slower to enable, leading to a gap between when something is \\xe2\\x80\\x9cavailable\\xe2\\x80\\x9d and \\xe2\\x80\\x9creally",
"title": "The Story"
},
{
"id": "ART-991_KNOWLEDGE_NODE-2",
"text": "different outcomes, some positive and the poor experiences leading to me churning off a vendor.\\n\\nExample 1: Bad\\n\\nIn my role, I produce many videos for external enablement, and we leverage a mix of YouTube and another vendor, which I will refer to as \\xe2\\x80\\x9cFoo.\\xe2\\x80\\x9d\\n\\nOne evening, I had trouble uploading videos I worked late to produce, so I contacted their support to see what was happening. I heard back the next day, and this was the response:\\n\\n\\xe2\\x80\\x9cHi there,\\n\\nThank",
"title": "Why Poor Support May Be Costing You More Than You Think"
},
{
"id": "ART-2133_KNOWLEDGE_NODE-46",
"text": "people (engineers, designers, and developers). For example, a meaningful awareness of an external service provider\\xe2\\x80\\x99s (a) noti\\xef\\xac\\x81cations and outages, (b) advisories and vulnerabilities, (c) new capabilities, and (d) economics of usage, all via automations, is crucial for reducing security risks and \\xef\\xac\\x81nancial surprises down the line. Similarly, a continuous understanding of an engineer\\xe2\\x80\\x99s (a) skills and contributions, (b) deep work metrics, and (c)",
"title": "The Essential Methodology: Less but Better"
},
{
"id": "ART-991_KNOWLEDGE_NODE-11",
"text": "ready, they proactively contacted us to get us on the program and worked with us to ensure everything was operating as expected. During the cutover, they were on a call live with us to ensure everything worked as expected. We ran into a few hiccups, but they helped troubleshoot and solve with us live.\\n\\nThis is an excellent example of a partnership, not a traditional vendor/client relationship. They were honest about the lack of a feature (this builds credibility), but they were also proactive",
"title": "Why Poor Support May Be Costing You More Than You Think"
},
{
"id": "ART-16189_KNOWLEDGE_NODE-9",
"text": "Increased collaboration between support, engineering, and customer success\\n* Proactive engagement through real-time issue visibility and alerts\\n* Centralized communication and streamlined workflows\\n* Scalable operations without requiring a dedicated people manager\\n\\nWith DevRev, FOSSA shifted from reactive support to a connected, efficient, and proactive experience.\\n\\nWe evaluated our legacy vendor\\xe2\\x80\\x99s AI capabilities, and it was difficult to even get them to come to the table. In",
"title": "FOSSA’s Unified Support Strategy for Elevated Customer Experience"
},
{
"id": "ART-2957_KNOWLEDGE_NODE-0",
"text": "b'Summary\\n\\nDescription: On November 7, 2024, we identified significant latency issues affecting our Web Monitoring API and other domains routed through Fastly. The issue was resolved later the same day by rerouting traffic for the impacted service.\\n\\nSeverity: High\\n\\nImpact: The latency affected the performance of the Web Monitoring API and other DevRev services, potentially causing delays in customer workflows and impacting user experience. Root Cause Analysis\\n\\nThe latency was traced",
"title": "Increased Latency on Web Monitoring API - November 7, 2024"
},
{
"id": "ART-4172_KNOWLEDGE_NODE-15",
"text": "(<https://support.devrev.ai/>).\\n\\n### 6.The following services shall be out of scope\\n\\n* Services related to Third-Party Products\\n* Errors in any end-user data or other information supplied by the Customer\\n* Errors not attributable to the DevRev service\\n\\n### 7. Holiday schedule\\n\\n**INDIA(APAC) Holiday Schedule**\\n\\n| Dates | Dates cont. |\\n| --- | --- |\\n| January 1 | May 1 |\\n| January 14 | August 15 |\\n| January 26 | August 27 |\\n| March 14 | October 1 |\\n| March 30 | October 20 |\\n|",
"title": "DevRev Service Level Agreement"
},
{
"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 ([support@DevRev.ai](mailto:support@DevRev.ai))\\n* Support Portal",
"title": "DevRev Service Level Agreement"
}
] |
3c39d4b7-5a9b-470e-aa49-a3c138e97349
|
workflow filter based on customer account variable
|
[
{
"id": "ART-12392_KNOWLEDGE_NODE-25",
"text": "| --- | --- |\\n| Account created | Filter conditions | Account object |\\n| Account updated | Filter conditions | Account object |\\n| Contact created | Filter conditions | Customer User object |\\n| Contact updated | Filter conditions | User object |\\n| Enhancement updated | Filter conditions | Enhancement object |\\n| Incident updated | Filter conditions | Incident object |\\n| Issue created | Filter conditions | Issue object |\\n| Issue linked With object | Filter conditions | Issue and linked",
"title": "Triggers | Workflows | Computer by DevRev | 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-1649_KNOWLEDGE_NODE-464",
"text": "set, then \"after\" is used.\\nAllowed values: after before\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string Optional\\nFilters for work reported by any of",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1649_KNOWLEDGE_NODE-451",
"text": "provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string Optional\\nFilters for work reported by any of these users.\\nsort_by string",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1961_KNOWLEDGE_NODE-37",
"text": "\\n{{Ticket\\xc2\\xa0Created\\xc2\\xa0>\\xc2\\xa0Output\\xc2\\xa0>\\xc2\\xa0Reported\\xc2\\xa0By\\xc2\\xa0>\\xc2\\xa0Rev\\xc2\\xa0Org\\xc2\\xa0>\\xc2\\xa0Display\\xc2\\xa0Name}}.\\xe2\\x80\\x9d\\n\\n\\n\\nDelay\\n\\n\\n\\nDuration: 2 minutes\\n\\n\\n\\nIf-else\\n\\n\\n\\nAttribute:\\xc2\\xa0Ticket\\xc2\\xa0Created/Output\\xc2\\xa0>\\xc2\\xa0Applies\\xc2\\xa0to\\xc2\\xa0part\\xc2\\xa0>\\xc2\\xa0Display\\xc2\\xa0ID \\nOperator: Equals \\nOperand: CAPL-18\\n\\n\\n\\nTicket \\ncreated\\n\\n\\n\\nEnd\\n```\\n\\n[### Workflow action",
"title": "Workflows | Computer by DevRev | DevRev"
},
{
"id": "ART-1961_KNOWLEDGE_NODE-34",
"text": "button toolbar.\\n4. Set your triggers. You can have multiple triggers within a single workflow.\\n5. To configure your workflow, utilize the data reference pane to select values from previous nodes.\\n6. Connect steps with multiple paths as needed, allowing for the management of complex workflows on one canvas.\\n7. To add conditional logic, use a control step.\\n\\n Select a value for the LHS; select the appropriate operator; and enter or select a value for the RHS, which can be a literal value",
"title": "Workflows | Computer by DevRev | DevRev"
},
{
"id": "ART-1566_KNOWLEDGE_NODE-7",
"text": "specified user(s).\\n\\ncreated_date object Optional\\nShow 2 properties\\ncustom_fields map from strings to any Optional\\n\\nFilters for custom fields.\\n\\ndisplay_name list of strings Optional\\n\\nArray of display names of accounts to be filtered.\\n\\ndomains list of strings Optional\\n\\nDomains for accounts to be filtered.\\n\\nexternal_refs list of strings Optional\\n\\nArray of references of accounts to be filtered.\\n\\nfirst integer Optional\\n\\nThe number of accounts to return. The default is",
"title": "Transition (Beta) — DevRev | Docs"
},
{
"id": "ART-1560_KNOWLEDGE_NODE-517",
"text": "used.\\n\\nAllowed values: after before\\nopportunity.account string Optional\\n\\nFilters for opportunities belonging to any of the provided accounts.\\n\\nopportunity.contacts string Optional\\n\\nFilters for opportunities with any of the provided contacts.\\n\\nopportunity.subtype string Optional\\n\\nFilters for opportunity with any of the provided subtypes.\\n\\nowned_by string Optional\\n\\nFilters for work owned by any of these users.\\n\\nreported_by string Optional\\n\\nFilters for work reported by any of",
"title": "Assign (Beta) — DevRev | Docs"
},
{
"id": "ART-1785_KNOWLEDGE_NODE-440",
"text": "parameters.\\n\\napplies_to_part string Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by string Optional\\nFilters for work created by any of these users.\\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.accounts string Optional\\nFilters for issues with any of the provided Accounts.\\nissue.priority enum Optional\\nFilters for",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1790_KNOWLEDGE_NODE-441",
"text": "parameters.\\n\\napplies_to_part string Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by string Optional\\nFilters for work created by any of these users.\\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.accounts string Optional\\nFilters for issues with any of the provided Accounts.\\nissue.priority enum Optional\\nFilters for",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1566_KNOWLEDGE_NODE-517",
"text": "used.\\n\\nAllowed values: after before\\nopportunity.account string Optional\\n\\nFilters for opportunities belonging to any of the provided accounts.\\n\\nopportunity.contacts string Optional\\n\\nFilters for opportunities with any of the provided contacts.\\n\\nopportunity.subtype string Optional\\n\\nFilters for opportunity with any of the provided subtypes.\\n\\nowned_by string Optional\\n\\nFilters for work owned by any of these users.\\n\\nreported_by string Optional\\n\\nFilters for work reported by any of",
"title": "Transition (Beta) — DevRev | Docs"
},
{
"id": "ART-1802_KNOWLEDGE_NODE-446",
"text": "parameters.\\n\\napplies_to_part string Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by string Optional\\nFilters for work created by any of these users.\\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.accounts string Optional\\nFilters for issues with any of the provided Accounts.\\nissue.priority enum Optional\\nFilters for",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1784_KNOWLEDGE_NODE-440",
"text": "parameters.\\n\\napplies_to_part string Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by string Optional\\nFilters for work created by any of these users.\\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.accounts string Optional\\nFilters for issues with any of the provided Accounts.\\nissue.priority enum Optional\\nFilters for",
"title": "Locate Post — DevRev | Docs"
},
{
"id": "ART-1779_KNOWLEDGE_NODE-442",
"text": "parameters.\\n\\napplies_to_part string Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by string Optional\\nFilters for work created by any of these users.\\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.accounts string Optional\\nFilters for issues with any of the provided Accounts.\\nissue.priority enum Optional\\nFilters for",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1792_KNOWLEDGE_NODE-444",
"text": "parameters.\\n\\napplies_to_part string Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by string Optional\\nFilters for work created by any of these users.\\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.accounts string Optional\\nFilters for issues with any of the provided Accounts.\\nissue.priority enum Optional\\nFilters for",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1783_KNOWLEDGE_NODE-440",
"text": "parameters.\\n\\napplies_to_part string Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by string Optional\\nFilters for work created by any of these users.\\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.accounts string Optional\\nFilters for issues with any of the provided Accounts.\\nissue.priority enum Optional\\nFilters for",
"title": "Locate — DevRev | Docs"
},
{
"id": "ART-1308_KNOWLEDGE_NODE-443",
"text": "parameters.\\n\\napplies_to_part string Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by string Optional\\nFilters for work created by any of these users.\\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.accounts string Optional\\nFilters for issues with any of the provided Accounts.\\nissue.priority enum Optional\\nFilters for",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1592_KNOWLEDGE_NODE-443",
"text": "parameters.\\n\\napplies_to_part string Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by string Optional\\nFilters for work created by any of these users.\\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.accounts string Optional\\nFilters for issues with any of the provided Accounts.\\nissue.priority enum Optional\\nFilters for",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1806_KNOWLEDGE_NODE-446",
"text": "parameters.\\n\\napplies_to_part string Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by string Optional\\nFilters for work created by any of these users.\\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.accounts string Optional\\nFilters for issues with any of the provided Accounts.\\nissue.priority enum Optional\\nFilters for",
"title": "Self Post — DevRev | Docs"
},
{
"id": "ART-1786_KNOWLEDGE_NODE-443",
"text": "sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1301_KNOWLEDGE_NODE-446",
"text": "parameters.\\n\\napplies_to_part string Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by string Optional\\nFilters for work created by any of these users.\\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.accounts string Optional\\nFilters for issues with any of the provided Accounts.\\nissue.priority enum Optional\\nFilters for",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1792_KNOWLEDGE_NODE-446",
"text": "sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1804_KNOWLEDGE_NODE-446",
"text": "parameters.\\n\\napplies_to_part string Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by string Optional\\nFilters for work created by any of these users.\\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.accounts string Optional\\nFilters for issues with any of the provided Accounts.\\nissue.priority enum Optional\\nFilters for",
"title": "Self — DevRev | Docs"
},
{
"id": "ART-1785_KNOWLEDGE_NODE-442",
"text": "sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1804_KNOWLEDGE_NODE-448",
"text": "sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string",
"title": "Self — DevRev | Docs"
},
{
"id": "ART-1806_KNOWLEDGE_NODE-448",
"text": "sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string",
"title": "Self Post — DevRev | Docs"
}
] |
324e4314-929d-4d55-829b-00d2b0cfb363
|
create CRM to track leads and potential clients
|
[
{
"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-6175_KNOWLEDGE_NODE-24",
"text": "[Snap-ins](/docs/snapins)\\n[Automate](/docs/automate)\\n[Airtable](/docs/automations/airtable)\\n\\nAirtable\\n========\\n\\nThe **Airtable** snap-in automates lead intake from Airtable form submissions by mapping responses to DevRev contacts, accounts, and custom objects. It supports field mapping, duplicate detection, tagging, and ownership assignment using custom configurations. Submissions are processed in real time, enabling seamless CRM integration and streamlined data",
"title": "Airtable | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2002_KNOWLEDGE_NODE-31",
"text": "**Group** conditions across various vistas in DevRev to track specific work, capacity, and more.\\n\\nYou can add custom attributes to opportunities to track additional information. For more information on custom attributes, see [object customization](./object-customization).\\n\\n### External reference\\n\\nWhile ingesting customer identity into DevRev, customer information coming across channels must be matched to the same record. \\nFor example, a customer record created by you using APIs should",
"title": "Contacts | Computer for Growth Teams | DevRev"
},
{
"id": "ART-15502_KNOWLEDGE_NODE-5",
"text": "marketing campaigns on DevRev. This guide goes through the process of creating a \\xe2\\x80\\x9cCampaign\\xe2\\x80\\x9d custom object with relevant fields.\\n\\nAll DevRev objects require a schema. First, create a schema for the \\xe2\\x80\\x9cCampaign\\xe2\\x80\\x9d custom object. Make sure to replace the `<TOKEN>` with your API token.\\n\\n### Create custom objects\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl --location \\'https://api.devrev.ai/schemas.custom.set\\' \\\\ |\\n| > | --header \\'Content-Type:",
"title": "Custom objects | DevRev | Docs"
},
{
"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-1592_KNOWLEDGE_NODE-356",
"text": "Create.\\n\\nPOST https:// api.devrev.ai / rev-users.create\\nCreates a Rev user for a Rev organization. Rev user can be a customer or a lead of an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of the account to which the created Rev user is associated.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev user.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1783_KNOWLEDGE_NODE-353",
"text": "rev-users.create\\nCreates a Rev user for a Rev organization. Rev user can be a customer or a lead of an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of the account to which the created Rev user is associated.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev user.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ncustom_schema_fragments list of strings Optional\\nThe schema",
"title": "Locate — DevRev | Docs"
},
{
"id": "ART-4096_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 Users](/public/api-reference/rev-users/create)\\n\\n# Create Rev User\\n\\nPOST\\n\\nhttps://api.devrev.ai/rev-users.create\\n\\nTry it\\n\\nCreates a Rev user for a Rev organization. Rev user can be a customer or a lead of an organization.\\n\\n### Request\\n\\nThis endpoint expects an",
"title": "Create Rev User — DevRev | Docs"
},
{
"id": "ART-1804_KNOWLEDGE_NODE-359",
"text": "rev-users.create\\nCreates a Rev user for a Rev organization. Rev user can be a customer or a lead of an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of the account to which the created Rev user is associated.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev user.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ncustom_schema_fragments list of strings Optional\\nThe schema",
"title": "Self — DevRev | Docs"
},
{
"id": "ART-1301_KNOWLEDGE_NODE-359",
"text": "rev-users.create\\nCreates a Rev user for a Rev organization. Rev user can be a customer or a lead of an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of the account to which the created Rev user is associated.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev user.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ncustom_schema_fragments list of strings Optional\\nThe schema",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1792_KNOWLEDGE_NODE-357",
"text": "rev-users.create\\nCreates a Rev user for a Rev organization. Rev user can be a customer or a lead of an organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Optional\\nThe ID of the account to which the created Rev user is associated.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev user.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ncustom_schema_fragments list of strings Optional\\nThe schema",
"title": "Update — DevRev | Docs"
}
] |
f95a98db-4fc1-46d8-8128-65213477b402
|
Next SLA Target field logic
|
[
{
"id": "ART-1986_KNOWLEDGE_NODE-42",
"text": "Target\\n------------------------------------\\n\\nIn order to filter tickets based on SLA, you can use the **Next SLA Target** filter.\\nHere\\xe2\\x80\\x99s how the filter works:\\n\\n* **All**: Filters all tickets that currently have an SLA applied to them. It will not filter tickets that had an SLA applied in the past and have been completed.\\n* **Breached since**:\\n\\n + **Any**: Filters all tickets that breached SLA, irrespective of when they were breached.\\n + **Over an hour**: Filters all",
"title": "Service-level agreement | Computer for Support Teams | DevRev"
},
{
"id": "ART-1986_KNOWLEDGE_NODE-40",
"text": "conversation moves to any stage except Waiting on User |\\n\\nViewing SLAs\\n------------\\n\\nThe SLA targets applied to a particular conversation can be viewed in the **Inbox** and the **Conversation Detailed** view. For a ticket in any of the ticket vistas.\\n\\nWhen there are two active metrics, vista displays the one closest to the breach. In the case of a conversation where both the first response and full resolution metrics are active, and the first response is due in five minutes but the full",
"title": "Service-level agreement | Computer for Support Teams | DevRev"
}
] |
97f3f9bb-c129-4fae-aca6-2e6a8ca6c64f
|
SLAs and OLAs in DevRev
|
[
{
"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-2695_KNOWLEDGE_NODE-25",
"text": "Teams](/docs/product/support)\\n[Operational-level agreement](/docs/product/ola)\\n\\nOperational-level agreement\\n===========================\\n\\nAn operational-level agreement (OLA) is an internal contract that defines the service level targets expected from different teams within your organization. OLAs are customer account agnostic, and they are usually created to ensure that internal stakeholders have their own targets, which in turn helps meet the customer SLAs.\\n\\nCreate an",
"title": "Operational-level agreement | Computer for Support Teams | DevRev"
},
{
"id": "ART-2695_KNOWLEDGE_NODE-26",
"text": "OLA\\n-------------\\n\\nYou can create OLAs for issues.\\n\\n1. Go to **Settings** > **Service Level Agreements** > **OLAs** > **+ Create**.\\n2. In the **Create OLA** window, enter a name and description for the OLA.\\n\\nBy default, the OLA is created in the *Draft* state. You can assign policies to the OLA as needed.\\n\\nCreate policies within an OLA\\n-----------------------------\\n\\n1. Click **+ Issue Policy**.\\n2. In the **New Issue Policy** pane, select the appropriate **Conditions** and",
"title": "Operational-level agreement | Computer for Support Teams | DevRev"
},
{
"id": "ART-1986_KNOWLEDGE_NODE-40",
"text": "conversation moves to any stage except Waiting on User |\\n\\nViewing SLAs\\n------------\\n\\nThe SLA targets applied to a particular conversation can be viewed in the **Inbox** and the **Conversation Detailed** view. For a ticket in any of the ticket vistas.\\n\\nWhen there are two active metrics, vista displays the one closest to the breach. In the case of a conversation where both the first response and full resolution metrics are active, and the first response is due in five minutes but the full",
"title": "Service-level agreement | Computer for Support Teams | DevRev"
},
{
"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-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-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 ([support@DevRev.ai](mailto:support@DevRev.ai))\\n* Support Portal",
"title": "DevRev Service Level Agreement"
},
{
"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-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-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"
}
] |
a07f4968-aeef-4e58-8660-c4c54decf3f5
|
ticket and conversation syncing with same slack thread
|
[
{
"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-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-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-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-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-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-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-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-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"
}
] |
ad7b1fb3-4bfc-4005-8d05-bdcf696b5062
|
SLA Status column missing in export
|
[
{
"id": "ART-1508_KNOWLEDGE_NODE-20",
"text": "\"removed_by\": { |\\n| 338 | \"display_id\": \"string\", |\\n| 339 | \"id\": \"string\", |\\n| 340 | \"display_name\": \"string\", |\\n| 341 | \"display_picture\": { |\\n| 342 | \"display_id\": {}, |\\n| 343 | \"id\": {}, |\\n| 344 | \"file\": {} |\\n| 345 | }, |\\n| 346 | \"email\": \"string\", |\\n| 347 | \"full_name\": \"string\", |\\n| 348 | \"state\": \"active\" |\\n| 349 | } |\\n| 350 | } |\\n| 351 | ], |\\n| 352 | \"sla\": { |\\n| 353 | \"id\": \"string\", |\\n| 354 | \"name\": \"string\", |\\n| 355 | \"status\": \"archived\", |\\n| 356 | \"display_id\":",
"title": "Export Conversations | DevRev | Docs"
},
{
"id": "ART-15484_KNOWLEDGE_NODE-3",
"text": "survey responses, and tickets\\n\\n### Works\\n\\nModified endpoints that handle work objects ([works API reference](/public/api-reference/works)):\\n\\n* Added `sla_summary` property to issues and tickets\\n* Added `value` property to ticket sentiment field\\n\\nThese changes affect the following endpoints:\\n\\n* [`/works.create`](/public/api-reference/works/create)\\n* [`/works.export`](/public/api-reference/works/export-post)\\n* [`/works.get`](/public/api-reference/works/get-post)\\n*",
"title": "January 8, 2025 | DevRev | Docs"
},
{
"id": "ART-1521_KNOWLEDGE_NODE-21",
"text": "\"string\", |\\n| 354 | \"name\": \"string\", |\\n| 355 | \"status\": \"archived\", |\\n| 356 | \"display_id\": \"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\":",
"title": "Export Conversations (POST) | DevRev | Docs"
}
] |
5a0884da-7299-4cab-862e-664a112a0fc9
|
reason agent did not follow conversation after plug and email response
|
[
{
"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-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-1954_KNOWLEDGE_NODE-36",
"text": "bot mentions will still appear in the **Others** tab.\\n\\nFollow conversations\\n--------------------\\n\\nTo receive updates about conversations in the Plug inbox, you must be a member of the support group. To manage membership of the support group go to [**Settings** > **Groups**](https://app.devrev.ai/devrev/settings/groups).\\n\\nFor more information about groups, refer to [Groups](/docs/product/groups).\\n\\nDaily email digest\\n------------------\\n\\nDevRev sends a daily email digest with a summary",
"title": "Updates | Computer by DevRev | DevRev"
},
{
"id": "ART-4206_KNOWLEDGE_NODE-22",
"text": "webhook events?**\\n\\n* Verify your webhook URL is publicly accessible\\n* Check that you\\xe2\\x80\\x99ve registered for the \\xe2\\x80\\x9cai\\\\_agent\\\\_response\\xe2\\x80\\x9d event type\\n* Ensure your server responds with a 2xx status code quickly\\n\\n**Execution errors?**\\n\\n* Check the error message in the error event\\n* Verify your agent ID is correct\\n* Ensure your session\\\\_object is a valid string\\n\\n**Agent not responding as expected?**\\n\\n* Review the skill\\\\_triggered and skill\\\\_executed",
"title": "Agents async API | DevRev | Docs"
},
{
"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-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-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-12391_KNOWLEDGE_NODE-28",
"text": "visibility | Dropdown | Visibility of agent comments: internal or external. For customer-facing use cases it is external. |\\n| panel | Dropdown | Panel for agent responses: CustomerChat. |\\n| quick\\\\_replies (optional) | Array[String] | Preset reply options that display to users. |\\n| respond\\\\_to\\\\_user\\\\_types | Array[String] | User types the agent engages with (for example, customer). For customer facing use cases it is customer. |\\n| suspend\\\\_on\\\\_message\\\\_from (optional) | String | User",
"title": "Conversational workflows | Workflows | Computer by DevRev | DevRev"
},
{
"id": "ART-4206_KNOWLEDGE_NODE-8",
"text": "\"event\": { |\\n| > | \"input_message\": { |\\n| > | \"message\": \"Your query to the agent\" |\\n| > | } |\\n| > | }, |\\n| > | \"session_object\": \"unique_conversation_identifier\", |\\n| > | \"webhook_target\": { |\\n| > | \"webhook\": \"don:integration:dvrv-us-1:devo/0:webhook/auCJ7By8\" |\\n| > | }, |\\n| > | \"client_metadata\": { |\\n| > | \"user_id\": \"12345\", |\\n| > | \"conversation_id\": \"conv-789\" |\\n| > | } |\\n| > | }\\' |\\n```\\n\\n##### \\n\\nThe session\\\\_object parameter is critical for maintaining conversation",
"title": "Agents async API | DevRev | Docs"
},
{
"id": "ART-2040_KNOWLEDGE_NODE-46",
"text": "also some generic [AirSync scopes and limitations](/docs/import).\\n\\n### Comments\\n\\nInline email replies may be omitted when importing Zendesk ticket responses into DevRev. These replies include and update the contents of previous emails within the same message. This omission occurs due to limitations in the Zendesk API.\\n\\n### Updates\\n\\n* Changes to the description field in DevRev are not properly transferred since the description isn\\xe2\\x80\\x99t a first-class field in Zendesk.\\n* If a",
"title": "Zendesk AirSync | AirSync | Snap-ins | DevRev"
}
] |
9bc112b6-efe6-4ae5-a637-2b0282a1d1d0
|
upgrade role of existing user to admin
|
[
{
"id": "ART-1948_KNOWLEDGE_NODE-27",
"text": "default.\\n\\nAdmins have the authority to configure access for different user groups by assigning or revoking roles. These roles determine the level of permissions and privileges granted to a group, allowing them to perform particular tasks or access specific features.\\n\\nOnly an admin can grant admin privileges to another user.\\n\\nCreating a new group\\n--------------------\\n\\nYou need to be an admin to create a group.\\n\\n1. Go to [**Settings > User Management >",
"title": "Groups | Computer by DevRev | DevRev"
},
{
"id": "ART-1956_KNOWLEDGE_NODE-27",
"text": "Roles**](https://app.devrev.ai/devrev/settings/user-roles), select the role to assign.\\n2. Select **Assign role**.\\n3. To assign the role to a group:\\n 1. Select **+ Group**.\\n 2. Search for and select the groups.\\n 3. Select **Assign role**.\\n4. To assign the role to a user:\\n 1. Select **+ User**.\\n 2. Search for and select the users.\\n 3. Select **Assign role**.\\n\\n![]()\\n\\nYou cannot assign a role to the **All users** group.\\n\\nManage customer roles\\n---------------------\\n\\n###",
"title": "Roles | Computer by DevRev | 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-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-16790_KNOWLEDGE_NODE-7",
"text": "users?\\n\\nClick on the three-dot menu (\\xe2\\x8b\\xaf) next to any user to access management options. This typically includes options to change roles, deactivate users, or modify their access privileges.\\n\\nWhat does \"Deactivate user\" do?\\n\\nDeactivating a user removes their access to the organization while preserving their account information.\\n\\nHow do I invite new users?\\n\\nWhile not shown in these specific screenshots, there should be an \"Invite\" or \"Add user\" button that allows you to send",
"title": "Computer Settings and Preferences FAQs"
},
{
"id": "ART-1955_KNOWLEDGE_NODE-39",
"text": "Privileges: dataset object ['CREATE']\\n* *Dataset Owner:* A role that allows the creator to view, edit and delete a dataset\\n\\n Privileges: dataset object ['READ', 'UPDATE', 'DELETE']\\n\\n\\xe2\\x80\\x9cAdmins\\xe2\\x80\\x9d group\\n--------------\\n\\nGroup for all organization admins, includes the necessary privileges to manage the platform configuration, integrations, and other administrative items. Only an admin can promote another user to admin.\\n\\n**Privileges:**\\n\\n* *Issue Interactor:* Contains",
"title": "Default privileges by group | Roles | Computer by DevRev | DevRev"
},
{
"id": "ART-4148_KNOWLEDGE_NODE-2",
"text": "Rev users\\n\\n* Added [`POST /rev-users.associations.add`](/beta/api-reference/rev-users/associations-add) to add new associations (workspaces/Rev organizations and accounts) to Rev users\\n* Added [`POST /rev-users.associations.remove`](/beta/api-reference/rev-users/associations-remove) to remove associations from Rev users\\n\\n### Roles\\n\\n* Added [`POST /roles.apply`](/beta/api-reference/roles/apply) to add/remove roles of a principal\\n\\n### Webhooks\\n\\n* Added [`POST",
"title": "March 3, 2025 | DevRev | Docs"
}
] |
e849f701-0592-4bad-837c-0faed999b9a2
|
created by and reported by different accounts in DevRev ticket
|
[
{
"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-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-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"
},
{
"id": "ART-3235_KNOWLEDGE_NODE-26",
"text": "system.\\n\\nAfter configuring these settings, the snap-in automatically processes new tickets and enriches their **Reported By** fields based on the provided email addresses.\\n\\n[PreviousSlack Broadcaster](/docs/automations/slack-broadcaster)[NextTicket approval workflow](/docs/automations/ticket-approval-workflow)\\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": "Reported by enricher | Automate | Snap-ins | DevRev"
},
{
"id": "ART-1986_KNOWLEDGE_NODE-37",
"text": "a customer * The ticket was created by a customer experience engineer but reported by a customer | A new comment on the ticket by the customer after the customer experience engineer replied | * The agent added a comment to the customer chat * The ticket is moved to Awaiting Customer Response, or the ticket is closed | | |\\n| Full resolution time | * Ticket created by a customer * The ticket was created by a customer experience engineer but reported by a customer | Ticket created | The",
"title": "Service-level agreement | Computer for Support Teams | DevRev"
},
{
"id": "ART-6174_KNOWLEDGE_NODE-27",
"text": "happens automatically:\\n\\n* The original conversation moves 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 + Equivalent metadata as the conversation, including source channel, customer account information, and external members added as **reported by** on the ticket\\n + An AI-generated ticket title and description based on customer messages\\n\\nConvert conversations to",
"title": "Conversation to ticket conversion | Conversations | Computer for Support Teams | DevRev"
},
{
"id": "ART-1986_KNOWLEDGE_NODE-36",
"text": "conversations:\\n\\n**Tickets**\\n\\n| Metric | Default conditions | Start event | End event | Pause event | Resume event |\\n| --- | --- | --- | --- | --- | --- |\\n| First response time | * Ticket created by a customer * The ticket was created by a customer experience engineer but reported by a customer | Ticket created | * The agent added a comment to the customer chat * The ticket is moved to Awaiting Customer Response, or the ticket is closed | | |\\n| Next response time | * Ticket created by",
"title": "Service-level agreement | Computer for Support Teams | DevRev"
}
] |
37715b44-4073-436d-99de-a2a1c6f3c784
|
create report with ticket tags and type
|
[
{
"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-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"
},
{
"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"
}
] |
ec00ce52-4b55-4121-8c4d-eb3d8d87fc69
|
set up workflow or skills for AI agent to connect to external website and conduct actions
|
[
{
"id": "ART-15617_KNOWLEDGE_NODE-10",
"text": "Context : Agents lack unified view of customer, product, engineering, and incident data\\n\\nAI Constraints : AI add-on costs $50 per user monthly for entire organization with limited external data access\\n\\nTraining Dependencies : AI agent requires training and cannot retrieve data from external systems or make API calls\\n\\nWorkflow Limitations : Rule-based workflows lack AI decision points and intelligent routing capabilities\\n\\nIntegration Complexity : External app automations require complex,",
"title": "Pylon - Competitive - for the PLuG on website"
},
{
"id": "ART-15617_KNOWLEDGE_NODE-2",
"text": "add-on\\n\\nLimitation : AI agents operate with significant constraints\\n\\nCost : $50 per user monthly, requires purchasing for entire organization\\n\\nTraining Requirements : AI agent trained only on data within Pylon, specific web URLs, and uploaded files\\n\\nFunctionality Gap : Cannot retrieve data from external systems, make API calls, or access broader organizational context Custom Workflows\\n\\nPosition : Limited capabilities\\n\\nWeakness : Lacks AI decision points for intelligent workflow",
"title": "Pylon - Competitive - for the PLuG on website"
},
{
"id": "ART-16803_KNOWLEDGE_NODE-28",
"text": "step\\n---------\\n\\nThe **HTTP step** allows your workflow to send or receive data from any service with a REST API. This step supports all common HTTP methods and provides flexibility for authentication, headers, and request/response handling.\\n\\nTo configure an HTTP step:\\n\\n1. On the **workflow canvas**, add an action step named **HTTP**.\\n2. Select the **Auth Token connection** you want to use.\\n\\n If no connection exists, go to [**Settings** >",
"title": "Workflow nodes | Workflows | Computer by DevRev | DevRev"
},
{
"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-1472_KNOWLEDGE_NODE-30",
"text": "authenticate and connect with GitHub. This ensures that the snap-in has the necessary permissions to interact with GitHub APIs.\\n\\n## Resources\\n\\nThe final snap-in code and manifest can be found [here](https://github.com/devrev/snap-in-examples/tree/main/9-external-action).\\n\\nWas this page helpful?YesNo\\n\\n[Snap-in triggered by a DevRev eventUp Next](/public/snapin-development/tutorials/triggered-event)\\n\\n[Built",
"title": "Using a snap-in to perform an external action — DevRev | Docs"
}
] |
f2185be2-5b89-43d0-b8f4-06b365819103
|
disable search for help site pages that resolve to 404 error
|
[
{
"id": "ART-15509_KNOWLEDGE_NODE-18",
"text": "window.plugSDK.initSearchAgent(); |\\n| 10 | } |\\n| 11 | }); |\\n| 12 | }, []); |\\n```\\n\\nToggle search agent\\n-------------------\\n\\nThe `toggleSearchAgent` method allows you to control the visibility of the search agent.\\n\\nIf no input is provided, the method toggles the search bar: opening it if it\\xe2\\x80\\x99s closed, and closing it if it\\xe2\\x80\\x99s open.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | window.plugSDK.toggleSearchAgent(true); |\\n```\\n\\nCheck Search Agent",
"title": "Methods | DevRev | Docs"
}
] |
b8819088-9d5b-4220-bcbc-9d479cb81c3e
|
change behavior of Needs response attribute
|
[
{
"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"
}
] |
be6805a0-b34e-42bd-93e2-e8c819b43baf
|
hybrid search action output variable usage in workflow
|
[
{
"id": "ART-1961_KNOWLEDGE_NODE-37",
"text": "\\n{{Ticket\\xc2\\xa0Created\\xc2\\xa0>\\xc2\\xa0Output\\xc2\\xa0>\\xc2\\xa0Reported\\xc2\\xa0By\\xc2\\xa0>\\xc2\\xa0Rev\\xc2\\xa0Org\\xc2\\xa0>\\xc2\\xa0Display\\xc2\\xa0Name}}.\\xe2\\x80\\x9d\\n\\n\\n\\nDelay\\n\\n\\n\\nDuration: 2 minutes\\n\\n\\n\\nIf-else\\n\\n\\n\\nAttribute:\\xc2\\xa0Ticket\\xc2\\xa0Created/Output\\xc2\\xa0>\\xc2\\xa0Applies\\xc2\\xa0to\\xc2\\xa0part\\xc2\\xa0>\\xc2\\xa0Display\\xc2\\xa0ID \\nOperator: Equals \\nOperand: CAPL-18\\n\\n\\n\\nTicket \\ncreated\\n\\n\\n\\nEnd\\n```\\n\\n[### Workflow action",
"title": "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"
}
] |
1ed4c3f7-556a-4bb1-a164-0e75ded3c0c5
|
difference between issue, ticket, and part
|
[
{
"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-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-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-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-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-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-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-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"
},
{
"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"
}
] |
6ccf1ad9-d4b0-4bc9-a7c9-406724e9a7f3
|
Salesforce airdropped accounts error No tickets found for this account
|
[
{
"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"
}
] |
c5db3b79-e110-4da2-9e15-00c3329229fe
|
custom widget for conversation analytics
|
[
{
"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"
},
{
"id": "ART-1952_KNOWLEDGE_NODE-28",
"text": "adjustments before finalizing it.\\n\\nWidget builder\\n--------------\\n\\nWith the widget builder, you can create custom widgets for your vista reports. You can define the widget's data source, construct measures, dimensions, and pick a suitable visualization. The widget builder offers a range of tools and options to help you create the ideal widget for your report.\\n\\nWidgets represent the building blocks of DevRev Dashboards. They are the leaf-level data visualizations which are composed",
"title": "Vista Reports | Vistas | Computer by DevRev | DevRev"
},
{
"id": "ART-1952_KNOWLEDGE_NODE-35",
"text": "well.\\n\\n### Save\\n\\nAdd measures, dimensions, and filters. Experiment with arranging them, preview your changes, and remember to **Save** your widget. This ensures the widget appears on the dashboard.\\n\\n### Custom fields\\n\\nYou can also create reports based on custom fields by creating them via Object Customization. You\\xe2\\x80\\x99ll be able to utilize these custom fields in report generation, as they can be used in measures, dimensions, and filters.\\n\\n### Cross-entity",
"title": "Vista Reports | Vistas | Computer by DevRev | DevRev"
}
] |
68534721-0afa-459c-8761-4171f9e3a860
|
unwanted encrypted details in Title field
|
[
{
"id": "ART-12453_KNOWLEDGE_NODE-23",
"text": "provides an auto-masking feature that masks data before sending to the server. Input views such as text fields, text views, and web views are automatically masked.\\n\\nWhile the auto-masking feature may be sufficient for most situations, you can manually mark additional views as sensitive using the following method:\\n\\n[code]\\n\\n 1| DevRev.markSensitiveViews(_:) \\n ---|---\\n[/code] \\n \\nIf any previously masked views need to be unmasked, you can use the following method:\\n\\n[code]\\n\\n",
"title": "Features — DevRev | Docs"
},
{
"id": "ART-12449_KNOWLEDGE_NODE-28",
"text": "findViewById(R.id.view1) \\n ---|--- \\n 2| val view2 = findViewById(R.id.view2) \\n 3| \\n 4| DevRev.markSensitiveViews(listOf(view1, view2))\\n[/code] \\n \\n#### Unmask\\n\\n##### Using tag\\n\\n#####\\n\\nUse Tag method only when you don\\xe2\\x80\\x99t have any other tag already applied to your UI element.\\n\\n[code]\\n\\n 1| android:tag=\"devrev-unmask\" \\n ---|---\\n[/code] \\n \\nFor example:\\n\\n[code]\\n\\n 1| <WebView \\n ---|--- \\n 2| android:id=\"@+id/webview2\" \\n",
"title": "Features — DevRev | Docs"
}
] |
d48a5d80-6a76-4e20-90d7-cccb9535520d
|
relationship between workspaces and accounts in DevRev
|
[
{
"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-1414_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/workspaces)\\n\\n#\\n\\nWorkspaces\\n\\n`rev-orgs` endpoint\\n\\n\\xe2\\x84\\xb9\\xef\\xb8\\x8f Workspaces (or rev orgs) are the organizations that your customers belong to. A workspace offers more granularity than accounts to define the instances of your product. Users can be mapped",
"title": "Workspaces — DevRev | Docs"
},
{
"id": "ART-1210_KNOWLEDGE_NODE-0",
"text": "b'Workspaces | 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\\nWorkspaces\\n==========\\n\\nCopy page\\n\\n`rev-orgs` endpoint\\n\\n\\xe2\\x84\\xb9\\xef\\xb8\\x8f Workspaces (or rev orgs) are the organizations that your customers belong to. A workspace offers more granularity than accounts to define the instances of your product. Users can be mapped to track",
"title": "Workspaces | DevRev | Docs"
},
{
"id": "ART-1997_KNOWLEDGE_NODE-28",
"text": "single account. This allows us to consolidate various workspaces under one account.\\n\\nTo create a new organization in DevRev:\\n\\n1. Click on your profile picture in the top left corner.\\n2. Go to the **Orgs** section and click on **+**.\\n3. Fill in the details and click **Create**.\\n4. Now you can find your newly created org in **Orgs**.\\n\\nIn modern SaaS applications, customers often create multiple workspaces for testing, production, and staging. All entities that drive support",
"title": "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-1997_KNOWLEDGE_NODE-26",
"text": "it holds information about the company, including its name, address, industry, domain, and website address.\\n\\nDevRev leverages convergence to link DevRev accounts with other DevRev entities, including tickets, conversations, opportunities, workspaces, and engagements. This linking offers a 360-degree view of an account across sales, customer success, and support. To enable real-time collaboration among employees from different departments on an account, it provides a discussion",
"title": "Computer for Growth Teams | DevRev"
},
{
"id": "ART-2933_KNOWLEDGE_NODE-2",
"text": "[contacts](https://docs.devrev.ai/product/grow#-contact) which represents an individual user associated with the account of the organization. To create a contact, we also need to use the `rev-orgs.list` API with the `accounts` filter to get the default [workspace](https://docs.devrev.ai/product/grow#-workspace)(rev org) created with the account. We will be creating a contact under the workspace (`rev_org`) of the account as contacts (`rev_user`) cannot exist individually without being",
"title": "Account creation | DevRev | Docs"
},
{
"id": "ART-2002_KNOWLEDGE_NODE-25",
"text": "about the customer initiating the conversation. Similarly, tickets on DevRev can capture who the ticket was reported by (or reported for).\\n\\nConcepts\\n--------\\n\\nCustomer identity in DevRev includes the following important constructs:\\n\\n* **External User/contact**: Your end user or customer or users associated with organization Accounts or Workspaces.\\n* **Account/workspace**: Any logical grouping that an external user is part of. It could represent a customer account for your B2B product",
"title": "Contacts | 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-15506_KNOWLEDGE_NODE-10",
"text": "preferences, it is not recommended to mark emails as non-unique.\\n\\n**Attributes for [workspaces](https://developer.devrev.ai/public/api-reference/rev-orgs/workspaces)**\\n\\n| Attributes | Description | Type | Required | Unique |\\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 | \\xe2\\x9d\\x8c | \\xe2\\x9c\\x85 |\\n| `display_name` |",
"title": "Identify your users with Plug | DevRev | Docs"
},
{
"id": "ART-16264_KNOWLEDGE_NODE-28",
"text": "**Account** and **Reported By**. This provides a more streamlined approach to managing customer data.\\n* **Automatic workspace display:** When a ticket reporter is associated with a specific workspace within an account, adding that user to the **Reported By** field will automatically reveal three fields: **Account**, **Workspace**, and **Reported By**.\\n* **Dynamic user listing:**\\n\\n + Upon selection of an account, the **Reported By** list is filtered to show only users associated with that",
"title": "June 2025 | Changelog | DevRev"
}
] |
e7c9ba8e-08f1-43e1-a7de-a29adb4dcec3
|
unable to see updated views of recently added attributes
|
[
{
"id": "ART-15716_KNOWLEDGE_NODE-29",
"text": "objects and their instances.\\n\\nSometimes, new custom object types or instances may not appear immediately in the UI\\xe2\\x80\\x94try refreshing or logging out and back in.\\n\\nIf you still can\\xe2\\x80\\x99t find it, check if the custom object is filtered out by any active UI filters or if it\\xe2\\x80\\x99s in a different workspace.\\n\\nIf the issue persists, it could be a UI sync or indexing delay. Escalate to engineering with the custom object\\xe2\\x80\\x99s name, schema, and instance details for",
"title": "Support queries related playbook"
},
{
"id": "ART-1604_KNOWLEDGE_NODE-9",
"text": "\"create_view\": { \\n 89| \"is_hidden\": true \\n 90| }, \\n 91| \"detail_view\": { \\n 92| \"is_hidden\": true \\n 93| }, \\n 94| \"display_name\": \"foo\", \\n 95| \"filter_view\": { \\n 96| \"is_hidden\": true \\n 97| }, \\n 98| \"group_name\": \"foo\", \\n 99| \"is_active_in_detail_view\": true, \\n 100| \"is_bulk_action_enabled\": true, \\n 101|",
"title": "Get Schemas Custom (Beta) — DevRev | Docs"
},
{
"id": "ART-1285_KNOWLEDGE_NODE-2",
"text": "10 | \"create_view\": { |\\n| 11 | \"is_hidden\": true |\\n| 12 | }, |\\n| 13 | \"detail_view\": { |\\n| 14 | \"is_hidden\": true |\\n| 15 | }, |\\n| 16 | \"display_name\": \"string\", |\\n| 17 | \"filter_view\": { |\\n| 18 | \"is_hidden\": true |\\n| 19 | }, |\\n| 20 | \"group_name\": \"string\", |\\n| 21 | \"is_active_in_detail_view\": true, |\\n| 22 | \"is_bulk_action_enabled\": true, |\\n| 23 | \"is_groupable\": true, |\\n| 24 | \"is_hidden\": true, |\\n| 25 | \"is_hidden_during_create\": true, |\\n| 26 | \"is_read_only\": true, |\\n| 27",
"title": "Inputs | DevRev | Docs"
},
{
"id": "ART-1957_KNOWLEDGE_NODE-34",
"text": "on the field.\\n * **Description**: Add some information about why you added this field. This is only visible to you.\\n3. Click **Save to draft**. These fields can be reviewed and then published by clicking **Publish changes**.\\n4. Review the changes and click **Publish changes** once you are ready.\\n5. Refresh the page to see the changes in published mode. You can\\'t make changes in this mode.\\n\\nTo edit or delete a custom field, click the **\\xe2\\x8b\\xae** icon next to the field. You\\'ll see",
"title": "Object customization | Computer by DevRev | DevRev"
},
{
"id": "ART-5153_KNOWLEDGE_NODE-30",
"text": "|\\n| 619 | \"view_name\": \"string\" |\\n| 620 | } |\\n| 621 | ] |\\n| 622 | } |\\n| 623 | ], |\\n| 624 | \"create_view\": { |\\n| 625 | \"is_hidden\": true |\\n| 626 | }, |\\n| 627 | \"decimal_places\": 1, |\\n| 628 | \"detail_view\": { |\\n| 629 | \"is_hidden\": true |\\n| 630 | }, |\\n| 631 | \"display_name\": \"string\", |\\n| 632 | \"filter_view\": { |\\n| 633 | \"is_hidden\": true |\\n| 634 | }, |\\n| 635 | \"group_name\": \"string\", |\\n| 636 | \"is_active_in_detail_view\": true, |\\n| 637 | \"is_bulk_action_enabled\": true, |\\n| 638",
"title": "Get Widget (POST) | DevRev | Docs"
},
{
"id": "ART-1633_KNOWLEDGE_NODE-427",
"text": "is_read_only \" : true , 110 \" is_required \" : true , 111 \" is_shown_in_summary \" : true , 112 \" is_sortable \" : true , 113 \" list_view \" : { 114 \" is_hidden \" : true 115 } , 116 \" placeholder \" : \" string \" , 117 \" summary_view \" : { 118 \" is_hidden \" : true 119 } , 120 \" tooltip \" : \" string \" 121 } 122 } 123 } , 124 \" name \" : \" string \" , 125 \" new_value \" : { 126 \" type \" : \" bool \" , 127 \" value \" : true 128 } , 129 \" old_value \" : { 130 \" type \" : \" bool \" , 131 \" value \" : true 132 } 133",
"title": "List — DevRev | Docs"
},
{
"id": "ART-5155_KNOWLEDGE_NODE-30",
"text": "|\\n| 624 | \"create_view\": { |\\n| 625 | \"is_hidden\": true |\\n| 626 | }, |\\n| 627 | \"decimal_places\": 1, |\\n| 628 | \"detail_view\": { |\\n| 629 | \"is_hidden\": true |\\n| 630 | }, |\\n| 631 | \"display_name\": \"string\", |\\n| 632 | \"filter_view\": { |\\n| 633 | \"is_hidden\": true |\\n| 634 | }, |\\n| 635 | \"group_name\": \"string\", |\\n| 636 | \"is_active_in_detail_view\": true, |\\n| 637 | \"is_bulk_action_enabled\": true, |\\n| 638 | \"is_currency_field\": true, |\\n| 639 | \"is_groupable\": true, |\\n| 640 | \"is_hidden\":",
"title": "Get Widget | DevRev | Docs"
},
{
"id": "ART-1830_KNOWLEDGE_NODE-425",
"text": "\" : {} 90 } , 91 \" origin \" : \" string \" , 92 \" ui \" : { 93 \" create_view \" : { 94 \" is_hidden \" : true 95 } , 96 \" detail_view \" : { 97 \" is_hidden \" : true 98 } , 99 \" display_name \" : \" string \" , 100 \" filter_view \" : { 101 \" is_hidden \" : true 102 } , 103 \" group_name \" : \" string \" , 104 \" is_active_in_detail_view \" : true , 105 \" is_bulk_action_enabled \" : true , 106 \" is_groupable \" : true , 107 \" is_hidden \" : true , 108 \" is_hidden_during_create \" : true , 109 \" is_read_only \" : true",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1832_KNOWLEDGE_NODE-434",
"text": "string \" , 92 \" ui \" : { 93 \" create_view \" : { 94 \" is_hidden \" : true 95 } , 96 \" detail_view \" : { 97 \" is_hidden \" : true 98 } , 99 \" display_name \" : \" string \" , 100 \" filter_view \" : { 101 \" is_hidden \" : true 102 } , 103 \" group_name \" : \" string \" , 104 \" is_active_in_detail_view \" : true , 105 \" is_bulk_action_enabled \" : true , 106 \" is_groupable \" : true , 107 \" is_hidden \" : true , 108 \" is_hidden_during_create \" : true , 109 \" is_read_only \" : true , 110 \" is_required \" : true ,",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1606_KNOWLEDGE_NODE-10",
"text": "\"is_hidden\": true \\n 75| }, \\n 76| \"display_name\": \"foo\", \\n 77| \"filter_view\": { \\n 78| \"is_hidden\": true \\n 79| }, \\n 80| \"group_name\": \"foo\", \\n 81| \"is_active_in_detail_view\": true, \\n 82| \"is_bulk_action_enabled\": true, \\n 83| \"is_currency_field\": true, \\n 84| \"is_groupable\": true, \\n 85| \"is_hidden\": true,",
"title": "List Schemas Custom (Beta) — DevRev | Docs"
},
{
"id": "ART-1830_KNOWLEDGE_NODE-435",
"text": "93 \" create_view \" : { 94 \" is_hidden \" : true 95 } , 96 \" detail_view \" : { 97 \" is_hidden \" : true 98 } , 99 \" display_name \" : \" string \" , 100 \" filter_view \" : { 101 \" is_hidden \" : true 102 } , 103 \" group_name \" : \" string \" , 104 \" is_active_in_detail_view \" : true , 105 \" is_bulk_action_enabled \" : true , 106 \" is_groupable \" : true , 107 \" is_hidden \" : true , 108 \" is_hidden_during_create \" : true , 109 \" is_read_only \" : true , 110 \" is_required \" : true , 111 \" is_shown_in_summary",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1492_KNOWLEDGE_NODE-3",
"text": "\"origin\": \"string\", \\n 9| \"ui\": { \\n 10| \"create_view\": { \\n 11| \"is_hidden\": true \\n 12| }, \\n 13| \"detail_view\": { \\n 14| \"is_hidden\": true \\n 15| }, \\n 16| \"display_name\": \"string\", \\n 17| \"filter_view\": { \\n 18| \"is_hidden\": true \\n 19| }, \\n 20| \"group_name\": \"string\", \\n 21| \"is_active_in_detail_view\": true, \\n 22| \"is_bulk_action_enabled\": true, \\n 23|",
"title": "Inputs — DevRev | Docs"
},
{
"id": "ART-1492_KNOWLEDGE_NODE-4",
"text": "\"is_groupable\": true, \\n 24| \"is_hidden\": true, \\n 25| \"is_hidden_during_create\": true, \\n 26| \"is_read_only\": true, \\n 27| \"is_shown_in_summary\": true, \\n 28| \"is_sortable\": true, \\n 29| \"list_view\": { \\n 30| \"is_hidden\": true \\n 31| }, \\n 32| \"placeholder\": \"string\", \\n 33| \"summary_view\": { \\n 34| \"is_hidden\": true \\n 35| }, \\n 36| \"tooltip\": \"string\" \\n 37| }, \\n 38|",
"title": "Inputs — DevRev | Docs"
},
{
"id": "ART-1630_KNOWLEDGE_NODE-9",
"text": "49| \"is_shown_in_summary\": true, \\n 50| \"is_sortable\": true, \\n 51| \"list_view\": { \\n 52| \"is_hidden\": true \\n 53| }, \\n 54| \"order\": 42, \\n 55| \"placeholder\": \"foo\", \\n 56| \"summary_view\": { \\n 57| \"is_hidden\": true \\n 58| }, \\n 59| \"tooltip\": \"foo\", \\n 60| \"unit\": \"foo\" \\n 61| }, \\n",
"title": "List Schemas Stock (Beta) — DevRev | Docs"
},
{
"id": "ART-1645_KNOWLEDGE_NODE-24",
"text": "\"ctype__customer_impact\": [ true ], \\n >| \"ctype__impacted_environments\": [ \"Prod\" ] \\n >| } \\n >| }\\'\\n[/code] \\n \\nNote that both _customer_impact_ and _impacted_environments_ are filterable fields, marked with `is_filterable: true` above.\\n\\n## Schema fragment versioning\\n\\nSchema fragments are immutable. When evolving a fragment:\\n\\n 1. A new fragment is created and chained to the older one.\\n 2. The older fragment remains intact.\\n 3. Objects referencing the",
"title": "Object customization (Beta) — DevRev | Docs"
},
{
"id": "ART-1626_KNOWLEDGE_NODE-12",
"text": "\"is_hidden_during_create\": true, \\n 87| \"is_read_only\": true, \\n 88| \"is_required\": true, \\n 89| \"is_shown_in_summary\": true, \\n 90| \"is_sortable\": true, \\n 91| \"list_view\": { \\n 92| \"is_hidden\": true \\n 93| }, \\n 94| \"order\": 42, \\n 95| \"placeholder\": \"foo\", \\n 96| \"summary_view\": { \\n 97| \"is_hidden\": true \\n",
"title": "List Schemas Custom (POST) (Beta) — DevRev | Docs"
},
{
"id": "ART-5155_KNOWLEDGE_NODE-37",
"text": "|\\n| 752 | \"group_name\": \"string\", |\\n| 753 | \"is_active_in_detail_view\": true, |\\n| 754 | \"is_bulk_action_enabled\": true, |\\n| 755 | \"is_currency_field\": true, |\\n| 756 | \"is_groupable\": true, |\\n| 757 | \"is_hidden\": true, |\\n| 758 | \"is_hidden_during_create\": true, |\\n| 759 | \"is_read_only\": true, |\\n| 760 | \"is_required\": true, |\\n| 761 | \"is_shown_in_summary\": true, |\\n| 762 | \"is_sortable\": true, |\\n| 763 | \"list_view\": { |\\n| 764 | \"is_hidden\": true |\\n| 765 | }, |\\n| 766 | \"order\": 1,",
"title": "Get Widget | DevRev | Docs"
},
{
"id": "ART-1831_KNOWLEDGE_NODE-436",
"text": "\" , 100 \" filter_view \" : { 101 \" is_hidden \" : true 102 } , 103 \" group_name \" : \" string \" , 104 \" is_active_in_detail_view \" : true , 105 \" is_bulk_action_enabled \" : true , 106 \" is_groupable \" : true , 107 \" is_hidden \" : true , 108 \" is_hidden_during_create \" : true , 109 \" is_read_only \" : true , 110 \" is_required \" : true , 111 \" is_shown_in_summary \" : true , 112 \" is_sortable \" : true , 113 \" list_view \" : { 114 \" is_hidden \" : true 115 } , 116 \" placeholder \" : \" string \" , 117 \"",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1827_KNOWLEDGE_NODE-426",
"text": "\" : true 95 } , 96 \" detail_view \" : { 97 \" is_hidden \" : true 98 } , 99 \" display_name \" : \" string \" , 100 \" filter_view \" : { 101 \" is_hidden \" : true 102 } , 103 \" group_name \" : \" string \" , 104 \" is_active_in_detail_view \" : true , 105 \" is_bulk_action_enabled \" : true , 106 \" is_groupable \" : true , 107 \" is_hidden \" : true , 108 \" is_hidden_during_create \" : true , 109 \" is_read_only \" : true , 110 \" is_required \" : true , 111 \" is_shown_in_summary \" : true , 112 \" is_sortable \" : true",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-15487_KNOWLEDGE_NODE-22",
"text": "are filterable fields,\\nmarked with `is_filterable: true` above.\\n\\nSchema fragment versioning\\n--------------------------\\n\\nSchema fragments are immutable. When evolving a fragment:\\n\\n1. A new fragment is created and chained to the older one.\\n2. The older fragment remains intact.\\n3. Objects referencing the older fragment are unaffected (more on this later).\\n\\nThe same API endpoint `schemas.custom.set` is used to create and update fragments. The\\nAPI internally figures out how to version",
"title": "Object customization | DevRev | Docs"
}
] |
b270f73d-6648-4d9a-82fe-724cd12d0fd8
|
send ticket to a contact not configured
|
[
{
"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-26",
"text": "configuration instructions, refer to [Email snap-in configuration](/docs/integrations/email-config).\\n\\nFor more information, refer to the [Email snap-in](/marketplace/email-with-tickets) on the DevRev marketplace.\\n\\nConversation and ticket creation for emails\\n-------------------------------------------\\n\\nWhen an email is received, DevRev checks if the sender is linked to your workspace and creates a conversation or ticket. If a sender is not recognized, DevRev creates a new user profile to",
"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-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-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-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-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-2027_KNOWLEDGE_NODE-32",
"text": "**Subscribers** field.\\n\\n *Is able to:* View the ticket on DevRev and receive in-app notifications.\\n* Without DevRev account\\n\\n *Added to:* **Email members** field as subscriber.\\n\\n *Is able to:* Reply to the ticket via email.\\n\\nEmail deliverability status\\n\\nThe sender of an email is able to view the status of an email. Additionally, the sender can view if their email has bounced, along with details about the bounce event.\\n\\nBelow are the various possible states of an email.\\n\\n* *In",
"title": "Email | Integrate | Snap-ins | 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-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-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-33",
"text": "members** does not remove them from the **Reported by** field.\\n\\nShadow users can also be subscribers and email members.\\n\\n* **CCed members in email**: The CCed members in emails will be added to reporters if they are contacts in the workspace to which the ticket belongs. They will be added to email members if they are part of the ongoing email thread, without any workspace restriction.\\n* **Shadow users**: Users created for tracking and record-keeping purposes that do not have access to the",
"title": "Tickets | Computer for Support Teams | DevRev"
},
{
"id": "ART-2002_KNOWLEDGE_NODE-26",
"text": "(for example Stripe as a customer of Slack) or a workspace in your software product (such as a Slack workspace).\\n\\nCreate a new customer contact\\n-----------------------------\\n\\n1. Go to **Contacts** > **+ Contact**.\\n2. Fill in the following fields as **Add Display Name, Description, Domains, Tags, Tiers**.\\n3. Click **Create**.\\n\\nWhile creating new customer records, be sure to specify the [**External Reference**](#external-reference) so customer information coming from other channels (like",
"title": "Contacts | Computer for Growth Teams | DevRev"
}
] |
84eb5821-3ddf-43c9-b238-48b8e84799ca
|
works.list endpoint reported_by query parameter usage
|
[
{
"id": "ART-1653_KNOWLEDGE_NODE-479",
"text": "returned, or if no cursor is provided, then from the end. Entries will always be returned in the specified sort-by order.\\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 strings Optional\\nFields to sort the works",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1641_KNOWLEDGE_NODE-479",
"text": "returned, or if no cursor is provided, then from the end. Entries will always be returned in the specified sort-by order.\\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 strings Optional\\nFields to sort the works",
"title": "Get Post — 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-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-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-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-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-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-1456_KNOWLEDGE_NODE-4",
"text": "cursor will be returned, or if no cursor is provided, then from the end. Entries will always be returned in the specified sort-by order.\\n\\nmodified_bylist of stringsOptional\\n\\nFilters for work modified by any of these users.\\n\\nmodified_dateobjectOptional\\n\\nProvides ways to specify date ranges on objects.\\n\\nShow 2 variants\\n\\nowned_bylist of stringsOptional\\n\\nFilters for work owned by any of these users.\\n\\nreported_bylist of stringsOptional\\n\\nFilters for work reported by any of these",
"title": "List Works (POST) — 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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-1444_KNOWLEDGE_NODE-3",
"text": "otherwise if not set, then \\xe2\\x80\\x9cafter\\xe2\\x80\\x9d is used.\\n\\nAllowed values: afterbefore\\n\\nmodified_bylist of stringsOptional\\n\\nFilters for work modified by any of these users.\\n\\nowned_bylist of stringsOptional\\n\\nFilters for work owned by any 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\\nstage.namelist of",
"title": "List Works — DevRev | Docs"
},
{
"id": "ART-1248_KNOWLEDGE_NODE-18",
"text": "\\'50\\'.\\n\\nmodeenumOptional\\n\\nThe iteration mode to use, otherwise if not set, then \"after\" is\\nused.\\n\\nAllowed values:afterbefore\\n\\nmodified\\\\_bylist of stringsOptional\\n\\nFilters for work modified by any of these users.\\n\\nowned\\\\_bylist of stringsOptional\\n\\nFilters for work owned by any 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",
"title": "List Works | DevRev | Docs"
},
{
"id": "ART-1452_KNOWLEDGE_NODE-3",
"text": "\\xe2\\x80\\x9850\\xe2\\x80\\x99, the maximum is \\xe2\\x80\\x985000\\xe2\\x80\\x99.\\n\\nissueobjectOptional\\n\\nShow 8 properties\\n\\nmodified_bylist of stringsOptional\\n\\nFilters for work modified by any of these users.\\n\\nmodified_dateobjectOptional\\n\\nProvides ways to specify date ranges on objects.\\n\\nShow 2 variants\\n\\nowned_bylist of stringsOptional\\n\\nFilters for work owned by any of these users.\\n\\nreported_bylist of stringsOptional\\n\\nFilters for work reported by any of these",
"title": "Export Works (POST) — DevRev | Docs"
},
{
"id": "ART-1245_KNOWLEDGE_NODE-17",
"text": "default is \\'50\\', the\\nmaximum is \\'5000\\'.\\n\\nissueobjectOptional\\n\\nShow 8 properties\\n\\nmodified\\\\_bylist of stringsOptional\\n\\nFilters for work modified by any of these users.\\n\\nmodified\\\\_dateobjectOptional\\n\\nProvides ways to specify date ranges on objects.\\n\\nShow 2 variants\\n\\nowned\\\\_bylist of stringsOptional\\n\\nFilters for work owned by any of these users.\\n\\nreported\\\\_bylist of stringsOptional\\n\\nFilters for work reported by any of these users.\\n\\nstageobjectOptional\\n\\nThe filter",
"title": "Export Works (POST) | 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-1804_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 — 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-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-1605_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": "Create — 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-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-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-1308_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-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-1780_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": "Get Post — 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-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-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-1792_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": "Update — DevRev | Docs"
},
{
"id": "ART-1654_KNOWLEDGE_NODE-471",
"text": "returned in the specified sort-by order.\\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 strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for",
"title": "List — 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-1834_KNOWLEDGE_NODE-450",
"text": "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 strings Optional\\nFields to",
"title": "Delete — 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-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-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-1790_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": "List Post — 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-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"
},
{
"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-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-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-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-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-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-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-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-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-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-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-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-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-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-1551_KNOWLEDGE_NODE-525",
"text": "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 strings Optional\\n\\nFilters for work reported by any of these users.\\n\\nsort_by list of strings Optional\\n\\nFields to sort the works by and the direction to sort them.\\n\\nstage object Optional\\n\\nThe filter for stages.\\n\\nShow property\\nstaged_info object",
"title": "Update (Beta) — DevRev | Docs"
},
{
"id": "ART-1564_KNOWLEDGE_NODE-525",
"text": "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 strings Optional\\n\\nFilters for work reported by any of these users.\\n\\nsort_by list of strings Optional\\n\\nFields to sort the works by and the direction to sort them.\\n\\nstage object Optional\\n\\nThe filter for stages.\\n\\nShow property\\nstaged_info object",
"title": "List (Beta) — DevRev | Docs"
},
{
"id": "ART-1838_KNOWLEDGE_NODE-451",
"text": "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 Optional\\nFilters for work",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1547_KNOWLEDGE_NODE-526",
"text": "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 strings Optional\\n\\nFilters for work reported by any of these users.\\n\\nsort_by list of strings Optional\\n\\nFields to sort the works by and the direction to sort them.\\n\\nstage object Optional\\n\\nThe filter for stages.\\n\\nShow property\\nstaged_info object",
"title": "Get Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1301_KNOWLEDGE_NODE-470",
"text": "specified sort-by order.\\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 strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1643_KNOWLEDGE_NODE-463",
"text": "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 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",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1302_KNOWLEDGE_NODE-470",
"text": "specified sort-by order.\\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 strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1549_KNOWLEDGE_NODE-525",
"text": "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 strings Optional\\n\\nFilters for work reported by any of these users.\\n\\nsort_by list of strings Optional\\n\\nFields to sort the works by and the direction to sort them.\\n\\nstage object Optional\\n\\nThe filter for stages.\\n\\nShow property\\nstaged_info object",
"title": "List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1802_KNOWLEDGE_NODE-470",
"text": "specified sort-by order.\\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 strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-4131_KNOWLEDGE_NODE-19",
"text": "variants\\n\\nowned\\\\_bylist of stringsOptional\\n\\nFilters for incidents owned by any of the provided users.\\n\\npialist of stringsOptional\\n\\nFilters for incidents with any of the provided PIAs.\\n\\nplaybookslist of stringsOptional\\n\\nFilters for incidents with any of the provided playbooks.\\n\\nrelated\\\\_docslist of stringsOptional\\n\\nFilters for incidents with any of the provided related docs.\\n\\nreported\\\\_bylist of longsOptional\\n\\nFilters for incidents with any of the provided",
"title": "List Incidents (POST) | DevRev | Docs"
},
{
"id": "ART-1804_KNOWLEDGE_NODE-470",
"text": "specified sort-by order.\\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 strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow",
"title": "Self — DevRev | Docs"
},
{
"id": "ART-1822_KNOWLEDGE_NODE-465",
"text": "\"before\", then entries before the provided cursor will be returned, or if no cursor is provided, then from the end. Entries will always be returned in the specified sort-by order.\\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",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1787_KNOWLEDGE_NODE-466",
"text": "\"before\", then entries before the provided cursor will be returned, or if no cursor is provided, then from the end. Entries will always be returned in the specified sort-by order.\\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",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1308_KNOWLEDGE_NODE-467",
"text": "specified sort-by order.\\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 strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1825_KNOWLEDGE_NODE-464",
"text": "\"before\", then entries before the provided cursor will be returned, or if no cursor is provided, then from the end. Entries will always be returned in the specified sort-by order.\\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",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1790_KNOWLEDGE_NODE-465",
"text": "specified sort-by order.\\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 strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1655_KNOWLEDGE_NODE-462",
"text": "\"before\", then entries before the provided cursor will be returned, or if no cursor is provided, then from the end. Entries will always be returned in the specified sort-by order.\\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",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1653_KNOWLEDGE_NODE-471",
"text": "subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these 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",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1785_KNOWLEDGE_NODE-464",
"text": "specified sort-by order.\\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 strings Optional\\nFields to sort the works by and the direction to sort them.\\nstage object Optional\\nThe filter for stages.\\nShow",
"title": "Create — DevRev | Docs"
}
] |
b49e43b4-a055-409a-b700-4294fa89cfe1
|
how to create new organization
|
[
{
"id": "ART-1997_KNOWLEDGE_NODE-28",
"text": "single account. This allows us to consolidate various workspaces under one account.\\n\\nTo create a new organization in DevRev:\\n\\n1. Click on your profile picture in the top left corner.\\n2. Go to the **Orgs** section and click on **+**.\\n3. Fill in the details and click **Create**.\\n4. Now you can find your newly created org in **Orgs**.\\n\\nIn modern SaaS applications, customers often create multiple workspaces for testing, production, and staging. All entities that drive support",
"title": "Computer for Growth Teams | DevRev"
},
{
"id": "ART-1211_KNOWLEDGE_NODE-1",
"text": "\"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{ |\\n| > | \"account\": \"ACC-12345\", |\\n| > | \"display_name\": \"string\" |\\n| > | }\\' |\\n```\\n\\n[Try it](/api-reference/rev-orgs/create?explorer=true)\\n\\n201Created\\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\":",
"title": "Create Rev Org | 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"
},
{
"id": "ART-1597_KNOWLEDGE_NODE-342",
"text": "Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-17213_KNOWLEDGE_NODE-2",
"text": "as the capabilities and limitations of the external system being integrated.\\n\\nDevRev organization\\n-------------------\\n\\nIf this is your first time developing a snap-in, you should start by creating a new DevRev organization:\\n\\n1. Click on your profile picture in the top left corner.\\n2. Go to the **Orgs** section and click on **+**.\\n3. Fill in the necessary details and click **Create**.\\n\\nYou now find your newly created organization under **Orgs**.\\n\\nExternal",
"title": "Getting started | DevRev | Docs"
},
{
"id": "ART-1558_KNOWLEDGE_NODE-388",
"text": "rev-orgs.create\\n\\nCreates a Rev organization in the authenticated user\\xe2\\x80\\x99s Dev organization.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\n\\nAccount Id to associate with this Rev organization.\\n\\ndisplay_name string Required\\n\\nName of the Rev organization.\\n\\nartifacts list of strings Optional\\n\\nThe IDs of the artifacts to associate with the Rev organization.\\n\\ncustom_fields map from strings to any Optional\\n\\nApplication-defined custom",
"title": "Metric Definitions List (Beta) — DevRev | Docs"
},
{
"id": "ART-1560_KNOWLEDGE_NODE-391",
"text": "rev-orgs.create\\n\\nCreates a Rev organization in the authenticated user\\xe2\\x80\\x99s Dev organization.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\n\\nAccount Id to associate with this Rev organization.\\n\\ndisplay_name string Required\\n\\nName of the Rev organization.\\n\\nartifacts list of strings Optional\\n\\nThe IDs of the artifacts to associate with the Rev organization.\\n\\ncustom_fields map from strings to any Optional\\n\\nApplication-defined custom",
"title": "Assign (Beta) — DevRev | Docs"
},
{
"id": "ART-1577_KNOWLEDGE_NODE-343",
"text": "Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1605_KNOWLEDGE_NODE-339",
"text": "rev-orgs.create\\ncURL\\n$ curl -X POST https://api.devrev.ai/rev-orgs.create \\\\ > -H \" Authorization: Bearer <token> \" \\\\ > -H \" Content-Type: application/json \" \\\\ > -d \\' { > \"account\": \"ACC-12345\", > \"display_name\": \"display_name\" > } \\'\\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 \"",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1211_KNOWLEDGE_NODE-0",
"text": "b'Create 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\\nCreate Rev Org\\n==============\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/rev-orgs.create\\n\\nPOST\\n\\n/rev-orgs.create\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/rev-orgs.create \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -H",
"title": "Create Rev Org | DevRev | Docs"
},
{
"id": "ART-1407_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# Create Rev Org\\n\\nPOST\\n\\nhttps://api.devrev.ai/rev-orgs.create\\n\\nTry it\\n\\nCreates a Rev organization in the authenticated user\\xe2\\x80\\x99s Dev organization.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\naccountstringRequired`format:",
"title": "Create Rev Org — DevRev | Docs"
},
{
"id": "ART-1371_KNOWLEDGE_NODE-2",
"text": "collection](https://postman.devrev.ai/).\\n\\n[](https://postman.devrev.ai/)\\n[code]\\n\\n https://api.devrev.ai \\n ---\\n[/code] \\n \\nYou can use the DevRev API in test a demo organization which doesn\\xe2\\x80\\x99t affect your live data or interact with your real customers.\\n\\nTo create a new organization in DevRev:\\n\\n 1. Click on your profile picture on the top left corner.\\n 2. Go to the **Orgs** section and click on **+**.\\n 3. Fill in the details and click **Create**.\\n\\nNow you can",
"title": "Getting started — DevRev | Docs"
},
{
"id": "ART-1306_KNOWLEDGE_NODE-340",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1821_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1211_KNOWLEDGE_NODE-4",
"text": "\"id\": \"string\", |\\n| 47 | \"display_name\": \"string\" |\\n| 48 | }, |\\n| 49 | \"domain\": \"string\" |\\n| 50 | } |\\n| 51 | } |\\n```\\n\\nCreates a Rev organization in the authenticated user\\'s Dev\\norganization.\\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\\naccountstringRequired`format: \"id\"`\\n\\nAccount Id to associate with this Rev",
"title": "Create Rev Org | DevRev | Docs"
},
{
"id": "ART-1782_KNOWLEDGE_NODE-337",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1593_KNOWLEDGE_NODE-343",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1637_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1607_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1829_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1302_KNOWLEDGE_NODE-343",
"text": "authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ncustom_schema_fragments list of strings Optional\\nSchema fragment IDs associated with",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1787_KNOWLEDGE_NODE-339",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1827_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1652_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1303_KNOWLEDGE_NODE-340",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Export Post — DevRev | Docs"
},
{
"id": "ART-1785_KNOWLEDGE_NODE-337",
"text": "authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ncustom_schema_fragments list of strings Optional\\nSchema fragment IDs associated with",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1609_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1509_KNOWLEDGE_NODE-337",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Prepare — DevRev | Docs"
},
{
"id": "ART-1804_KNOWLEDGE_NODE-343",
"text": "authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ncustom_schema_fragments list of strings Optional\\nSchema fragment IDs associated with",
"title": "Self — DevRev | Docs"
},
{
"id": "ART-1837_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1639_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Export Post — DevRev | Docs"
},
{
"id": "ART-1592_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1828_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1643_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1651_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1783_KNOWLEDGE_NODE-337",
"text": "authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from strings to any Optional\\nApplication-defined custom fields.\\ncustom_schema_fragments list of strings Optional\\nSchema fragment IDs associated with",
"title": "Locate — DevRev | Docs"
},
{
"id": "ART-1305_KNOWLEDGE_NODE-342",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1825_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1826_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1838_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1588_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1830_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1636_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1649_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1831_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1822_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1823_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1633_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1579_KNOWLEDGE_NODE-336",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1650_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1836_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1824_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1605_KNOWLEDGE_NODE-336",
"text": "\" , 9 \" suggested_answer \" : \" suggested_answer \" , 10 \" suggested_for_deletion \" : true , 11 \" topic \" : \" topic \" , 12 \" verified \" : true 13 } 14 }\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1833_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1832_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1653_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1641_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1834_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1211_KNOWLEDGE_NODE-5",
"text": "organization.\\n\\ndisplay\\\\_namestringRequired`format: \"text\"`\\n\\nName of the Rev organization.\\n\\ndescriptionstringOptional`format: \"text\"`\\n\\nDescription of the Rev organization.\\n\\nenvironmentenumOptional\\n\\nThe environment of the Org. Defaults to \\'production\\' if not specified.\\n\\nAllowed values:productionstagingtest\\n\\nexternal\\\\_refstringOptional`format: \"text\"`\\n\\nExternal ref is a custom unique identifier which is a reference to\\nan unique id for this organization\\'s data in some system",
"title": "Create Rev Org | DevRev | Docs"
},
{
"id": "ART-1654_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1590_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1835_KNOWLEDGE_NODE-335",
"text": "object\\nShow 12 properties\\nAPI Reference rev-orgs Create.\\n\\nPOST https:// api.devrev.ai / rev-orgs.create\\nCreates a Rev organization in the authenticated user\\'s Dev organization.\\nRequest.\\n\\nThis endpoint expects an object.\\naccount string Required\\nAccount Id to associate with this Rev organization.\\ndisplay_name string Required\\nName of the Rev organization.\\nartifacts list of strings Optional\\nThe IDs of the artifacts to associate with the Rev organization.\\ncustom_fields map from",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1175_KNOWLEDGE_NODE-2",
"text": "[Postman collection](https://postman.devrev.ai/).\\n\\n[![]()](https://postman.devrev.ai/)\\n\\n```\\n| |\\n| --- |\\n| https://api.devrev.ai |\\n```\\n\\nYou can use the DevRev API in test a demo organization which doesn\\xe2\\x80\\x99t affect your live data or interact with your real customers.\\n\\nTo create a new organization in DevRev:\\n\\n1. Click on your profile picture on the top left corner.\\n2. Go to the **Orgs** section and click on **+**.\\n3. Fill in the details and click **Create**.\\n\\nNow you",
"title": "Getting started | 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"
}
] |
5cb55f9b-47ee-4c04-94bc-51ceab24eaa8
|
show all tickets created in the last week
|
[
{
"id": "ART-1835_KNOWLEDGE_NODE-450",
"text": "task ticket\\nFilters for work of the provided types.\\nactual_close_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\napplies_to_part list of strings Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by list of strings Optional\\nFilters for work created by any of these users.\\ncreated_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\ncustom_fields map from strings to any Optional\\nFilters for",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1564_KNOWLEDGE_NODE-508",
"text": "ticket\\n\\nFilters for work of the provided types.\\n\\nactual_close_date object Optional\\n\\nProvides ways to specify date ranges on objects.\\n\\nShow 2 variants\\napplies_to_part list of strings Optional\\n\\nFilters for work belonging to any of the provided parts.\\n\\ncreated_by list of strings Optional\\n\\nFilters for work created by any of these users.\\n\\ncreated_date object Optional\\n\\nProvides ways to specify date ranges on objects.\\n\\nShow 2 variants\\ncustom_fields map from strings to any",
"title": "List (Beta) — DevRev | Docs"
},
{
"id": "ART-1609_KNOWLEDGE_NODE-465",
"text": "opportunity task ticket\\nFilters for work of the provided types.\\nactual_close_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\napplies_to_part list of strings Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by list of strings Optional\\nFilters for work created by any of these users.\\ncreated_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\ncursor string Optional\\nThe cursor to resume",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1509_KNOWLEDGE_NODE-462",
"text": "opportunity task ticket\\nFilters for work of the provided types.\\nactual_close_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\napplies_to_part list of strings Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by list of strings Optional\\nFilters for work created by any of these users.\\ncreated_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\ncursor string Optional\\nThe cursor to resume",
"title": "Prepare — DevRev | Docs"
},
{
"id": "ART-1579_KNOWLEDGE_NODE-461",
"text": "opportunity task ticket\\nFilters for work of the provided types.\\nactual_close_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\napplies_to_part list of strings Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by list of strings Optional\\nFilters for work created by any of these users.\\ncreated_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\ncursor string Optional\\nThe cursor to resume",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1828_KNOWLEDGE_NODE-462",
"text": "opportunity task ticket\\nFilters for work of the provided types.\\nactual_close_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\napplies_to_part list of strings Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by list of strings Optional\\nFilters for work created by any of these users.\\ncreated_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\ncursor string Optional\\nThe cursor to resume",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1593_KNOWLEDGE_NODE-468",
"text": "opportunity task ticket\\nFilters for work of the provided types.\\nactual_close_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\napplies_to_part list of strings Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by list of strings Optional\\nFilters for work created by any of these users.\\ncreated_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\ncursor string Optional\\nThe cursor to resume",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1306_KNOWLEDGE_NODE-465",
"text": "opportunity task ticket\\nFilters for work of the provided types.\\nactual_close_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\napplies_to_part list of strings Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by list of strings Optional\\nFilters for work created by any of these users.\\ncreated_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\ncursor string Optional\\nThe cursor to resume",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1825_KNOWLEDGE_NODE-462",
"text": "opportunity task ticket\\nFilters for work of the provided types.\\nactual_close_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\napplies_to_part list of strings Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by list of strings Optional\\nFilters for work created by any of these users.\\ncreated_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\ncursor string Optional\\nThe cursor to resume",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1827_KNOWLEDGE_NODE-471",
"text": "opportunity task ticket\\nFilters for work of the provided types.\\nactual_close_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\napplies_to_part list of strings Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by list of strings Optional\\nFilters for work created by any of these users.\\ncreated_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\ncursor string Optional\\nThe cursor to resume",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1577_KNOWLEDGE_NODE-468",
"text": "opportunity task ticket\\nFilters for work of the provided types.\\nactual_close_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\napplies_to_part list of strings Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by list of strings Optional\\nFilters for work created by any of these users.\\ncreated_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\ncursor string Optional\\nThe cursor to resume",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1652_KNOWLEDGE_NODE-447",
"text": "values: issue opportunity task ticket\\nFilters for work of the provided types.\\nactual_close_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\napplies_to_part list of strings Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by list of strings Optional\\nFilters for work created by any of these users.\\ncreated_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\ncustom_fields map from strings to",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1838_KNOWLEDGE_NODE-450",
"text": "Optional\\nAllowed values: issue opportunity task ticket\\nFilters for work of the provided types.\\nactual_close_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\napplies_to_part list of strings Optional\\nFilters for work belonging to any of the provided parts.\\ncreated_by list of strings Optional\\nFilters for work created by any of these users.\\ncreated_date object Optional\\nProvides ways to specify date ranges on objects.\\nShow 2 variants\\ncustom_fields",
"title": "List Post — DevRev | Docs"
}
] |
f6818a4c-cadb-4f21-bc84-a8fbbad2cb83
|
MS Teams integration Snap-In similar to Slack
|
[
{
"id": "ART-4216_KNOWLEDGE_NODE-27",
"text": "**Marketplace**, search for **Microsoft Teams**, and install the snap-in.\\n2. In the snap-in config modal, click **Install** then go to the **AirSyncs** section in your settings left nav.\\n3. Click **+Import** and select the Microsoft Teams logo.\\n4. Create a new connection to your Microsoft Teams account, or use an existing connection if you already have one.\\n5. Once the connection is established, select the Microsoft Teams team you want to import and specify the DevRev part that should be",
"title": "Microsoft Teams AirSync | AirSync | Snap-ins | DevRev"
},
{
"id": "ART-1272_KNOWLEDGE_NODE-4",
"text": "an event source to subscribe to GitHub/Slack/any external events.\\n\\nSnap-in package\\n---------------\\n\\nA snap-in package is a collection of DevRev objects and their relationships that describe the functionality of the developed snap-in.\\nIt doesn\\xe2\\x80\\x99t reference an object within the installer\\xe2\\x80\\x99s dev org. It\\xe2\\x80\\x99s a parent object collecting snap-in versions. A good analogy for a snap-in package is an Andriod/iOS app which can house different versions of the",
"title": "Concepts | DevRev | Docs"
},
{
"id": "ART-4216_KNOWLEDGE_NODE-25",
"text": "syncs.\\n\\nSetting up the Microsoft Teams connection\\n-----------------------------------------\\n\\nTo configure the Microsoft Teams connection, you need to use OAuth authentication. Access to a Microsoft Teams admin account is required.\\n\\nSupported objects\\n-----------------\\n\\nThe following is a list of Microsoft Teams objects and their corresponding DevRev equivalents. Those marked as **Sync to DevRev** are eligible for import from Microsoft Teams to DevRev.\\n\\n| Microsoft Teams Object |",
"title": "Microsoft Teams AirSync | AirSync | Snap-ins | DevRev"
},
{
"id": "ART-4216_KNOWLEDGE_NODE-31",
"text": "established it is no longer available.\\n\\n### Sync to DevRev\\n\\nAfter a successful import from a Microsoft Teams team, you can choose to sync the imported data with DevRev. This feature airdrops any new channels, messages, users, tasks, and any changes made to previously imported items from Microsoft Teams.\\n\\nTo perform a one-time sync to DevRev, follow these steps:\\n\\n1. Go to **Settings** > **Integrations** > **AirSyncs**.\\n2. Locate the previously imported team.\\n3. Select the",
"title": "Microsoft Teams AirSync | AirSync | Snap-ins | DevRev"
},
{
"id": "ART-16806_KNOWLEDGE_NODE-29",
"text": "allowing you to search and add actions without leaving your current task, making the process smoother and more efficient. Currently, you can install Slack actions, with more coming soon!\\n\\n![]()\\xc2\\xa0For more information about *Marketplace*, refer to the following article: [Convergence | Automate | Snap-ins](/docs/automations/converge)\\n\\n![]()\\n\\n### PLuG\\n\\n**Ability to Insert an Article in RTE**:\\n\\nUsers can now add an article link via the **Insert Article** button in the RTE, allowing",
"title": "July 2025 | Changelog | DevRev"
},
{
"id": "ART-4216_KNOWLEDGE_NODE-26",
"text": "DevRev Object | Sync to DevRev |\\n| --- | --- | --- |\\n| Plan | Parts | \\xe2\\x9c\\x85 |\\n| User | Identity/DevUser | \\xe2\\x9c\\x85 |\\n| Channel | Chat | \\xe2\\x9c\\x85 |\\n| Attachments in Message/Thread/Task | Artifacts on Article | \\xe2\\x9c\\x85 |\\n| Message | Comment | \\xe2\\x9c\\x85 |\\n| Thread | Comment | \\xe2\\x9c\\x85 |\\n| Task | Issue/Ticket | \\xe2\\x9c\\x85 |\\n\\nImporting from Microsoft Teams\\n------------------------------\\n\\nFollow the steps below to import from Microsoft Teams:\\n\\n1. Go to",
"title": "Microsoft Teams AirSync | AirSync | Snap-ins | DevRev"
},
{
"id": "ART-10696_KNOWLEDGE_NODE-21",
"text": "- [Zoho Projects AirSync](/docs/integrations/zoho)\\n - [Microsoft Teams AirSync](/docs/integrations/ms-teams)\\n - [Azure DevOps Wikis AirSync](/docs/integrations/azure-wiki)\\n - [Jira Software AirSync](/docs/integrations/jira)\\n\\n * [DevRev for Jira app](/docs/integrations/jira-plugin)\\n - [Linear AirSync](/docs/integrations/linear)\\n - [ClickUp AirSync](/docs/integrations/clickup)\\n - [Azure Boards AirSync](/docs/integrations/azure-boards)\\n - [GitBook",
"title": "Tracxn Integration | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-4216_KNOWLEDGE_NODE-30",
"text": "after the last sync or import.\\n* **View Report** \\n This option allows you to access detailed information about the initial import and any subsequent syncs performed.\\n* **Delete Import** \\n If you want to remove the import and all items that were imported from Microsoft Teams into DevRev, you can use this option.\\n* **Edit Connection** \\n Use this option to change the connection used for any subsequent actions. It can be helpful if a connection becomes inactive or the user who",
"title": "Microsoft Teams AirSync | AirSync | Snap-ins | DevRev"
}
] |
284afbd1-35fb-4ca2-9ccf-28195cb26755
|
editor glitching out after hitting edit on article
|
[
{
"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"
}
] |
3a284469-5858-4720-b27a-b55ff842be9d
|
send CSAT survey more than once from CSAT on-Ticket Snap-In manual resend
|
[
{
"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-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-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-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"
}
] |
d53bb282-1e6e-401b-9fff-a161628b3f1a
|
Mobile-responsive design with native mobile app support
|
[
{
"id": "ART-1474_KNOWLEDGE_NODE-6",
"text": "the application should utilize the showSupport API, as shown below:\\n\\n1 DevRev. showSupport (context: Context ) Support button.\\n\\nThe mobile SDK also offers a support button that can be integrated into your application. To include it on the current screen, add the following code to your XML layout:\\n\\n<ai.devrev.sdk..view.FloatingActionButton android:id=\"@+id/_fab\" android:layout_width=\"wrap_content\" android:layout_height=\"wrap_content\" android:layout_margin=\"24dp\"",
"title": "Integrate PLuG with your Android app — DevRev | Docs"
},
{
"id": "ART-2898_KNOWLEDGE_NODE-15",
"text": "to tailor its appearance to your application\\xe2\\x80\\x99s design.\\n\\n[code]\\n\\n 1| android:src=\"@your_drawable_here\" \\n ---|---\\n[/code] \\n \\nand\\n\\n[code]\\n\\n 1| android:backgroundTint=\"@your_background_color\" \\n ---|---\\n[/code] \\n \\nAt this stage, your app is fully configured to utilize all functionalities of the DevRev PLuG SDK. Pressing the support button directs the user to the chat interface, enabling effective interaction and support.\\n\\n## Analytics\\n\\nThe DevRev SDK",
"title": "Android integration — DevRev | Docs"
},
{
"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-1474_KNOWLEDGE_NODE-7",
"text": "app:layout_constraintBottom_toBottomOf=\"parent\" app:layout_constraintEnd_toEndOf=\"parent\" />\\n\\nThe support button accepts default parameters like:\\n\\n1 android: src = \"@your_drawable_here\"\\n\\nor\\n\\n1 android: backgroundTint = \"@your_background_color\"\\n\\nThis allows customization according to your preferences. The button appears on your screen.\\n\\nAt this stage, you should be able to run the app and leverage all the features of the DevRev SDK. Clicking the Support. button navigates the user to",
"title": "Integrate PLuG with your Android app — DevRev | Docs"
},
{
"id": "ART-12456_KNOWLEDGE_NODE-5",
"text": "notifications](/public/sdks/react-native/features#unregister-from-push-notifications)\\n * [Processing push notifications](/public/sdks/react-native/features#processing-push-notifications)\\n * [Android](/public/sdks/react-native/features#android)\\n * [iOS](/public/sdks/react-native/features#ios)\\n * [Screen transition tracking (Android only)](/public/sdks/react-native/features#screen-transition-tracking-android-only)\\n\\n[SDKs](/public/sdks)[DevRev SDK for React Native and",
"title": "Features — 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-2982_KNOWLEDGE_NODE-10",
"text": "chat feature can be shown as a modal screen from the top-most screen.\\n\\n#####\\n\\nThis functionality requires 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() \\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",
"title": "React Native integration — DevRev | Docs"
},
{
"id": "ART-1353_KNOWLEDGE_NODE-4",
"text": "other system.\\n\\n\\xf0\\x9f\\x92\\xbb SDKs\\n------\\n\\n### Web\\n\\n[Plug Web SDK](/sdks/web/installation)\\n\\n### Mobile\\n\\n[DevRev SDK for Android](/sdks/mobile/android/quickstart)[DevRev SDK for iOS](/sdks/mobile/ios/quickstart)[DevRev SDK for React Native and Expo](/sdks/mobile/react-native/quickstart)[DevRev SDK for Cordova](/sdks/mobile/cordova/quickstart)[DevRev SDK for Flutter](/sdks/mobile/flutter/quickstart)\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[####",
"title": "For Developers | DevRev | Docs"
},
{
"id": "ART-12476_KNOWLEDGE_NODE-6",
"text": "concurrent operations.\\n\\nComprehensive Documentation: The DevRev SDK is supported by extensive documentation, including detailed migration guides, integration instructions, and a complete API reference.\\n\\nIllustrative Sample Codebases: To aid in implementation, sample codebases are provided for all supported platforms, demonstrating best practices and common usage patterns.\\n\\nBroader Framework Compatibility: In addition to React Native, the DevRev SDK offers support for Expo, providing",
"title": "The Future of Sessions - Powered By DevRev"
},
{
"id": "ART-15489_KNOWLEDGE_NODE-1",
"text": "SDK](/sdks/web/installation)\\n\\n### Mobile\\n\\n[DevRev SDK for Android](/sdks/mobile/android/quickstart)[DevRev SDK for iOS](/sdks/mobile/ios/quickstart)[DevRev SDK for React Native and Expo](/sdks/mobile/react-native/quickstart)[DevRev SDK for Cordova](/sdks/mobile/cordova/quickstart)[DevRev SDK for Flutter](/sdks/mobile/flutter/quickstart)\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/guides/custom-objects)[#### Install the Web SDK\\n\\nNext](/sdks/web/installation)[Built",
"title": "SDKs | DevRev | Docs"
},
{
"id": "ART-15505_KNOWLEDGE_NODE-4",
"text": "repository](https://github.com/devrev/devrev-sdk-react-native). To set up and run the sample app:\\n\\n1. Go to the sample directory:\\n\\n ```\\n | | |\\n | --- | --- |\\n | 1 | cd sample |\\n ```\\n2. Install dependencies:\\n\\n ```\\n | | |\\n | --- | --- |\\n | 1 | yarn install |\\n ```\\n3. For iOS, run:\\n\\n ```\\n | | |\\n | --- | --- |\\n | 1 | cd ios |\\n | 2 | pod install |\\n ```\\n4. Run the app on Android or iOS using:\\n\\n ```\\n | | |\\n | --- | --- |\\n | 1",
"title": "Quickstart guide (React Native) | DevRev | Docs"
},
{
"id": "ART-4254_KNOWLEDGE_NODE-1",
"text": "demo](https://devrev.ai/request-a-demo)\\n\\n#\\n\\nSDKs\\n\\nThe DevRev SDK is a powerful tool designed to further enhance our widget on your website or application. With this SDK, you can integrate DevRev\\xe2\\x80\\x99s feature-rich widget, allowing you to create a dynamic and personalized user experience.\\n\\n[PLuG Web SDK](/public/sdks/web/installation)[DevRev SDK for Android](/sdks/mobile/android/quickstart)[DevRev SDK for iOS](/sdks/mobile/ios/quickstart)[DevRev SDK for React Native and",
"title": "SDKs — DevRev | Docs"
},
{
"id": "ART-12461_KNOWLEDGE_NODE-4",
"text": "DevRev.configure(appID, successCallback, errorCallback) \\n ---|---\\n[/code] \\n \\n## Sample app\\n\\nA sample app with use cases for the DevRev Cordova plugin is provided as part of our [public repository](https://github.com/devrev/devrev-sdk-cordova). To set up and run the sample app:\\n[code]\\n\\n 1| cd sample \\n ---|--- \\n 2| npm install \\n 3| cordova platform add android \\n 4| cordova platform add ios\\n[/code] \\n \\n###### Android\\n\\n###### iOS\\n\\n[code]\\n\\n 1|",
"title": "Quickstart guide — DevRev | Docs"
},
{
"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-2115_KNOWLEDGE_NODE-0",
"text": "b\"However, there are several key differentiators between PLuG Session Analytics and Mixpanel: 1. Support for Extensive Mobile Framework : According to Mixpanel's documentation, their mobile native SDK is still in beta for iOS, and Android support is expected next year. There's no timeline for other frameworks yet. In contrast, PLuG already offers robust support across multiple mobile frameworks. \\xc2\\xa0 \\xc2\\xa0 2. Missing Heatmap Feature: Mixpanel currently does not offer a heatmap feature,",
"title": "MixPanel vs DevRev Session Replay"
},
{
"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-2901_KNOWLEDGE_NODE-16",
"text": "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: 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",
"title": "iOS integration — DevRev | Docs"
},
{
"id": "ART-2901_KNOWLEDGE_NODE-14",
"text": "7| // Update the user\\'s information. \\n 8| await DevRev.updateUser(Identity(organizationID: \"organization-1337\"))\\n[/code] \\n \\n## PLuG support chat\\n\\n### UIKit\\n\\nThe support chat feature can be shown as a modal screen from a specific 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",
"title": "iOS integration — DevRev | Docs"
},
{
"id": "ART-12449_KNOWLEDGE_NODE-14",
"text": "DevRev.createSupportConversation(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": "Features — DevRev | Docs"
},
{
"id": "ART-15505_KNOWLEDGE_NODE-3",
"text": "ID**.\\n3. Configure the DevRev SDK in your app using the obtained credentials.\\n\\n##### \\n\\nThe DevRev SDK must be configured before you can use any of its features.\\n\\nThe SDK becomes ready for use once the following configuration method is executed.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | DevRev.configure(appID: string) |\\n```\\n\\nSample app\\n----------\\n\\nA sample app with use cases for the DevRev React Native plugin has been provided as a part of our [public",
"title": "Quickstart guide (React Native) | DevRev | Docs"
},
{
"id": "ART-15505_KNOWLEDGE_NODE-2",
"text": "[GitHub](https://docs.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh).\\n\\nInstallation\\n------------\\n\\nTo install the DevRev SDK, run the following command:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | npm install @devrev/sdk-react-native |\\n```\\n\\nSet up the DevRev SDK\\n---------------------\\n\\n1. Open the DevRev web app at [https://app.devrev.ai](https://app.devrev.ai/) and go to the **Settings** page.\\n2. Under **Plug settings** copy the value under **Your unique App",
"title": "Quickstart guide (React Native) | DevRev | Docs"
},
{
"id": "ART-15517_KNOWLEDGE_NODE-5",
"text": "sample directory:\\n\\n ```\\n | | |\\n | --- | --- |\\n | 1 | cd sample |\\n ```\\n2. Install dependencies:\\n\\n ```\\n | | |\\n | --- | --- |\\n | 1 | yarn install |\\n ```\\n3. Run clean and prebuild:\\n\\n ```\\n | | |\\n | --- | --- |\\n | 1 | npx expo prebuild --clean |\\n ```\\n4. Run the app On Android:\\n\\n ```\\n | | |\\n | --- | --- |\\n | 1 | npx expo run:android |\\n ```\\n\\n OR open `android` in Android Studio and run the app.\\n5. Run the app On iOS:\\n\\n",
"title": "Quickstart guide (Expo) | 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-15513_KNOWLEDGE_NODE-24",
"text": "Kotlin\\n\\n###### Java\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | DevRev.showSupport(context: Context) |\\n```\\n\\n### Create a new conversation\\n\\nYou have the ability to create a new conversation from within your app. The method shows the support chat screen and creates a new conversation at the same time.\\n\\n###### Kotlin\\n\\n###### Java\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | DevRev.createSupportConversation(context: Context) |\\n```\\n\\n### Support button\\n\\nThe DevRev SDK also provides a support",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-12454_KNOWLEDGE_NODE-4",
"text": "provided as a part of our [public repository](https://github.com/devrev/devrev-sdk-react-native). To set up and run the sample app:\\n\\n 1. Go to the sample directory:\\n[code] 1| cd sample \\n ---|---\\n[/code] \\n \\n 2. Install dependencies:\\n[code] 1| yarn install \\n ---|---\\n[/code] \\n \\n 3. For iOS, run:\\n[code] 1| cd ios \\n ---|--- \\n 2| pod install\\n[/code] \\n \\n 4. Run the app on Android or iOS using:\\n[code] 1| npx react-native start \\n",
"title": "Quickstart guide for React Native — DevRev | Docs"
},
{
"id": "ART-1463_KNOWLEDGE_NODE-7",
"text": ")\\n\\nIf a UIViewController is provided as the from parameter, the screen is presented modally.\\n\\nIf a UINavigationController is provided as the from parameter, the screen is pushed onto the navigation stack.\\n\\nFor example:\\n\\n1 DevRev. showSupport ( from : mainViewController )\\n\\nSwiftUI. :\\n\\nFor SwiftUI apps, a dedicated view is provided. Use the public view property:\\n\\n1 DevRev.supportView`\\n\\nNew conversation callback. :\\n\\nFor convenience, a callback closure is added, so the host app",
"title": "Integrate PLuG with your iOS app — DevRev | Docs"
},
{
"id": "ART-2901_KNOWLEDGE_NODE-17",
"text": "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 \\nThis allows your app to access the ID of the newly created conversation.\\n\\nFor example:\\n\\n[code]\\n\\n 1| DevRev.conversationCreatedCompletion = {",
"title": "iOS integration — DevRev | Docs"
},
{
"id": "ART-12454_KNOWLEDGE_NODE-2",
"text": "app](/public/sdks/react-native/quickstart#sample-app)\\n\\n[SDKs](/public/sdks)[DevRev SDK for React Native and Expo](/public/sdks/react-native/quickstart)\\n\\n#\\n\\nQuickstart guide for React Native\\n\\nThis guide helps you integrate the DevRev SDK into your React Native app.\\n\\n## Installation\\n\\nTo install the DevRev SDK, run the following command:\\n\\n[code]\\n\\n 1| npm install @devrev/sdk-react-native \\n ---|---\\n[/code] \\n \\n## Set up the DevRev SDK\\n\\n 1. Open the DevRev web app at",
"title": "Quickstart guide for React Native — DevRev | Docs"
},
{
"id": "ART-2898_KNOWLEDGE_NODE-3",
"text": "notifications](/public/sdks/mobile/android#handle-push-notifications)\\n * [Troubleshooting](/public/sdks/mobile/android#troubleshooting)\\n\\n[SDKs](/public/sdks/web/overview)[Mobile SDK](/public/sdks/mobile/android)\\n\\n#\\n\\nAndroid integration\\n\\nThis section describes the process of integrating PLuG using the DevRev SDK with your Android app.\\n\\n## Requirements\\n\\n * Android Studio 2022.1.1 or later\\n * Android Gradle plugin version 7.4 or later\\n * Gradle version 7.6 or later\\n * Minimum",
"title": "Android integration — 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-2901_KNOWLEDGE_NODE-4",
"text": "[Troubleshooting](/public/sdks/mobile/ios#troubleshooting)\\n\\n[SDKs](/public/sdks/web/overview)[Mobile SDK](/public/sdks/mobile/android)\\n\\n#\\n\\niOS integration\\n\\nThis section describes the process of integrating PLuG using the DevRev SDK with your iOS app.\\n\\n## Requirements\\n\\n * Xcode 16.0 or higher (latest stable version available on the App Store).\\n * Swift 5.9 or later.\\n * Set the minimum deployment target for your iOS application as iOS 15.\\n\\n## Integration\\n\\nThe DevRev SDK can",
"title": "iOS integration — DevRev | Docs"
},
{
"id": "ART-1463_KNOWLEDGE_NODE-4",
"text": "appID:secret:supportID: )\\n\\nFor example:\\n\\n1 DevRev. configure ( appID : appID, secret : secret, supportID : supportID ) For UIKit apps, configure the SDK within the AppDelegate.application(_:didFinishLaunchingWithOptions:) method.\\nFor SwiftUI apps, depending on your app\\xe2\\x80\\x99s architecture, perform SDK configuration either at the entry point or in the initial view of the app.\\nUser identification.\\n\\nTo use specific SDK features, user identification is mandatory. Follow these steps to",
"title": "Integrate PLuG with your iOS app — DevRev | Docs"
},
{
"id": "ART-1463_KNOWLEDGE_NODE-6",
"text": "foo@example.org \" )) Place the identification function appropriately in your app, preferably after the user logs in. If user information is available at app launch, invoke the function following the DevRev.configure(appID:secret:supportID:) method.\\nPLuG support chat.\\n\\nUIKit. :\\n\\nThe support chat feature in UIKit can be displayed either as a modal screen or pushed onto a navigation stack.\\n\\nTo show the support screen, use the overloaded method:\\n\\n1 DevRev. showSupport ( from:isAnimated:",
"title": "Integrate PLuG with your iOS app — DevRev | Docs"
},
{
"id": "ART-15517_KNOWLEDGE_NODE-3",
"text": "\"@devrev/sdk-react-native-expo-plugin\" |\\n | 5 | ] |\\n | 6 | } |\\n | 7 | } |\\n ```\\n3. Rebuild your app:\\n\\n ```\\n | | |\\n | --- | --- |\\n | $ | npx expo prebuild --clean |\\n ```\\n\\nSet up the DevRev SDK\\n---------------------\\n\\n1. Open the DevRev web app at [https://app.devrev.ai](https://app.devrev.ai/) and go to the **Settings** page.\\n2. Under **Plug settings** copy the value under **Your unique App ID**.\\n3. Configure the DevRev SDK in your app using the obtained",
"title": "Quickstart guide (Expo) | DevRev | Docs"
},
{
"id": "ART-15517_KNOWLEDGE_NODE-1",
"text": "Expo](/sdks/react-native/quickstart)\\n\\nQuickstart guide for Expo\\n=========================\\n\\nCopy page\\n\\nDevRev SDK, used for integrating DevRev services into your Expo app.\\n\\nRequirements\\n------------\\n\\n* React Native 0.79.0 or later.\\n* For Expo apps, Expo 50.0.0 or later.\\n* Android: minimum API level 24.\\n* iOS: minimum deployment target 15.1.\\n* Recommended: A locally configured SSH key registered on",
"title": "Quickstart guide (Expo) | 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-4257_KNOWLEDGE_NODE-15",
"text": "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: settingsViewController) \\n 6| \\n 7| // Show the support chat screen from the top-most",
"title": "DevRev SDK for iOS — DevRev | Docs"
},
{
"id": "ART-4256_KNOWLEDGE_NODE-20",
"text": "how users navigate through your app. Although view controllers are automatically tracked, you can manually track screens using the following method:\\n\\n[code]\\n\\n 1| DevRev.trackScreen(name: string) \\n ---|---\\n[/code] \\n \\n## Push notifications\\n\\nYou can configure your app to receive push notifications from the DevRev SDK. The SDK is able to handle push notifications and execute actions based on the notification\\xe2\\x80\\x99s content.\\n\\nThe DevRev backend sends push notifications to",
"title": "DevRev SDK for React Native — DevRev | Docs"
},
{
"id": "ART-4257_KNOWLEDGE_NODE-14",
"text": "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 display the support chat screen from the top-most view controller, use the following",
"title": "DevRev SDK for iOS — DevRev | Docs"
},
{
"id": "ART-15515_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\\n### UIKit\\n\\nThe support chat feature can be shown as a modal screen from a specific 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",
"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-1978_KNOWLEDGE_NODE-26",
"text": "online platform that enables your customers to interact with your support team, create support tickets, track the progress of their requests, and engage in conversations related to their issues. It serves as a centralized hub for managing customer support inquiries efficiently.\\n\\nThe customer portal is available in both web and mobile formats (Android and iOS). It enables end users to access support articles, manage tickets, and interact with the support team.\\n\\nBenefits of using the customer",
"title": "Customer portal | Computer for Support Teams | DevRev"
},
{
"id": "ART-15501_KNOWLEDGE_NODE-6",
"text": "method is executed.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | DevRev.configure(appID:) |\\n```\\n\\nFor example:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | DevRev.configure(appID: \"abcdefg12345\") |\\n```\\n\\n* UIKit apps\\n\\nConfigure the SDK in the `AppDelegate.application(_:didFinishLaunchingWithOptions:)` method.\\n\\n* SwiftUI apps\\n\\nDepending on your app\\xe2\\x80\\x99s architecture, configure the SDK at the app\\xe2\\x80\\x99s entry point or initial view.\\n\\nSample app\\n----------\\n\\nA sample app with use",
"title": "Quickstart guide | DevRev | Docs"
}
] |
2b14ecd6-3175-4965-897b-c465916618a6
|
DevRev customer UI and how to create it when using DevRev as backend
|
[
{
"id": "ART-15501_KNOWLEDGE_NODE-7",
"text": "cases for both UIKit and SwiftUI has been provided as part of our [public repository](https://github.com/devrev/devrev-sdk-ios).\\n\\nBefore you start using the sample app you will need to configure it to be used with your Apple Developer team and your DevRev credentials. For your convenience the code has been marked with compiler error directives (`#error`) at the places that need attention.\\n\\n1. Add your credentials to the relevant `AppDelegate.swift` of the SwiftUI or UIKit sample.\\n *",
"title": "Quickstart guide | DevRev | Docs"
},
{
"id": "ART-2901_KNOWLEDGE_NODE-17",
"text": "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 \\nThis allows your app to access the ID of the newly created conversation.\\n\\nFor example:\\n\\n[code]\\n\\n 1| DevRev.conversationCreatedCompletion = {",
"title": "iOS integration — DevRev | Docs"
},
{
"id": "ART-15501_KNOWLEDGE_NODE-5",
"text": "your project, making it ready for use.\\n\\nSet up the DevRev SDK\\n---------------------\\n\\n1. Open the DevRev web app at [https://app.devrev.ai](https://app.devrev.ai/) and go to the **Settings** page.\\n2. Under **Plug settings** copy the value under **Your unique App ID**.\\n3. Configure the DevRev SDK in your app using the obtained credentials.\\n\\n##### \\n\\nThe DevRev SDK must be configured before you can use any of its features.\\n\\nThe SDK becomes ready for use once the following configuration",
"title": "Quickstart guide | 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-1978_KNOWLEDGE_NODE-38",
"text": "conversations on the portal.\\n3. Under **Styling**, upload a banner image which should be in the ratio of 6:1. You can also set light/dark mode for appearance and select your accent color.\\n4. If you want to enable customers to create tickets from the portal, under **Tabs** turn on **Enable ticket creation**. Assign default owner and part.\\n5. If you want to enable public ticket creation wherein unauthenticated users can create tickets, contact DevRev support.\\n6. Turn on the **Enable banner**",
"title": "Customer portal | Computer for Support Teams | DevRev"
},
{
"id": "ART-12447_KNOWLEDGE_NODE-7",
"text": "`AndroidManifest.xml`, as shown below:\\n\\n[code]\\n\\n 1| <application \\n ---|--- \\n 2| android:name=\".FooApplication\"> \\n 3| </application>\\n[/code] \\n \\n## Sample app\\n\\nWe provide a sample app demonstrating use cases with both XML-based UI and Jetpack Compose as part our [public repository](https://github.com/devrev/devrev-sdk-android).\\n\\nBefore running the sample app, make sure to configure it with your DevRev credentials. To do this, update the",
"title": "Quickstart guide — DevRev | Docs"
},
{
"id": "ART-12454_KNOWLEDGE_NODE-4",
"text": "provided as a part of our [public repository](https://github.com/devrev/devrev-sdk-react-native). To set up and run the sample app:\\n\\n 1. Go to the sample directory:\\n[code] 1| cd sample \\n ---|---\\n[/code] \\n \\n 2. Install dependencies:\\n[code] 1| yarn install \\n ---|---\\n[/code] \\n \\n 3. For iOS, run:\\n[code] 1| cd ios \\n ---|--- \\n 2| pod install\\n[/code] \\n \\n 4. Run the app on Android or iOS using:\\n[code] 1| npx react-native start \\n",
"title": "Quickstart guide for React Native — DevRev | Docs"
},
{
"id": "ART-12454_KNOWLEDGE_NODE-3",
"text": "[https://app.devrev.ai](https://app.devrev.ai/) and go to the **Settings** page.\\n 2. Under **PLuG settings** copy the value under **Your unique App ID**.\\n 3. After obtaining the credentials, you can configure the DevRev SDK in your app.\\n\\nThe SDK will be ready for use once you execute the following configuration method.\\n\\n[code]\\n\\n 1| DevRev.configure(appID: string) \\n ---|---\\n[/code] \\n \\n## Sample app\\n\\nA sample app with use cases for the DevRev React Native plugin has been",
"title": "Quickstart guide for React Native — DevRev | Docs"
},
{
"id": "ART-12457_KNOWLEDGE_NODE-4",
"text": "---|---\\n[/code] \\n \\n\\n## Set up the DevRev SDK\\n\\n 1. Open the DevRev web app at [https://app.devrev.ai](https://app.devrev.ai/) and go to the **Settings** page.\\n 2. Under **PLuG settings** copy the value under **Your unique App ID**.\\n 3. After obtaining the credentials, you can configure the DevRev SDK in your app.\\n\\nThe SDK will be ready for use once you execute the following configuration method.\\n\\n[code]\\n\\n 1| DevRev.configure(appID: string) \\n ---|---\\n[/code] \\n \\n##",
"title": "Quickstart guide for Expo — DevRev | Docs"
},
{
"id": "ART-15498_KNOWLEDGE_NODE-4",
"text": "following configuration method is executed.\\n\\n###### Kotlin\\n\\n###### Java\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | DevRev.configure(context: Context, appId: String) |\\n```\\n\\nEnsure that the custom application is specified in the `AndroidManifest.xml`:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | <application |\\n| 2 | android:name=\".MyApp\"> |\\n| 3 | </application> |\\n```\\n\\nUse this property to check whether the DevRev SDK has been configured:\\n\\n###### Kotlin\\n\\n###### Java\\n\\n```\\n| | |\\n| --- |",
"title": "Quickstart guide | DevRev | Docs"
},
{
"id": "ART-12449_KNOWLEDGE_NODE-14",
"text": "DevRev.createSupportConversation(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": "Features — DevRev | Docs"
},
{
"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-1463_KNOWLEDGE_NODE-7",
"text": ")\\n\\nIf a UIViewController is provided as the from parameter, the screen is presented modally.\\n\\nIf a UINavigationController is provided as the from parameter, the screen is pushed onto the navigation stack.\\n\\nFor example:\\n\\n1 DevRev. showSupport ( from : mainViewController )\\n\\nSwiftUI. :\\n\\nFor SwiftUI apps, a dedicated view is provided. Use the public view property:\\n\\n1 DevRev.supportView`\\n\\nNew conversation callback. :\\n\\nFor convenience, a callback closure is added, so the host app",
"title": "Integrate PLuG with your iOS app — DevRev | Docs"
},
{
"id": "ART-1474_KNOWLEDGE_NODE-3",
"text": "page.\\n\\nInitialization.\\n\\nAfter you\\xe2\\x80\\x99ve obtained the necessary credentials, proceed to configure the DevRev SDK within your app.\\n\\nTo configure the SDK, invoke the following method inside your Application class:\\n1 fun DevRev. configure ( 2 context: Context , 3 appID: String , 4 secret: String , 5 supportId: String 6 ) If you don\\xe2\\x80\\x99t have a custom Application class, create one as shown below:\\n1 import ai.devrev.sdk.DevRev 2 3 class FooApplication : Application () { 4 5",
"title": "Integrate PLuG with your Android app — 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-15519_KNOWLEDGE_NODE-2",
"text": "the **Settings** page.\\n2. Under **Plug settings**, copy the value under **Your unique App ID**.\\n3. After obtaining the credentials, configure the DevRev SDK in your app.\\n\\n##### \\n\\nThe DevRev SDK must be configured before you can use any of its features.\\n\\nThe SDK will be ready for use once you execute the following configuration method:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | DevRev.configure(appID, successCallback, errorCallback) |\\n```\\n\\nSample app\\n----------\\n\\nA sample app with use",
"title": "Quickstart guide | DevRev | Docs"
},
{
"id": "ART-2898_KNOWLEDGE_NODE-15",
"text": "to tailor its appearance to your application\\xe2\\x80\\x99s design.\\n\\n[code]\\n\\n 1| android:src=\"@your_drawable_here\" \\n ---|---\\n[/code] \\n \\nand\\n\\n[code]\\n\\n 1| android:backgroundTint=\"@your_background_color\" \\n ---|---\\n[/code] \\n \\nAt this stage, your app is fully configured to utilize all functionalities of the DevRev PLuG SDK. Pressing the support button directs the user to the chat interface, enabling effective interaction and support.\\n\\n## Analytics\\n\\nThe DevRev SDK",
"title": "Android integration — 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-16580_KNOWLEDGE_NODE-3",
"text": "page](https://pub.dev/packages/devrev_sdk_flutter).\\n\\nSet up the DevRev SDK\\n---------------------\\n\\n1. Open the DevRev web app at [https://app.devrev.ai](https://app.devrev.ai/) and go to the **Settings** page.\\n2. Under **Plug settings** copy the value under **Your unique App ID**.\\n3. Configure the DevRev SDK in your app using the obtained credentials.\\n\\n##### \\n\\nThe DevRev SDK must be configured before you can use any of its features.\\n\\nThe SDK becomes ready for use once the following",
"title": "Quickstart guide | DevRev | Docs"
},
{
"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-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"
}
] |
76498094-21db-4ff9-819c-7144e3c22f1a
|
sessions not loading, keeps on loading
|
[
{
"id": "ART-15506_KNOWLEDGE_NODE-27",
"text": "|\\n| 1 | // Delete the existing Plug instance if it exists |\\n| 2 | if (window.plugSDK.isPlugInitialized) { |\\n| 3 | window.plugSDK.shutdown(); |\\n| 4 | } |\\n| 5 | |\\n| 6 | // Re-initialize Plug |\\n| 7 | window.plugSDK.init({ |\\n| 8 | app_id: appId, |\\n| 9 | |\\n| 10 | // With session token |\\n| 11 | session_token: sessionToken, |\\n| 12 | |\\n| 13 | // Or without session token |\\n| 14 | identity: {}, |\\n| 15 | }); |\\n```\\n\\nIf you\\xe2\\x80\\x99re using the Plug SDK for recording user sessions,",
"title": "Identify your users with Plug | DevRev | Docs"
},
{
"id": "ART-4955_KNOWLEDGE_NODE-1",
"text": "version PLuG session recordings. This change allows us to focus on delivering a more scalable and feature-rich solution that meets the evolving needs of our users. The old session recordings feature will officially be discontinued on 21st April, 2025.\\n\\nNote: The legacy recordings will not be migrated to the new system.\\n\\nWe encourage you to explore our new analytics stack which offers significantly enhanced capabilities for all your Conversational AI and session recording needs.\\n\\nHere's",
"title": "Transitioning to the New PLuG Sessions Experience"
}
] |
53aacb77-bee9-4664-9b98-60e25f045505
|
create new ticket when user reopens existing ticket after 7 days
|
[
{
"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-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-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-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-62",
"text": "up ticket.\\n\\nThe below fields would be copied on the new follow up ticket from the archived/immutable ticket:\\n\\n* Part\\n* Channel\\n* Account\\n* Workspace\\n* Reported by\\n* Description\\n* Title\\n* Channel specific custom fields\\n* Subtype\\n\\nThe follow up trigger is added in the workflows and admins configure the changes required on new follow up ticket, for example, copying of any other fields.\\n\\nInternal Tickets\\n----------------\\n\\nInternal tickets allow your team to create and manage",
"title": "Tickets | Computer for Support Teams | DevRev"
}
] |
5cf30f9b-f68e-483c-8193-5da13a356924
|
how to see created AI agent unique ID
|
[
{
"id": "ART-4206_KNOWLEDGE_NODE-13",
"text": "2 | \"payload\": { |\\n| 3 | \"ai_agent_response\": { |\\n| 4 | \"agent\": \"don:core:dvrv-us-1:devo/xyz:ai_agent/123\", |\\n| 5 | \"agent_response\": \"message\", |\\n| 6 | \"client_metadata\": { |\\n| 7 | /* your original metadata */ |\\n| 8 | }, |\\n| 9 | \"message\": \"The agent\\'s final response message\", |\\n| 10 | \"session\": \"don:core:dvrv-us-1:devo/xyz:ai_agent_session/3810\", |\\n| 11 | \"session_object\": \"unique_conversation_identifier\" |\\n| 12 | }, |\\n| 13 | \"type\": \"ai_agent_response\" |\\n| 14 | } |\\n| 15 | }",
"title": "Agents async API | DevRev | Docs"
},
{
"id": "ART-4206_KNOWLEDGE_NODE-11",
"text": "\"session_object\": \"unique_conversation_identifier\" |\\n| 20 | }, |\\n| 21 | \"type\": \"ai_agent_response\" |\\n| 22 | } |\\n| 23 | } |\\n```\\n\\nSkill executed\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"payload\": { |\\n| 3 | \"ai_agent_response\": { |\\n| 4 | \"agent\": \"don:core:dvrv-us-1:devo/xyz:ai_agent/123\", |\\n| 5 | \"agent_response\": \"progress\", |\\n| 6 | \"client_metadata\": { /* your original metadata */ }, |\\n| 7 | \"progress\": { |\\n| 8 | \"progress_state\": \"skill_executed\", |\\n| 9 |",
"title": "Agents async API | 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"
}
] |
50fc6566-f6b8-4423-a7b0-71e4fcfdb2fe
|
SLA reporting dashboard with historical trends
|
[
{
"id": "ART-4181_KNOWLEDGE_NODE-30",
"text": "formulas or SQL queries\\n\\n![]()\\n\\nOut-of-the-box SLA reports\\n\\nGet instant visibility into critical SLA metrics, ensuring consistent tracking across your entire support team\\n\\n![]()\\n\\nOnly hits, no misses : Retro-analyze SLA compliance\\n\\nView SLA breaches, hit rate, and miss rate as they happen to stay in control of your SLA adherence\\n\\n![]()\\n\\n![]()\\n\\nNo code custom SLA analytics\\n\\nCreate tailored SLA reports in seconds - no more complex formulas or SQL",
"title": "Support like a lightning fast pit-crew"
},
{
"id": "ART-4181_KNOWLEDGE_NODE-31",
"text": "queries\\n\\n![]()\\n\\nOut-of-the-box SLA reports\\n\\nGet instant visibility into critical SLA metrics, ensuring consistent tracking across your entire support team\\n\\n![]()\\n\\nOnly hits, no misses : Retro-analyze SLA compliance\\n\\nView SLA breaches, hit rate, and miss rate as they happen to stay in control of your SLA adherence\\n\\n![]()\\n\\n![]()\\n\\nEverything you need to fulfill your service level commitments\\n\\n* Org schedules\\n* Custom SLA metrics\\n* Auto SLA assignment\\n* Default SLA",
"title": "Support like a lightning fast pit-crew"
},
{
"id": "ART-1972_KNOWLEDGE_NODE-24",
"text": "[Product demos](/docs/DevRevU/demos)\\n\\n1. [Documentation](/docs)\\n3. [Computer for Support Teams](/docs/product/support)\\n[Support analytics](/docs/product/support-analytics)\\n[Ticket-SLA Analytics](/docs/dashboards/ticket-sla-analytics)\\n\\nTicket-SLA Analytics\\n====================\\n\\n* **SLA applied Tickets**\\n\\n Number of tickets where SLA is applied.\\n* **SLA compliance rate**\\n\\n Percentage of tickets where SLA was met out of all tickets where SLA is applied.\\n* **Active tickets with",
"title": "Ticket-SLA Analytics | Support analytics | Computer for Support Teams | DevRev"
},
{
"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"
}
] |
7da19b33-802b-4d03-9c86-4aa547e4c02b
|
show Plug widget on click of a button
|
[
{
"id": "ART-1270_KNOWLEDGE_NODE-6",
"text": "screen is open, you should use either the togglewidget() method with a boolean value or the toggleSearchAgent() method, depending on which PLuG instance you are using.\\n\\n1 window. plugSDK. toggleWidget ( true ) ; 2 window. plugSDK. toggleSearchAgent ( true ) ; Take actions from events.\\n\\nThis method can be used to listen to events coming from the PLuG widget. The following are the different PAYLOAD_TYPES.\\n\\nON_PLUG_WIDGET_CLOSED The PLuG widget is closed.\\n\\nON_PLUG_WIDGET_OPENED The PLuG",
"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-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-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-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-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-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-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-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-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-2063_KNOWLEDGE_NODE-27",
"text": "release notes, news, or blogs with your customers.\\n * *Open Widget*: Upon clicking on the nudge, the Plug widget opens to prompt the user to start a conversation. This is useful for informing customers about Plug cards and suggesting support options.\\n * *None*: When the user clicks on the nudge, nothing happens and there won't be any interaction.\\n9. Define rules as described in the [Create rules](#create-rules) section.\\n\\nCreate a banner\\n---------------\\n\\n1. Click **Settings** >",
"title": "Nudges | Computer for Your Customers | DevRev"
},
{
"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-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-15490_KNOWLEDGE_NODE-5",
"text": "shared any information.\\n\\nAfter integrating the Plug widget, you can personalize and contextualize customer engagement. Learn how to [identify your customers](/sdks/web/user-identity) and update their information.\\n\\nBind a hotkey to toggle search agent\\n------------------------------------\\n\\nYou can bind the `toggleSearchAgent` method to a hotkey, such as `Cmd + K` (or `Ctrl + K` for Windows), to toggle the search agent. Here\\xe2\\x80\\x99s an example implementation:\\n\\n###### Setup\\n\\n######",
"title": "Install Plug search | DevRev | Docs"
},
{
"id": "ART-1466_KNOWLEDGE_NODE-24",
"text": "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 conversation with your team.\\n\\n1 plugSDK. toggleWidget ( true , \\' create_conversation \\' , { 2 startConversationContent : \\' Hi \\' , 3 } ) ; 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",
"title": "Methods — DevRev | Docs"
},
{
"id": "ART-15513_KNOWLEDGE_NODE-25",
"text": "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```\\n| | |\\n| --- | --- |\\n| 1 | <ai.devrev.sdk.plug.view.PlugFloatingActionButton |\\n| 2 | android:id=\"@+id/plug_fab\" |\\n| 3 | android:layout_width=\"wrap_content\" |\\n| 4 | android:layout_height=\"wrap_content\" |\\n| 5 | android:layout_margin=\"24dp\" |\\n| 6 | app:layout_constraintBottom_toBottomOf=\"parent\" |\\n| 7 | app:layout_constraintEnd_toEndOf=\"parent\" />",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-2897_KNOWLEDGE_NODE-11",
"text": "options: `light` and `dark`.\\n\\n[code]\\n\\n 1| window.plugSDK.toggleTheme(\\'light | dark\\'); \\n ---|---\\n[/code] \\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\\n## Toggle widget\\n\\nThe `toggleWidget` method allows you to control the visibility of the",
"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-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-15490_KNOWLEDGE_NODE-3",
"text": "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```\\n\\nTo toggle `searchAgent`, call the following method on any event required:\\n\\n```\\n| |\\n| --- |\\n| window.plugSDK.toggleSearchAgent(); |\\n```\\n\\nTo prefill search input from outside the window,",
"title": "Install Plug search | DevRev | Docs"
},
{
"id": "ART-15509_KNOWLEDGE_NODE-15",
"text": "prompt to start a conversation with your team.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | plugSDK.toggleWidget(true, \\'create_conversation\\', { |\\n| 2 | startConversationContent: \\'Hi\\', |\\n| 3 | }); |\\n```\\n\\nShutdown\\n--------\\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```\\n| | |\\n| --- | --- |\\n| 1 | await window.plugSDK.shutdown();",
"title": "Methods | 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-8",
"text": "selector string is used to match the element to which the widget 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",
"title": "Methods — DevRev | Docs"
},
{
"id": "ART-886_KNOWLEDGE_NODE-5",
"text": "be used to select a single page, a URL containing text, or a wildcard\\n The example rule above will only show the nudge when the exact URL is matched.\\n For wildcards, you can use the Contains operator\\n The Action can either launch a URL, launch the PLuG widget, or do nothing (e.g. notification only)\\n \\n \\n Validate preview\\n When satisfied, click on Publish\\n Enjoy your new nudge!\\n\\n\\nAnalytics\\n\\nDevRev Nudges have full tracking including impressions, clicks, and more",
"title": "Nudges | The Book of DevRev"
},
{
"id": "ART-2894_KNOWLEDGE_NODE-6",
"text": "considered an anonymous user. Anonymous users are the users that come to your site and haven\\xe2\\x80\\x99t yet logged in or shared any information.\\n\\nAfter integrating the PLuG widget, you can personalize and contextualize customer engagement. Learn how to [identify your customers](/public/sdks/web/user-identity) and update their information.\\n\\n## Bind a hotkey to toggle search agent\\n\\nYou can bind the `toggleSearchAgent` method to a hotkey, such as `Cmd + K` (or `Ctrl + K` for Windows), to",
"title": "Install PLuG search — DevRev | Docs"
},
{
"id": "ART-982_KNOWLEDGE_NODE-5",
"text": "be used to select a single page, a URL containing text, or a wildcard\\n The example rule above will only show the nudge when the exact URL is matched.\\n For wildcards, you can use the Contains operator\\n The Action can either launch a URL, launch the PLuG widget, or do nothing (e.g. notification only)\\n \\n \\n Validate preview\\n When satisfied, click on Publish\\n Enjoy your new nudge!\\n\\n\\nAnalytics\\n\\nDevRev Nudges have full tracking including impressions, clicks, and more",
"title": "DevRev Nudges - Driving Customer Engagement"
},
{
"id": "ART-2897_KNOWLEDGE_NODE-19",
"text": "10| } \\n 11| }); \\n 12| }, []);\\n[/code] \\n \\n## Toggle search agent\\n\\nThe `toggleSearchAgent` method allows you to control the visibility of the search agent.\\n\\nIf no input is provided, the method toggles the search bar: opening it if it\\xe2\\x80\\x99s closed, and closing it if it\\xe2\\x80\\x99s open.\\n\\n[code]\\n\\n 1| window.plugSDK.toggleSearchAgent(true); \\n ---|---\\n[/code] \\n \\n## Check Search Agent status\\n\\nUse `isSearchAgentOpen` to determine whether the search",
"title": "Methods — DevRev | Docs"
},
{
"id": "ART-15509_KNOWLEDGE_NODE-18",
"text": "window.plugSDK.initSearchAgent(); |\\n| 10 | } |\\n| 11 | }); |\\n| 12 | }, []); |\\n```\\n\\nToggle search agent\\n-------------------\\n\\nThe `toggleSearchAgent` method allows you to control the visibility of the search agent.\\n\\nIf no input is provided, the method toggles the search bar: opening it if it\\xe2\\x80\\x99s closed, and closing it if it\\xe2\\x80\\x99s open.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | window.plugSDK.toggleSearchAgent(true); |\\n```\\n\\nCheck Search Agent",
"title": "Methods | DevRev | Docs"
},
{
"id": "ART-2063_KNOWLEDGE_NODE-29",
"text": "following types of action are supported:\\n * *Redirect to URL*: You can provide a URL that your customers are redirected to when clicking on a nudge. It's helpful for sharing release notes, news, or blogs with your customers.\\n * *Open Widget*: Upon clicking on the nudge, the Plug widget opens to prompt the user to start a conversation. This is useful for informing customers about Plug cards and suggesting support options.\\n * *None*: When the user clicks on the nudge, nothing happens and",
"title": "Nudges | Computer for Your Customers | DevRev"
}
] |
0279472a-af63-484e-9e28-f77644e3e538
|
AI based CSAT for all tickets setup
|
[
{
"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-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-1961_KNOWLEDGE_NODE-32",
"text": "part.\\n\\n**Sentiment evaluator**\\n\\nThe sentiment evaluator takes the ID of a ticket and assesses the customer's sentiment based on their comments. Sentiment values can be *Delighted*, *Happy*, *Frustrated*, *Neutral*, *Unhappy*, or *Unknown*. It also provides justification for the sentiment values. These values are only generated if there is a customer conversation on the ticket. For example, you can listen to a ticket update event, evaluate the sentiment, and send a comment to the",
"title": "Workflows | Computer by DevRev | DevRev"
},
{
"id": "ART-6176_KNOWLEDGE_NODE-26",
"text": "agents can monitor sentiment changes in real time and respond proactively to customer needs.\\n\\nInstallation\\n------------\\n\\n1. Install the [Real-time sentiment evaluator snap-in](/marketplace/realtime-sentiment-evaluator) from the DevRev marketplace.\\n2. Select the workspace to install the snap-in, and click **Install**.\\n\\n![]()\\n\\nConfiguration\\n-------------\\n\\n1. Post installing the snap-in, choose the number of recent customer messages to evaluate for generating the customer",
"title": "Real-time sentiment evaluator | Automate | Snap-ins | DevRev"
}
] |
1a0a3ce7-4f83-461a-b75e-e5679669b508
|
new hires trouble using slack
|
[
{
"id": "ART-2035_KNOWLEDGE_NODE-61",
"text": "them.\\n* As of the latest update, in case of unavailability of email, the snap-in creates new DevRev contact and attaches Slack user id for future reference. For legacy users, run the /AddSlackUserId command in DevRev on the Contacts to manually add their Slack user ID.\\n\\n[PreviousExotel](/docs/integrations/exotel)[NextWhatsApp](/docs/integrations/whatsapp)\\n\\n#### On this page\\n\\n* [Installation](#installation)\\n* [List of available commands](#list-of-available-commands)\\n* [Create DevRev",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-1005_KNOWLEDGE_NODE-3",
"text": "\\n Mail \\xe2\\x86\\x92 Gsuite\\n Messaging \\xe2\\x86\\x92 Slack\\n Conferencing \\xe2\\x86\\x92 Zoom/Gsuite\\n \\n \\n Hosting\\n \\n Website \\xe2\\x86\\x92 Vercel\\n DNS/Domains \\xe2\\x86\\x92 GoDaddy (pre me) then Route 53\\n \\n \\n\\n\\nThe following figure shows a high-level overview of these systems and some flows between them:\\n\\n\\n\\nWhen configuring this 3+ years ago, we set it up so that everything flows from BambooHR to Okta to all other systems. This means BambooHR is",
"title": "Choosing the Right Systems For Your Startup"
}
] |
884edd7b-75a0-417d-a002-cffb420d9ae9
|
agent timeout fetching large artifact content from ticket log file
|
[
{
"id": "ART-16594_KNOWLEDGE_NODE-0",
"text": "b'If an attachment is larger than 250 MB, it exceeds the maximum artifact size supported by DevRev and will not be uploaded. The current limit is defined as MAX_DEVREV_ARTIFACT_SIZE = 262144000 (250 MB). When using the default attachment processors in Airdrop SDK, such oversized attachments are automatically skipped, and the extraction process continues with the remaining attachments. This means you don\\xe2\\x80\\x99t need to implement custom filtering at the data extraction layer to handle them.",
"title": "What happens when trying to stream too big attachment in ADaaS SDK"
},
{
"id": "ART-17221_KNOWLEDGE_NODE-23",
"text": "blocked and can stall the sync process. To prevent this, the AirSync SDK implements a two-tier timeout mechanism.\\n\\n* The **soft timeout**, default of 10 minutes and configurable, sends an exit message to the worker thread, allowing it to gracefully shut down via the `onTimeout` function. How to configure this is shown in the example below.\\n* If the worker does not respond within the **hard timeout**, default of 13 minutes, it is forcefully terminated.\\n\\nThis mechanism ensures that the",
"title": "Data extraction | DevRev | Docs"
},
{
"id": "ART-17220_KNOWLEDGE_NODE-3",
"text": "time)EXTRACTION\\\\_ATTACHMENTS\\\\_CONTINUEEXTRACTION\\\\_ATTACHMENTS\\\\_ERROR\\n\\n### Event types\\n\\n| Event | Direction | Description |\\n| --- | --- | --- |\\n| `EXTRACTION_ATTACHMENTS_START` | AirSync \\xe2\\x86\\x92 Snap-in | Initiates the attachments extraction |\\n| `EXTRACTION_ATTACHMENTS_PROGRESS` | Snap-in \\xe2\\x86\\x92 AirSync | Indicates process is ongoing but runtime limit (13 minutes) reached |\\n| `EXTRACTION_ATTACHMENTS_DELAY` | Snap-in \\xe2\\x86\\x92 AirSync | Requests a delay due to rate",
"title": "Attachments extraction | DevRev | Docs"
},
{
"id": "ART-4206_KNOWLEDGE_NODE-2",
"text": "async API\\n================\\n\\nCopy page\\n\\nThis cookbook provides a step-by-step guide to use the asynchronous API for DevRev agents. It assumes you\\xe2\\x80\\x99ve already created an agent using the DevRev agent builder platform.\\n\\nThe DevRev async API enables you to execute agents without any execution timeout concerns. The execution occurs as an asynchronous workflow that sends events to you via webhooks. This approach ensures:\\n\\n* Agent complexity does not bring timeout concerns with",
"title": "Agents async API | DevRev | Docs"
},
{
"id": "ART-17221_KNOWLEDGE_NODE-25",
"text": "loop.\\n* Use `async/await` for I/O operations such as API calls or file reads.\\n* Add periodic async breaks in tight loops using `Promise.resolve()`, `setTimeout()`, or `setImmediate()`.\\n\\nYou can find examples of correct timeout-safe code in the [timeout-handling test suite](https://github.com/devrev/adaas-sdk/tree/main/src/tests/timeout-handling).\\n\\nTo test how your snap-in responds to timeouts, you can configure a shorter timeout using the `spawn` function:\\n\\n```\\n| | |\\n| --- | ---",
"title": "Data extraction | DevRev | Docs"
},
{
"id": "ART-1304_KNOWLEDGE_NODE-54",
"text": "datetime Optional\\nThe expiration timestamp of the URL.\\nAPI Reference artifacts Locate Post.\\n\\nPOST https:// api.devrev.ai / 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",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1566_KNOWLEDGE_NODE-49",
"text": "Locate.\\n\\nGET https://api.devrev.ai / artifacts.locate\\n\\nGets the download URL for the artifact.\\n\\nQuery parameters.\\n\\nid string Required\\n\\nThe ID of the artifact to get the URL for.\\n\\nversion string Optional\\n\\nThe version of the artifact that needs to be fetched.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nurl string\\n\\nThe artifact\\xe2\\x80\\x99s download URL.\\n\\nexpires_at datetime Optional\\n\\nThe expiration timestamp of the URL.\\n\\nAPI Reference artifacts Locate Post.\\n\\nPOST",
"title": "Transition (Beta) — DevRev | Docs"
},
{
"id": "ART-1780_KNOWLEDGE_NODE-49",
"text": "Locate.\\n\\nGET https:// api.devrev.ai / artifacts.locate\\nGets the download URL for the artifact.\\nQuery parameters.\\n\\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 Locate Post.\\n\\nPOST https:// api.devrev.ai /",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1558_KNOWLEDGE_NODE-49",
"text": "Locate.\\n\\nGET https://api.devrev.ai / artifacts.locate\\n\\nGets the download URL for the artifact.\\n\\nQuery parameters.\\n\\nid string Required\\n\\nThe ID of the artifact to get the URL for.\\n\\nversion string Optional\\n\\nThe version of the artifact that needs to be fetched.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nurl string\\n\\nThe artifact\\xe2\\x80\\x99s download URL.\\n\\nexpires_at datetime Optional\\n\\nThe expiration timestamp of the URL.\\n\\nAPI Reference artifacts Locate Post.\\n\\nPOST",
"title": "Metric Definitions List (Beta) — DevRev | Docs"
}
] |
5e84c4be-172b-48f5-8d9d-8237948cb00d
|
How to close sprint in DevRev
|
[
{
"id": "ART-1994_KNOWLEDGE_NODE-32",
"text": "there are no sprint boards for the part, click **New sprint board** and specify the name, duration of sprints, and the start date. The start time allows you to select the date and time when the sprint begins. The sprint will conclude at the same time after the specified number of days, including weekends.\\n\\n ![]()\\n2. Go to the new sprint board and click **Backlog**. Any issues assigned to the part but not to a sprint are listed here.\\n If there are no issues shown, you can go to the",
"title": "Sprint mode | Computer for Builders | DevRev"
}
] |
4d454b97-973f-48d9-85ab-b3e67aff041d
|
case notification when a ticket is created, assigned, and notification with support response
|
[
{
"id": "ART-1953_KNOWLEDGE_NODE-29",
"text": "[support@yourdomain.com](mailto:support@yourdomain.com)\\n* **Subject**: \"You are missing messages from <Org Name>\"\\n\\nReply to the customer on a ticket\\n---------------------------------\\n\\n* **Trigger**: When a reply is made to a customer on a ticket.\\n* **Action**: The system sends out a notification to the customer with the reply message.\\n* **Sender**: {Company\\\\_Name} [support@yourdomain.com](mailto:support@yourdomain.com)\\n* **Subject**: \"[{Company\\\\_Name}] Update on TKT-XXX\"\\n\\nTicket",
"title": "Customer email notifications | Computer by DevRev | DevRev"
},
{
"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-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-1976_KNOWLEDGE_NODE-29",
"text": "section.\\n\\nNotification behavior\\n---------------------\\n\\n* Group-only routing triggers notifications for all group members.\\n* Direct user assignment triggers notifications only for the assigned user.\\n* Combined group and user routing triggers notifications only for the assigned user.\\n* If a user is assigned as the owner after notifications have been sent to the group members, those notifications are removed for all members and retained only for the assigned owner.\\n* When a new owner is",
"title": "Routing | Computer for Support Teams | 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-1954_KNOWLEDGE_NODE-33",
"text": "notifications for new assignments.\\n * Group Mentions: Enable notifications for mentions involving your affiliated groups.\\n * Mentions: Enable alerts when you're mentioned.\\n * Comments: Enable updates for comments on your subscribed records.\\n * Attribute Updates: Enable notifications for attribute updates in records to which you subscribe.\\n3. Select the priority level (*Important*, *Others*, *Muted*) for each notification type. This determines the destination tab on the **Updates**",
"title": "Updates | Computer by DevRev | DevRev"
},
{
"id": "ART-16583_KNOWLEDGE_NODE-1",
"text": "whenever a DevRev customer experience engineer responds.\\n\\nConfiguration\\n-------------\\n\\n##### \\n\\n**Prerequisites**\\n\\n* Apple Developer Program access for iOS apps.\\n* Google Developer Account and Firebase project access for iOS apps.\\n* Admin access to DevRev Plug settings.\\n* Access to Bundle ID, Team ID, and APNs/FCM keys.\\n* Mobile SDK integration with your Android or iOS app.\\n\\n1. Go to **Settings** > **Support** > **Plug settings** > **Mobile push notifications**.\\n2. Click **+",
"title": "Push notifications for mobile | DevRev | Docs"
},
{
"id": "ART-12390_KNOWLEDGE_NODE-44",
"text": "(Optional) Users for private visibility | Output ports created dynamically based on button clicks |\\n| SendNotification | Sends a notification to specified users or groups. | * receivers: Users or groups who will receive the notification * body: The body of the notification * title: The title of the notification * linked\\\\_object: (Optional) The object which will open on clicking the notification | Empty response on success",
"title": "Workflow action library | Workflows | Computer by DevRev | DevRev"
}
] |
ffd4fe33-8c8d-4e54-a00a-986c543e6bb7
|
feature to show when another teammate is viewing the ticket
|
[
{
"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"
}
] |
48e3ad00-de35-429d-ba19-2f54d766c22e
|
add item to timeline using snap-in trigger email to CC user on ticket
|
[
{
"id": "ART-1485_KNOWLEDGE_NODE-10",
"text": "invoke the snap-in, two distinct triggers are implemented:\\n\\n 1. **Creation of work item** : This trigger is activated when new objects of type **Issue** or **Ticket** are created in DevRev.\\n\\n 2. **Text command** : This manual trigger is achieved by utilizing a slash command in the **Discussions** tab of the objects that support this feature.\\n\\n#### Action\\n\\nTo implement the desired action of adding a comment to the object timeline, it is essential to identify the appropriate [API] for",
"title": "Snap-in triggered by a DevRev event — DevRev | Docs"
},
{
"id": "ART-1485_KNOWLEDGE_NODE-8",
"text": "comment to the object timeline.\\n\\nTo learn more, refer to the [Using a snap-in to perform a DevRev action](/public/snapin-development/tutorials/timer-ticket-creator) tutorial.\\n\\n[1](/public/snapin-development/tutorials/triggered-event#installation-guide)\\n\\n### Installation guide\\n\\n * Install [DevRev CLI](/public/snapin-development/references/cli-install)\\n * Install [jq](https://stedolan.github.io/jq)\\n * Install [DevRev",
"title": "Snap-in triggered by a DevRev event — DevRev | Docs"
},
{
"id": "ART-1485_KNOWLEDGE_NODE-11",
"text": "this task. In this scenario, the `/timeline-entries.create` API is the designated choice for executing the action of adding a text comment from the snap-in. To accomplish this task, the DevRev SDK is employed.\\n\\n[2](/public/snapin-development/tutorials/triggered-event#creating-the-snap-in)\\n\\n### Creating the snap-in\\n\\n#### Updating the manifest\\n\\nThe next step involves updating the manifest to define key attributes of the snap-in. This includes deciding on the name and providing a",
"title": "Snap-in triggered by a DevRev event — DevRev | Docs"
},
{
"id": "ART-1277_KNOWLEDGE_NODE-28",
"text": "Sending the request to create the timeline entry comment |\\n| 26 | const response = await devrevSDK.timelineEntriesCreate(body as any); |\\n| 27 | |\\n| 28 | // Returning the response from the DevRev SDK |\\n| 29 | return response; |\\n| 30 | } |\\n```\\n\\n[12](/snapin-development/tutorials/triggered-event#deploying-the-snap-in-to-your-organization)\\n\\n### Deploying the snap-in to your organization\\n\\nUpon completing and validating the code changes, the next crucial step is\\ndeploying the snap-in to",
"title": "Snap-in triggered by a DevRev event | DevRev | Docs"
},
{
"id": "ART-1277_KNOWLEDGE_NODE-6",
"text": "objects of type\\n **Issue** or **Ticket** are created in DevRev.\\n2. **Text command**: This manual trigger is achieved by utilizing a slash\\n command in the **Discussions** tab of the objects that support this feature.\\n\\n#### Action\\n\\nTo implement the desired action of adding a comment to the object timeline, it\\nis essential to identify the appropriate [API]\\nfor this task. In this scenario, the `/timeline-entries.create` API is the\\ndesignated choice for executing the action of adding a",
"title": "Snap-in triggered by a DevRev event | DevRev | Docs"
},
{
"id": "ART-1278_KNOWLEDGE_NODE-22",
"text": "\"timeline_comment\", |\\n| 28 | }; |\\n| 29 | |\\n| 30 | // Create a timeline comment using the DevRev SDK |\\n| 31 | const response = await devrevSDK.timelineEntriesCreate(body as any); |\\n| 32 | |\\n| 33 | // Return the response from the DevRev API |\\n| 34 | return response; |\\n| 35 | } |\\n```\\n\\n[7](/snapin-development/tutorials/triggered-external-source#deploying-the-snap-in-to-your-organization)\\n\\n### Deploying the snap-in to your organization\\n\\nUpon completion and validation of the code",
"title": "Snap-in triggered by an external source | DevRev | Docs"
},
{
"id": "ART-1485_KNOWLEDGE_NODE-19",
"text": "comment on a DevRev work item created. \\n 5| - name: function_2 \\n 6| description: \\n 7| Function to create a timeline entry comment on a DevRev work item on which \\n 8| comment is added.\\n[/code] \\n \\n[6](/public/snapin-development/tutorials/triggered-event#automations)\\n\\n### Automations\\n\\nWith the building blocks in place, the final piece of the puzzle involves defining automations. These automations encapsulate a trigger and a corresponding function that",
"title": "Snap-in triggered by a DevRev event — DevRev | Docs"
},
{
"id": "ART-1265_KNOWLEDGE_NODE-9",
"text": "timeline of an issue/ticket using the `timeline-entries.create` API with different visibilities. You can now use this to create comments on timeline using automation or manually based on your use case.\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/guides/webhooks)[#### Object customization\\n\\nNext](/guides/object-customization)[Built with](https://buildwithfern.com/?utm_campaign=buildWith&utm_medium=docs&utm_source=developer.devrev.ai)\\n\\n![]()'",
"title": "Restricted messages on a timeline | DevRev | Docs"
},
{
"id": "ART-1277_KNOWLEDGE_NODE-14",
"text": "name: function_1 |\\n| 3 | description: |\\n| 4 | Function to create a timeline entry comment on a DevRev work item created. |\\n| 5 | - name: function_2 |\\n| 6 | description: |\\n| 7 | Function to create a timeline entry comment on a DevRev work item on which |\\n| 8 | comment is added. |\\n```\\n\\n[6](/snapin-development/tutorials/triggered-event#automations)\\n\\n### Automations\\n\\nWith the building blocks in place, the final piece of the puzzle involves\\ndefining automations. These automations",
"title": "Snap-in triggered by a DevRev event | DevRev | Docs"
},
{
"id": "ART-1473_KNOWLEDGE_NODE-26",
"text": "SDK \\n 31| const response = await devrevSDK.timelineEntriesCreate(body as any); \\n 32| \\n 33| // Return the response from the DevRev API \\n 34| return response; \\n 35| }\\n[/code] \\n \\n[7](/public/snapin-development/tutorials/triggered-external-source#deploying-the-snap-in-to-your-organization)\\n\\n### Deploying the snap-in to your organization\\n\\nUpon completion and validation of the code changes, the subsequent crucial step involves deploying the snap-in to your",
"title": "Snap-in triggered by an external source — DevRev | Docs"
},
{
"id": "ART-1485_KNOWLEDGE_NODE-6",
"text": "[command](/public/snapin-development/references/commands) within DevRev.\\n\\nThe focus 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\\n## Background context\\n\\n 1. **Webhook event handling** : Understand",
"title": "Snap-in triggered by a DevRev event — DevRev | Docs"
},
{
"id": "ART-1277_KNOWLEDGE_NODE-3",
"text": "specifically focused on work creation.\\n2. **Command-based activation**: Explore how the snap-in can be triggered by a\\n dedicated command within the DevRev environment.\\n3. **Payload exploration**: Delve into the payload structure, gaining insights\\n into how to efficiently extract essential fields from within the functions.\\n4. **Action execution**: Become proficient in executing a specified action - adding\\n a customizable comment to the object timeline.\\n\\nTo learn more, refer to the",
"title": "Snap-in triggered by a DevRev event | DevRev | Docs"
},
{
"id": "ART-1265_KNOWLEDGE_NODE-1",
"text": "page\\n\\nIntroduction\\n------------\\n\\nIn this tutorial, you\\xe2\\x80\\x99ll learn how to send restricted visibility messages on the 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](/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.\\nYou can use",
"title": "Restricted messages on a timeline | 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-1277_KNOWLEDGE_NODE-25",
"text": "requirements.\\n\\n[11](/snapin-development/tutorials/triggered-event#handling-command-event)\\n\\n### Handling command event\\n\\nFor scenarios where a command event is triggered, a dedicated function,\\n`handleCommandEvent`, can be implemented to handle the event appropriately. The\\nprovided TypeScript snippet outlines the structure of this function,\\ndemonstrating how to extract relevant information from the event payload and\\nutilize the DevRev SDK to create a timeline entry comment.\\n\\n```\\n| |",
"title": "Snap-in triggered by a DevRev event | DevRev | Docs"
},
{
"id": "ART-1265_KNOWLEDGE_NODE-6",
"text": "\"Content-Type: application/json\" -d |\\n| > | \\'{ |\\n| > | \"object\": \"don:core:<partition>:devo/<dev-org-id>:<object-type>/<object-id>\", |\\n| > | \"body\": \"message\", |\\n| > | \"visibility\": \"private\", |\\n| > | \"type\": \"timeline_comment\" |\\n| > | }\\' |\\n| > | \\'https://api.devrev.ai/timeline-entries.create\\' \\\\ |\\n| > | --header \\'Authorization: Bearer <PAT>\\' |\\n```\\n\\nYou receive the following `json` response.\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"timeline_entry\": { |\\n| 3 | \"type\":",
"title": "Restricted messages on a timeline | DevRev | Docs"
}
] |
8154c859-b4c6-4a5d-a189-70fe432fca42
|
service account in user types
|
[
{
"id": "ART-1362_KNOWLEDGE_NODE-2",
"text": "session token; it does not reference any dev user or customer. At the time of the token generation, the corresponding dev user can define the expiration time of the token. The lifetime of an AAT is usually in days. The subject of the AAT is set to the DON of the application, which is service account (for example, `don:identity:dvrv-us-1:devo/0:svcacc/gG88A`).\\n\\n * **System User Token (SUT)** : Uniquely identifies a system user belonging to a dev org. A SUT is obtained by a dev user with the",
"title": "Authentication — DevRev | Docs"
},
{
"id": "ART-1170_KNOWLEDGE_NODE-2",
"text": "be used to obtain a session token; it does not reference any dev user or customer. At the time of the token generation, the corresponding dev user can define the expiration time of the token. The lifetime of an AAT is usually in days. The subject of the AAT is set to the DON of the application, which is service account (for example, `don:identity:dvrv-us-1:devo/0:svcacc/gG88A`).\\n* **System User Token (SUT)**: Uniquely identifies a system user belonging to a dev org. A SUT is obtained by a dev",
"title": "Authentication | DevRev | Docs"
},
{
"id": "ART-1484_KNOWLEDGE_NODE-209",
"text": "choose multiple users from a list. Works with [Input layout](/public/snapin-development/references/snapkit#input-layout) and [Actions](/public/snapin-development/references/snapkit#actions) blocks.\\n\\n_Properties_\\n\\n * `user_types` (optional): The types of users that are allowed to be selected. Defaults to `[\"rev_user\", \"dev_user\"]`. Possible values: `\"rev_user\"`, `\"dev_user\"`, `\"sys_user\"`.\\n * `initial_rev_users_selected_options` (optional): The initially selected customers, a list of",
"title": "Snapkit — DevRev | Docs"
},
{
"id": "ART-17231_KNOWLEDGE_NODE-91",
"text": "Owner of the group |\\n| `type` | enum | | Type of the group |\\n\\n#### Enum values\\n\\n**member\\\\_type**\\n\\n| Value | Name | Description |\\n| --- | --- | --- |\\n| `dev_user` | dev\\\\_user | - |\\n| `rev_user` | rev\\\\_user | - |\\n| `svc_acc` | svc\\\\_acc | - |\\n\\n**type**\\n\\n| Value | Name | Description |\\n| --- | --- | --- |\\n| `dynamic` | dynamic | - |\\n| `static` | static | - |\\n\\n[\\xe2\\x96\\xb2 top](/airsync/supported-object-types#summary)\\n\\nincident\\n--------\\n\\n**Resource Type:**",
"title": "Supported DevRev object types | DevRev | Docs"
},
{
"id": "ART-1170_KNOWLEDGE_NODE-3",
"text": "user with the right level of privileges for a given system user. The SUT is issued for the DON of the corresponding system user. At the time of the token generation, the corresponding dev user can define the expiration time of the token. The lifetime of a SUT is usually in days. The subject of the SUT is set to the DON of the corresponding system user (for example, `don:identity:dvrv-us-1:devo/0:sysu/1`).\\n* **Session Token**: Obtained by an application to access DevRev APIs on behalf of a",
"title": "Authentication | DevRev | Docs"
}
] |
ecc1a43a-9090-4818-9dc9-dad5ee598651
|
create custom field in accounts
|
[
{
"id": "ART-1957_KNOWLEDGE_NODE-27",
"text": "[Issues](./issues#attributes)\\n* [Tickets](./tickets#attributes)\\n* [Opportunity](./grow#opportunity-attributes)\\n* [Account](./grow#account-attributes)\\n* [Contact](./grow#contact-attributes)\\n* [Parts](./parts#attributes)\\n\\n![]()\\n\\nAdding custom fields can be done by workspace admins only. Members of your organization can only view the custom fields and subtypes.\\n\\nTo get started with object customization, go to [**Settings** > **Object",
"title": "Object customization | Computer by DevRev | DevRev"
},
{
"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-1545_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": "Create (Beta) — DevRev | Docs"
},
{
"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-1957_KNOWLEDGE_NODE-28",
"text": "customization**](https://app.devrev.ai/devrev/settings/object-customization).\\nHere you can view all the existing objects and their subtypes. You can also check the objects that are no longer in use by going to **Show deprecated objects**.\\n\\nAdd a new field to an object or a subtype\\n-----------------------------------------\\n\\n1. Select the object or subtype you want to add to the custom field.\\n2. Clicking the **+ New field** button takes you to the edit mode where you can fill in the",
"title": "Object customization | Computer by DevRev | DevRev"
},
{
"id": "ART-15502_KNOWLEDGE_NODE-17",
"text": "\"don:core:dvrv-us-1:devo/demo:custom_object/campaign/1\" |\\n| > | }\\' |\\n```\\n\\nExtended use cases\\n------------------\\n\\n### Reference custom objects in other objects\\n\\nLet\\xe2\\x80\\x99s say you want to reference all the campaigns that have been run for a customer\\nworkspace. You can do so by adding a field of type \\xe2\\x80\\x9cid\\xe2\\x80\\x9d and \\xe2\\x80\\x9cid\\\\_type: custom\\\\_object.campaign\\xe2\\x80\\x9d\\nin the account tenant schema.\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl --location",
"title": "Custom objects | DevRev | Docs"
},
{
"id": "ART-15502_KNOWLEDGE_NODE-18",
"text": "\\'https://api.devrev.ai/schemas.custom.set\\' \\\\ |\\n| > | --header \\'Content-Type: application/json\\' \\\\ |\\n| > | --header \\'Accept: application/json\\' \\\\ |\\n| > | --header \\'Authorization: Bearer <TOKEN>\\' \\\\ |\\n| > | --data \\'{ |\\n| > | \"type\": \"tenant_fragment\", |\\n| > | \"description\": \"Tenant attributes for Account\", |\\n| > | \"leaf_type\": \"account\", |\\n| > | \"fields\": [ |\\n| > | { |\\n| > | \"name\": \"campaigns\", |\\n| > | \"field_type\": \"array\", |\\n| > | \"base_type\": \"id\", |\\n| > | \"id_type\": [",
"title": "Custom objects | DevRev | Docs"
},
{
"id": "ART-1306_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-2683_KNOWLEDGE_NODE-19",
"text": "objects in other objects\\n\\nLet\\xe2\\x80\\x99s say you want to reference all the campaigns that have been run for a customer workspace. You can do so by adding a field of type \\xe2\\x80\\x9cid\\xe2\\x80\\x9d and \\xe2\\x80\\x9cid_type: custom_object.campaign\\xe2\\x80\\x9d in the account tenant schema.\\n\\n[code]\\n\\n $| curl --location \\'https://api.devrev.ai/schemas.custom.set\\' \\\\ \\n ---|--- \\n >| --header \\'Content-Type: application/json\\' \\\\ \\n >| --header \\'Accept: application/json\\' \\\\",
"title": "Custom objects (Beta) — DevRev | Docs"
},
{
"id": "ART-1789_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-1828_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-1787_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-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-15507_KNOWLEDGE_NODE-17",
"text": "Additional information about the account |\\n\\n##### \\n\\nThe custom fields properties defined as part of the user, organization and account traits, must be configured in the DevRev web app **before** they can be used. See [Object customization](https://devrev.ai/docs/product/object-customization) for more information.\\n\\n##### User traits\\n\\nThe `UserTraits` class contains detailed information about the user:\\n\\n##### \\n\\nAll properties in `UserTraits` are optional.\\n\\n| Property | Type |",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-2895_KNOWLEDGE_NODE-7",
"text": "\\n >| \"devrev.ai\" \\n >| ], \\n >| \"custom_fields\": { \\n >| \"tnt__<field2_name>\": \"value x\" \\n >| } \\n >| } \\n >| } \\n >| }\\'\\n[/code] \\n \\n#####\\n\\nEnsure that you follow the specified format when providing your phone number.\\n\\n## Pass custom attributes\\n\\nTo create custom attributes, see [Object customization](https://developer.devrev.ai/beta/guides/object-customization).\\n\\nYou can",
"title": "Identify your users with PLuG — DevRev | Docs"
},
{
"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-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-1959_KNOWLEDGE_NODE-35",
"text": "issues\\n```\\n```\\n\\nLearn more about creating and managing custom fields in the [Object customization guide](https://developer.devrev.ai/beta/guides/object-customization).\\n\\n### Search over custom objects\\n\\nCustom fields use the standard field search syntax and support all field types including text, numeric, boolean, date, and array fields. You should add the leaf\\\\_type filter while searching over custom objects.\\n\\nSearch for book custom objects related to AI agents:\\n\\n```\\n```\\n1",
"title": "Search | Computer by DevRev | DevRev"
}
] |
36495a53-525c-449b-b1c5-42f12b98935b
|
ticket stopped syncing with Slack
|
[
{
"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-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-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-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-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-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-2045_KNOWLEDGE_NODE-58",
"text": "synced items is not propagated. This includes works (issues or tickets), accounts, users, links, and other types. When an item is deleted (either in DevRev or at the source) and that item exists at the other end, it will not be deleted but no further updates to it will be made.\\n\\n### References\\n\\n* In-text references (such as @mentions) will not be remapped.\\n\\n### Schema changes\\n\\n* If a new type is added to the external source after the initial sync, it will not be automatically picked up",
"title": "AirSync | 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-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"
}
] |
79c89e77-542c-4719-9b9c-d5650e91c9c9
|
Call recording and transcript are being processed playback never loads
|
[
{
"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-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"
}
] |
b7e98d27-d10d-4fbe-83fd-b3ec2062dcf7
|
sync account to salesforce value not updated but opportunity sync works
|
[
{
"id": "ART-2047_KNOWLEDGE_NODE-31",
"text": "prompted to manually map certain fields if needed. You can track the migration and perform any required mapping under **Settings** > **Integrations** > **AirSyncs**.\\n\\nThe duration of the import depends on the size of the Salesforce account and the data being imported. It can take seconds for an account with only a few dozen cases to a few hours for an account with tens of thousands of cases with many attachments. DevRev honors the Salesforce API rate limits and back-off and resumes",
"title": "Salesforce AirSync | AirSync | Snap-ins | DevRev"
},
{
"id": "ART-2911_KNOWLEDGE_NODE-27",
"text": "![]()\\n\\n Providing incorrect information in the configuration may lead to the merging of incorrect accounts, an irreversible action. The primary account continues syncing after the merge, while the secondary account no longer syncs with the external source. Field updates to the secondary account are ignored. When accounts are merged, the values of single-value stock fields from the secondary account, as well as any **common** custom field values of the secondary account, are lost.\\n3. Click",
"title": "Account deduplication | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2045_KNOWLEDGE_NODE-58",
"text": "synced items is not propagated. This includes works (issues or tickets), accounts, users, links, and other types. When an item is deleted (either in DevRev or at the source) and that item exists at the other end, it will not be deleted but no further updates to it will be made.\\n\\n### References\\n\\n* In-text references (such as @mentions) will not be remapped.\\n\\n### Schema changes\\n\\n* If a new type is added to the external source after the initial sync, it will not be automatically picked up",
"title": "AirSync | Snap-ins | DevRev"
},
{
"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-2047_KNOWLEDGE_NODE-44",
"text": "limitations](/docs/import).\\n\\n### Comments\\n\\n* Threaded case comments are not synced back to Salesforce.\\n\\n### Updates\\n\\n* Updates to Picklist\\\\_MultiSelect fields from DevRev are not loaded/synced back to Salesforce.\\n\\n### Knowledge articles\\n\\n* Only published articles in the master language are imported from Salesforce to DevRev.\\n* If the article has multiple rich text content fields, the article will be split into multiple DevRev articles, one for each rich text content",
"title": "Salesforce AirSync | AirSync | Snap-ins | DevRev"
},
{
"id": "ART-2047_KNOWLEDGE_NODE-27",
"text": "\\xe2\\x9c\\x85 | \\xe2\\x9c\\x85 |\\n| Comment on Case/Task/Problem/Incident | Comment on Ticket | \\xe2\\x9c\\x85 | \\xe2\\x9c\\x85 |\\n| Attachment on Case/Task/Problem/Incident | Attachment on Ticket | \\xe2\\x9c\\x85 | \\xe2\\x9d\\x8c |\\n| Product | Product | \\xe2\\x9c\\x85 | \\xe2\\x9d\\x8c |\\n| Account | Account | \\xe2\\x9c\\x85 | \\xe2\\x9d\\x8c |\\n| Contact | Contact | \\xe2\\x9c\\x85 | \\xe2\\x9d\\x8c |\\n| Opportunity | Opportunity | \\xe2\\x9c\\x85 | \\xe2\\x9c\\x85 |\\n| Lead | Contact | \\xe2\\x9d\\x8c | \\xe2\\x9d\\x8c |\\n|",
"title": "Salesforce AirSync | AirSync | Snap-ins | DevRev"
}
] |
e318f31d-049c-4067-8ae3-a7f3f4862b5c
|
record a video of exactly what needs to be done
|
[
{
"id": "ART-899_KNOWLEDGE_NODE-1",
"text": "DevRev PLuG Session Replay we provide the ability to record a users session and automatically attach it to a conversation when its started. This allows those providing support to the customer to see exactly what the customer was doing, and any potential errors, before they contacted support.\\n\\nThis allows them to have context, empathy, any ideally provide much better support without needing to ask the traditional boring questions of \\xe2\\x80\\x9cwhat were you doing when this",
"title": "Nudges | The Book of DevRev"
},
{
"id": "ART-1001_KNOWLEDGE_NODE-1",
"text": "DevRev PLuG Session Replay we provide the ability to record a users session and automatically attach it to a conversation when its started. This allows those providing support to the customer to see exactly what the customer was doing, and any potential errors, before they contacted support.\\n\\nThis allows them to have context, empathy, any ideally provide much better support without needing to ask the traditional boring questions of \\xe2\\x80\\x9cwhat were you doing when this",
"title": "DevRev PLuG Session Replay"
},
{
"id": "ART-12460_KNOWLEDGE_NODE-16",
"text": "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(successCallback, errorCallback)`| Starts the session recording. \\n`DevRev.stopRecording(successCallback, errorCallback)`| Ends the session recording and uploads it to the portal. \\n`DevRev.pauseRecording(successCallback, errorCallback)`| Pauses the ongoing session recording.",
"title": "Features — DevRev | Docs"
},
{
"id": "ART-4256_KNOWLEDGE_NODE-15",
"text": "is enabled by default.\\n\\nThe session recording feature includes the following methods to control the recording:\\n\\nMethod| Action \\n---|--- \\n`DevRev.startRecording()`| Start the session recording. \\n`DevRev.stopRecording()`| Stop the session recording and upload it to the portal. \\n`DevRev.pauseRecording()`| Pause the ongoing session recording. \\n`DevRev.resumeRecording()`| Resume a paused session recording. \\n`DevRev.processAllOnDemandSessions()`| Stop the ongoing session recording and",
"title": "DevRev SDK for React Native — DevRev | Docs"
},
{
"id": "ART-12456_KNOWLEDGE_NODE-16",
"text": "Action \\n---|--- \\n`DevRev.startRecording()`| Starts the session recording. \\n`DevRev.stopRecording()`| Stops the session recording and uploads it to the portal. \\n`DevRev.pauseRecording()`| Pauses the ongoing session recording. \\n`DevRev.resumeRecording()`| Resumes a paused session recording. \\n`DevRev.processAllOnDemandSessions()`| Stops the ongoing session recording and uploads all offline sessions on demand, including the current one. \\n \\n### Session properties\\n\\nYou can add",
"title": "Features — DevRev | Docs"
},
{
"id": "ART-2664_KNOWLEDGE_NODE-27",
"text": "your\\n [website](https://developer.devrev.ai/sdks/web/installation) or\\n [mobile app](https://developer.devrev.ai/sdks/mobile).\\n2. For web applications, configure\\n [user identification](https://developer.devrev.ai/sdks/web/user-identity).\\n3. Enable session recording for your users, go to **Settings** > **PluG and Portal** >\\n **Session Replays** and enable recording for your desired platform.\\n\\n **Note**: Alternatively, you can enable session recording during Plug SDK\\n",
"title": "Session analytics | Computer for Your Customers | DevRev"
},
{
"id": "ART-4255_KNOWLEDGE_NODE-19",
"text": "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.| pauseRecording()| pauseRecording(DevRev.INSTANCE); \\nResumes a paused session recording.| resumeRecording()| resumeRecording(DevRev.INSTANCE); \\n \\n### Session properties\\n\\nYou can add custom properties to the session recording to help you understand the context of the",
"title": "DevRev SDK for Android — DevRev | Docs"
},
{
"id": "ART-15507_KNOWLEDGE_NODE-27",
"text": "|\\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 recording. |\\n| `DevRev.stopRecording()` | Stops the session recording and uploads it to the portal. |\\n|",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-4257_KNOWLEDGE_NODE-20",
"text": "Action \\n---|--- \\n`DevRev.startRecording()`| Starts the session recording. \\n`DevRev.stopRecording()`| Ends the session recording and uploads it to the portal. \\n`DevRev.pauseRecording()`| Pauses the ongoing session recording. \\n`DevRev.resumeRecording()`| Resumes a paused session recording. \\n \\n### Session properties\\n\\nYou can add custom properties to the session recording to help you understand the context of the session. The properties are defined as a dictionary of string",
"title": "DevRev SDK for iOS — DevRev | Docs"
},
{
"id": "ART-16579_KNOWLEDGE_NODE-29",
"text": "recording. |\\n| `DevRev.stopRecording()` | Ends the session recording and uploads it to the portal. |\\n| `DevRev.pauseRecording()` | Pauses the ongoing session recording. |\\n| `DevRev.resumeRecording()` | Resumes a paused session recording. |\\n| `DevRev.processAllOnDemandSessions()` | Stops the ongoing session recording and uploads all offline sessions on demand, including the current one. |\\n\\n### Session properties\\n\\nYou can add custom properties to the session recording to help you",
"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-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-15513_KNOWLEDGE_NODE-33",
"text": "`DevRev.startRecording()` | Starts the session recording. |\\n| `DevRev.stopRecording()` | Ends the session recording and uploads it to the portal. |\\n| `DevRev.pauseRecording()` | Pauses the ongoing session recording. |\\n| `DevRev.resumeRecording()` | Resumes a paused session recording. |\\n| `DevRev.processAllOnDemandSessions()` | Stops the ongoing user recording and sends all on-demand sessions along with the current recording. |\\n\\nUsing this property returns the status of the session",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-12453_KNOWLEDGE_NODE-21",
"text": "is opt-in 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. \\n`DevRev.stopRecording()`| Ends the session recording and uploads it to the portal. \\n`DevRev.pauseRecording()`| Pauses the ongoing session recording. \\n`DevRev.resumeRecording()`| Resumes a paused session recording. \\n \\n### Session properties\\n\\nYou can add custom properties",
"title": "Features — DevRev | Docs"
},
{
"id": "ART-1001_KNOWLEDGE_NODE-2",
"text": "happened?\\xe2\\x80\\x9d\\n\\nSee it in action\\n\\n\\n \\n\\n\\nAt-a-glance\\n\\nThe PLuG Session Replay feature provides the ability to:\\n\\n\\n Natively record user sessions anywhere where PLuG is installed\\n Automatically attaches session recordings to conversation upon creation\\n Provides full privacy and data masking\\n Replay user sessions, view events and errors\\n\\n\\nHow it works\\n\\nThis feature can be leveraged anywhere where the PLuG widget is installed. Meaning, if you deploy the DevRev PLuG",
"title": "DevRev PLuG Session Replay"
},
{
"id": "ART-15510_KNOWLEDGE_NODE-14",
"text": "--- | --- |\\n| 1 | DevRev.resumeAllMonitoring(successCallback, errorCallback) |\\n```\\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\\n| Method | Action |\\n| --- | --- |\\n| `DevRev.startRecording(successCallback, errorCallback)` | Starts the session recording. |\\n|",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-2664_KNOWLEDGE_NODE-28",
"text": "initialization by setting the enable\\\\_session\\\\_recording option to true.\\n However, this method does not allow you to manage session recordings through\\n the settings page.\\n4. View Session recordings and analytics by going to **Explore** and searching for\\n [Session replays](/docs/plug/observability).\\n\\nFor detailed instructions on session recording options, refer to\\n[Session recording options and data masking](/docs/plug/session-recording).\\n\\nTrack events\\n------------\\n\\nFor",
"title": "Session analytics | Computer for Your Customers | DevRev"
},
{
"id": "ART-15515_KNOWLEDGE_NODE-32",
"text": "DevRev.resumeAllMonitoring() |\\n```\\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\\n| Method | Action |\\n| --- | --- |\\n| `DevRev.startRecording()` | Starts the session recording. |\\n| `DevRev.stopRecording()` | Ends the session recording and uploads it to the portal.",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-2901_KNOWLEDGE_NODE-20",
"text": "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-in 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. \\n`DevRev.stopRecording()`| Ends the session recording and uploads it to the",
"title": "iOS integration — DevRev | Docs"
},
{
"id": "ART-899_KNOWLEDGE_NODE-2",
"text": "happened?\\xe2\\x80\\x9d\\n\\nAt-a-glance\\n\\nThe PLuG Session Replay feature provides the ability to:\\n\\n\\n Natively record user sessions anywhere where PLuG is installed\\n Automatically attaches session recordings to conversation upon creation\\n Provides full privacy and data masking\\n Replay user sessions, view events and errors\\n\\n\\nHow it works\\n\\nThis feature can be leveraged anywhere where the PLuG widget is installed. Meaning, if you deploy the DevRev PLuG widget on your website for chat",
"title": "Nudges | The Book of DevRev"
},
{
"id": "ART-899_KNOWLEDGE_NODE-3",
"text": "support, you have the ability to natively record user sessions.\\n\\nFor example, we have the PLuG widget deployed on this site, our marketing site and others. Through the nature of this widget being on our sites, we can take advantage of this feature and track user sessions when new conversations are started.\\n\\n\\n\\nSee it in action'",
"title": "Nudges | The Book of DevRev"
},
{
"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-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-1001_KNOWLEDGE_NODE-3",
"text": "widget on your website for chat support, you have the ability to natively record user sessions.\\n\\nFor example, we have the PLuG widget deployed on this site, our marketing site and others. Through the nature of this widget being on our sites, we can take advantage of this feature and track user sessions when new conversations are started.\\n\\n\\n'",
"title": "DevRev PLuG Session Replay"
},
{
"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-4186_KNOWLEDGE_NODE-26",
"text": "then tracks and captures all screens, events, API service calls, exceptions (such as crashes and ANRs), errors, and gestures (including scrolls, taps, and rage taps).\\n\\nSession Replays\\n---------------\\n\\n![]()\\n\\nYou can search for **Session Replays** in **Explore** page where you can see the sessions for your Web app and sessions for Android and iOS on mobile.\\n\\n* View sessions by platform and time.\\n* Apply simple filters such as **Platform**, **Session duration**, **Date range**, etc.\\n*",
"title": "Computer for User Insights | Session analytics | Computer for Your Customers | DevRev"
},
{
"id": "ART-15509_KNOWLEDGE_NODE-5",
"text": "(True or False) |\\n| `session_recording_key` | Identifies your session recording account and is required to enable the SDK session recording features. | String |\\n| `enable_session_recording` | Instructs the widget to determine whether to start the session recording. | Boolean (True or False) |\\n| `session_token` | Identifies the user interacting with your app. | String |\\n| `primary_text_color` | The color of the launcher, button text for new tickets and conversations, conversation user text,",
"title": "Methods | DevRev | Docs"
}
] |
baa132fa-8833-4e19-befb-3f11f259b5ad
|
unable to open a ticket error
|
[
{
"id": "ART-1955_KNOWLEDGE_NODE-28",
"text": "tickets.\\n\\n Privileges: ticket object ['CREATE']\\n* *Customer Ticket Field Access:* Contains the field access on tickets\\n\\n Privileges: ticket object None\\n* *Self RevOrg Viewer:* Contains privileges on revOrgs for revUsers to view there workspace.\\n\\n Privileges: revo object ['READ']\\n* *Self RevOrg RevUsers Viewer:* Contains privileges on revUsers for revUsers to view there workspace revUsers.\\n\\n Privileges: revu object ['READ']\\n* *Self RevUsers Viewer:* Contains privileges on",
"title": "Default privileges by group | Roles | Computer by DevRev | DevRev"
},
{
"id": "ART-1978_KNOWLEDGE_NODE-38",
"text": "conversations on the portal.\\n3. Under **Styling**, upload a banner image which should be in the ratio of 6:1. You can also set light/dark mode for appearance and select your accent color.\\n4. If you want to enable customers to create tickets from the portal, under **Tabs** turn on **Enable ticket creation**. Assign default owner and part.\\n5. If you want to enable public ticket creation wherein unauthenticated users can create tickets, contact DevRev support.\\n6. Turn on the **Enable banner**",
"title": "Customer portal | Computer for Support Teams | DevRev"
},
{
"id": "ART-4255_KNOWLEDGE_NODE-33",
"text": "\\n**Solution** : Confirm that user identification is performed before using the `showSupport()` function or XML button.\\n\\n * **Issue** : Incorrect operation due to `App ID` and `secret` misconfiguration. \\n**Solution** : Ensure correct functionality by double-checking that both `App ID` and `secret` values are accurately configured in your application or sample app.\\n\\nWas this page helpful?YesNo\\n\\n[DevRev SDK for iOSUp Next](/public/sdks/ios)\\n\\n[Built",
"title": "DevRev SDK for Android — DevRev | Docs"
},
{
"id": "ART-1955_KNOWLEDGE_NODE-89",
"text": "object ['READ', 'UPDATE']\\n* *Ticket Creator:* Contains create privileges on tickets.\\n\\n Privileges: ticket object ['CREATE']\\n* *RevUser ticket Admin:* Contains privileges on user tickets admins.\\n\\n Privileges: ticket object ['READ', 'UPDATE']\\n* *RevUser conversation Admin:* Contains privileges on conversation admins.\\n\\n Privileges: conversation object ['READ', 'UPDATE']\\n\\n\\xe2\\x80\\x9cDev Users\\xe2\\x80\\x9d group\\n-----------------\\n\\nGroup for all dev users.\\n\\n**Privileges:**\\n\\n*",
"title": "Default privileges by group | Roles | Computer by DevRev | DevRev"
},
{
"id": "ART-1483_KNOWLEDGE_NODE-4",
"text": "changes to the snap-in:\\n\\n 1. Update the trigger condition to run every 10 minutes instead of work creation.\\n 2. Create a ticket whenever the snap-in is triggered.\\n\\nEnsure that you have at least one [part](https://docs.devrev.ai/product/parts#product-or-service) in your organization since every ticket must be linked to a part and have an owner.\\n\\nSince a DevRev ticket is created whenever the function is triggered, DevRev APIs need to be called that allow this functionality. Although one",
"title": "Using a snap-in to perform a DevRev action — 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"
}
] |
9c5bfe74-bb58-45dd-ad43-a526246cc97f
|
configure support email to create tickets automatically
|
[
{
"id": "ART-3207_KNOWLEDGE_NODE-39",
"text": "here are treated as new support tickets.\\n* **Conversations**: These addresses trigger conversations (not tickets).\\n\\n> Example: Use sales@yourcompany.com for general inquiries and help@yourcompany.com for support.\\n\\n### Step 4: Set the Default Part and Owner\\n\\n* Select the **default part** of your product for categorizing tickets.\\n* Assign a **default owner** (for example, a support lead or queue manager) for incoming tickets.\\n\\n### Step 5: Personalization settings\\n\\n| Setting |",
"title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-3207_KNOWLEDGE_NODE-38",
"text": "Step 2: Define the Primary Use Case\\n\\nChoose how DevRev should interpret emails sent to the primary address:\\n\\n* Choose between generating a **Ticket or a Conversation** from the incoming email.\\n\\nToggle on **Set email as the default channel for tickets** to ensure that:\\n\\n* Customer chat replies are sent via email as well as to the original source of the channel.\\n\\n### Step 3: Add Additional Support Emails\\n\\nYou can add more addresses to handle support requests.\\n\\n* **Tickets**: Emails",
"title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2027_KNOWLEDGE_NODE-26",
"text": "configuration instructions, refer to [Email snap-in configuration](/docs/integrations/email-config).\\n\\nFor more information, refer to the [Email snap-in](/marketplace/email-with-tickets) on the DevRev marketplace.\\n\\nConversation and ticket creation for emails\\n-------------------------------------------\\n\\nWhen an email is received, DevRev checks if the sender is linked to your workspace and creates a conversation or ticket. If a sender is not recognized, DevRev creates a new user profile to",
"title": "Email | Integrate | Snap-ins | 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"
},
{
"id": "ART-3207_KNOWLEDGE_NODE-37",
"text": "href=\"mailto:support@devrev.ai\">support@devrev.ai</a>\\n\\n\\n\\n18 </td>\\n\\n\\n\\n19 </tr>\\n\\n\\n\\n20 </table>\\n```\\n\\nShow more\\n```\\n\\n**Result**:\\n\\n![]()\\n\\n### Next steps for configuration of the snap-in\\n\\n### Step 1: Add a Primary Email Address\\n\\n* Format: Name <email@domain.com> \\xe2\\x80\\x94 this is what appears in the customer\\xe2\\x80\\x99s inbox.\\n* Example: Maple Support <support@maplesoftware.net>\\n\\nThis email address becomes the primary channel for incoming support mail.\\n\\n###",
"title": "Email snap-in configuration | Email | Integrate | Snap-ins | 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\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_@hooks.devrev.ai.\\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-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-3207_KNOWLEDGE_NODE-45",
"text": "snap-in. These only appear once the email snap-in is successfully installed and verified.\\n\\nSet-up the provided forwarding address to the account you want to forward from. For example support@example.com.\\n\\nIn the DevRev app, under the **Instructions** tab you can see a forwarding email address displayed as v\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_@hooks.devrev.ai. This is the address where you can forward your support emails.\\n\\nGoogle Workspace/Groups\\n\\n1. If you are using Google Groups, add your",
"title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-3207_KNOWLEDGE_NODE-46",
"text": "support address as a member of the Google Group.\\n\\n You must be a part of the group and have permission to send emails to the Google Group.\\n2. Go to the settings of your support Gmail account.\\n3. Navigate to **Forwarding and POP/IMAP** and add the forwarding email address v\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_@hooks.devrev.ai. Click **Next**.\\n4. Click **Proceed** when you are redirected to a new webpage. You are asked for a confirmation code sent to this forwarding address.\\n5. If the",
"title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-3207_KNOWLEDGE_NODE-49",
"text": "select **Forward all emails sent to this mailbox**, enter the forwarding address v\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_@hooks.devrev.ai, and choose whether you want to keep a copy of forwarded emails. If you don\\'t see this option, make sure a license is assigned to the user account. Select **Save changes**.\\n\\nOnce added, an invitation is sent to the hooks address. The invitation appears as a conversation in your inbox in the DevRev app. However, note that the conversation comment might not be",
"title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-15716_KNOWLEDGE_NODE-3",
"text": "SMTP/IMAP). You\\xe2\\x80\\x99ll need admin access to complete the setup.\\n\\n[Email integration setup instructions](https://devrev.ai/docs/integrations/email)\\n\\n6. Syncing Cases Between DevRev and Salesforce\\n\\nYes, you can sync cases (tickets) from DevRev to Salesforce using the Salesforce integration. Mapping and sync options are available during setup.\\n\\n[Syncing cases with Salesforce](https://devrev.ai/docs/integrations/salesforce#sync-cases)\\n\\n7. Supported Airdrop Sources\\n\\nDevRev Airdrop",
"title": "Support queries related playbook"
},
{
"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 `v1.abc.xyz@hooks.devrev.ai`, you should set up email forwarding from `test@company.com` to `v1.abc.xyz@hooks.devrev.ai`.\\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"
}
] |
7237eb0f-026f-48f9-af24-7b62b7fadad2
|
visualize created date by month in report
|
[
{
"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"
}
] |
fe760a93-ee85-4917-ad74-84e416d1deaf
|
workflow trigger for new issue created and control to send slack message to assigned channel
|
[
{
"id": "ART-2035_KNOWLEDGE_NODE-51",
"text": "Slack.\\n\\nFor example:\\n\\n* /devrev view TKT-#\\n* /devrev view ISS-#\\n\\nThese commands open the specific object mentioned in the command.\\n\\nCreating custom workflows\\n-------------------------\\n\\nThe users can configure their own workflows around Slack using DevRev's workflow engine.\\n\\n| Workflow Action | Description | Inputs | Outputs |\\n| --- | --- | --- | --- |\\n| Send message on Slack | - Use this workflow node to send a message to any Slack channel as long as the DevRev app has access to",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"id": "ART-2035_KNOWLEDGE_NODE-52",
"text": "the channel. - Private channels are supported only if the DevRev app is a member of the channel. | - Slack connection - Slack channel id - Text message to send - Objects to mention with message - If any object is added here, a summary card of that object is sent with the message. | Slack message ID |\\n| Create new Slack channel | Use this workflow node to create a new Slack channel. | - Slack connection - Channel name Make sure this is unique. It is recommended to create this name",
"title": "Slack | Integrate | Snap-ins | DevRev"
},
{
"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-1478_KNOWLEDGE_NODE-18",
"text": "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 ==",
"title": "Event sources — DevRev | Docs"
},
{
"id": "ART-1490_KNOWLEDGE_NODE-58",
"text": "\\n 4| \\n 5| - name: post_message \\n 6| description: Function containing logic to post a message on newly created work.\\n[/code] \\n \\nFor functions, you also need to provide the actual JS/TS code behind this function. Refer to the README in the provided template.\\n\\n## Automations\\n\\nAutomation refers to linking events from the event sources to your functions.\\n\\nAutomations are defined as:\\n\\n[code]\\n\\n 1| automations: \\n ---|--- \\n 2| - name: <The name of the",
"title": "Snap-in manifest — DevRev | Docs"
},
{
"id": "ART-1277_KNOWLEDGE_NODE-6",
"text": "objects of type\\n **Issue** or **Ticket** are created in DevRev.\\n2. **Text command**: This manual trigger is achieved by utilizing a slash\\n command in the **Discussions** tab of the objects that support this feature.\\n\\n#### Action\\n\\nTo implement the desired action of adding a comment to the object timeline, it\\nis essential to identify the appropriate [API]\\nfor this task. In this scenario, the `/timeline-entries.create` API is the\\ndesignated choice for executing the action of adding a",
"title": "Snap-in triggered by a DevRev event | DevRev | Docs"
}
] |
0eada41c-1373-4cc9-a0be-878879432bbe
|
Email Service Snap-in setup email forwarding verification email not appearing as ticket
|
[
{
"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\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_@hooks.devrev.ai.\\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-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-1284_KNOWLEDGE_NODE-41",
"text": "forwarding address is `v1.abc.xyz@hooks.devrev.ai`, you should set up email\\nforwarding from `test@company.com` to `v1.abc.xyz@hooks.devrev.ai`.\\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-3207_KNOWLEDGE_NODE-49",
"text": "select **Forward all emails sent to this mailbox**, enter the forwarding address v\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_\\\\_@hooks.devrev.ai, and choose whether you want to keep a copy of forwarded emails. If you don\\'t see this option, make sure a license is assigned to the user account. Select **Save changes**.\\n\\nOnce added, an invitation is sent to the hooks address. The invitation appears as a conversation in your inbox in the DevRev app. However, note that the conversation comment might not be",
"title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev"
},
{
"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 `v1.abc.xyz@hooks.devrev.ai`, you should set up email forwarding from `test@company.com` to `v1.abc.xyz@hooks.devrev.ai`.\\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"
},
{
"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-1478_KNOWLEDGE_NODE-45",
"text": "sample of the YAML is shown below:\\n\\n[code]\\n\\n - name: email-event-source \\n --- \\n description: Event source which emits an event when an email is received. \\n display_name: Email events listener \\n type: email-forward \\n config: \\n allowlist: \\n - \"test@company.com\" \\n - \"mycompanydomain\"\\n[/code] \\n \\nThe event type of the events emitted by this event source is `email.receive`.\\n\\nWhen a snap-in using such an",
"title": "Event sources — DevRev | Docs"
},
{
"id": "ART-2027_KNOWLEDGE_NODE-28",
"text": "email address that messages to it create either a conversation or a ticket, but not both simultaneously. Whether to create a conversation or a ticket depends on the nature of the emails received at a specific email address.\\n\\nRead more about [conversations](../product/conversation) and [tickets](../product/tickets) to decide which is more suitable for your use case.\\n\\nWhen needed, you can link a conversation to a ticket. This is particularly useful if you decide to use conversations for all",
"title": "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-3207_KNOWLEDGE_NODE-51",
"text": "an invitation is sent to the hooks address. The invitation appears as a conversation in your inbox in the DevRev app. However, note that the conversation comment might not be rendered correctly as HTML, making the invite button inaccessible directly. To accept the invitation, you\\'ll need to download the email.eml attachment and open it in your preferred mail client. From there, you can click **Accept invite**.\\n\\nZoho Mail\\n\\nTo enable forwarding, add the",
"title": "Email snap-in configuration | Email | Integrate | Snap-ins | DevRev"
}
] |
f8aebea1-e017-4ae2-8a6d-eb82cf62ef4b
|
create a dashboard from scratch
|
[
{
"id": "ART-15687_KNOWLEDGE_NODE-32",
"text": "widget ID(s) of the widgets you created.\\n + Assign a user-friendly \"reference ID\" (alias) to each linked widget.\\n* **Define the layout**:\\n The layout section is crucial for defining the placement of widgets on the dashboard canvas.\\n For each widget, you can define:\\n\\n + Height and Width: The size of the widget.\\n + X and Y Coordinates: The position of the widget on the canvas.\\n* **Create tabs (Optional)**:\\n You can split widgets across different tabs within the dashboard for better",
"title": "Dashboards | Computer by DevRev | DevRev"
},
{
"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-15687_KNOWLEDGE_NODE-31",
"text": "dashboards\\n-------------------\\n\\nDashboards organize and display multiple widgets.\\n\\n* **Access the dashboard builder**:\\n Similar to the widget builder, access the dashboard builder by modifying your DevRev workspace URL. For example, your\\\\_workspace\\\\_slug/dashboard-preview.\\n The builder provides a boilerplate code.\\n\\n ![]()\\n* **Link widgets to the dashboard**:\\n\\n + Scroll to the section that defines the widgets to be linked.\\n + Remove any existing widget IDs and paste the",
"title": "Dashboards | Computer by DevRev | DevRev"
},
{
"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"
},
{
"id": "ART-15687_KNOWLEDGE_NODE-27",
"text": "Section)**:\\n In the \"oasis\" or \"dataset\" section, define the tables used in your queries and the name of the resulting dataset.\\n Provide a user-friendly description for the widget tooltip.\\n* **Define dimensions**:\\n Dimensions are fields you want to expose for filtering records or using in visualizations.\\n For each dimension, define:\\n\\n + **Field type**: The data type of the field.\\n + **UI hints**: Whether it\\'s visible, hidden, or filterable.\\n + **Display name**: How the field",
"title": "Dashboards | Computer by DevRev | DevRev"
}
] |
663e3798-21c4-4e85-9526-a9456bf0dbc2
|
remove ticket fields from creation page
|
[
{
"id": "ART-1957_KNOWLEDGE_NODE-34",
"text": "on the field.\\n * **Description**: Add some information about why you added this field. This is only visible to you.\\n3. Click **Save to draft**. These fields can be reviewed and then published by clicking **Publish changes**.\\n4. Review the changes and click **Publish changes** once you are ready.\\n5. Refresh the page to see the changes in published mode. You can\\'t make changes in this mode.\\n\\nTo edit or delete a custom field, click the **\\xe2\\x8b\\xae** icon next to the field. You\\'ll see",
"title": "Object customization | Computer by DevRev | DevRev"
},
{
"id": "ART-1622_KNOWLEDGE_NODE-8",
"text": "\"is_groupable\": true, \\n 49| \"is_hidden\": true, \\n 50| \"is_required\": true, \\n 51| \"placeholder\": \"foo\", \\n 52| \"tooltip\": \"foo\", \\n 53| \"view_name\": \"foo\" \\n 54| } \\n 55| ] \\n 56| } \\n 57| ], \\n 58| \"create_view\": { \\n 59| \"is_hidden\": true \\n 60| }, \\n 61|",
"title": "Get Schemas Aggregated (POST) (Beta) — DevRev | Docs"
},
{
"id": "ART-15487_KNOWLEDGE_NODE-25",
"text": "\"field_type\": \"rich_text\", |\\n| > | \"ui\": { |\\n| > | \"display_name\": \"RCA\", |\\n| > | } |\\n| > | }, |\\n| > | { |\\n| > | \"name\": \"customer_impact\", |\\n| > | \"field_type\": \"bool\", |\\n| > | \"is_filterable\": true, |\\n| > | \"ui\": { |\\n| > | \"display_name\": \"Customer Impact\", |\\n| > | } |\\n| > | } |\\n| > | ], |\\n| > | \"deleted_fields\": [ \"regression\" ] |\\n| > | }\\' |\\n```\\n\\nNote that:\\n\\n* The API payload reflects the entire state of the new fragment version.\\n* The `deleted_fields` array specifies",
"title": "Object customization | DevRev | Docs"
},
{
"id": "ART-1628_KNOWLEDGE_NODE-4",
"text": "\"display_name\": \"foo\", \\n 27| \"is_groupable\": true, \\n 28| \"is_hidden\": true, \\n 29| \"is_required\": true, \\n 30| \"placeholder\": \"foo\", \\n 31| \"tooltip\": \"foo\", \\n 32| \"view_name\": \"foo\" \\n 33| } \\n 34| ] \\n 35| } \\n 36| ], \\n 37| \"create_view\": { \\n 38| \"is_hidden\":",
"title": "Get Schemas Stock (Beta) — DevRev | Docs"
},
{
"id": "ART-1829_KNOWLEDGE_NODE-424",
"text": "string \" , 100 \" filter_view \" : { 101 \" is_hidden \" : true 102 } , 103 \" group_name \" : \" string \" , 104 \" is_active_in_detail_view \" : true , 105 \" is_bulk_action_enabled \" : true , 106 \" is_groupable \" : true , 107 \" is_hidden \" : true , 108 \" is_hidden_during_create \" : true , 109 \" is_read_only \" : true , 110 \" is_required \" : true , 111 \" is_shown_in_summary \" : true , 112 \" is_sortable \" : true , 113 \" list_view \" : { 114 \" is_hidden \" : true 115 } , 116 \" placeholder \" : \" string \" ,",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1830_KNOWLEDGE_NODE-435",
"text": "93 \" create_view \" : { 94 \" is_hidden \" : true 95 } , 96 \" detail_view \" : { 97 \" is_hidden \" : true 98 } , 99 \" display_name \" : \" string \" , 100 \" filter_view \" : { 101 \" is_hidden \" : true 102 } , 103 \" group_name \" : \" string \" , 104 \" is_active_in_detail_view \" : true , 105 \" is_bulk_action_enabled \" : true , 106 \" is_groupable \" : true , 107 \" is_hidden \" : true , 108 \" is_hidden_during_create \" : true , 109 \" is_read_only \" : true , 110 \" is_required \" : true , 111 \" is_shown_in_summary",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1645_KNOWLEDGE_NODE-28",
"text": "{ \\n >| \"name\": \"customer_impact\", \\n >| \"field_type\": \"bool\", \\n >| \"is_filterable\": true, \\n >| \"ui\": { \\n >| \"display_name\": \"Customer Impact\", \\n >| } \\n >| } \\n >| ], \\n >| \"deleted_fields\": [ \"regression\" ] \\n >| }\\'\\n[/code] \\n \\nNote that:\\n\\n * The API payload reflects the entire state of the new fragment version.\\n * The `deleted_fields` array",
"title": "Object customization (Beta) — DevRev | Docs"
},
{
"id": "ART-1626_KNOWLEDGE_NODE-10",
"text": "\"is_required\": true, \\n 62| \"mfz\": {}, \\n 63| \"name\": \"foo\", \\n 64| \"oasis\": {}, \\n 65| \"origin\": \"foo\", \\n 66| \"ui\": { \\n 67| \"client_overrides\": [ \\n 68| {} \\n 69| ], \\n 70| \"create_view\": { \\n 71| \"is_hidden\": true \\n 72| }, \\n 73| \"detail_view\": { \\n 74| \"is_hidden\": true \\n 75|",
"title": "List Schemas Custom (POST) (Beta) — DevRev | Docs"
},
{
"id": "ART-1832_KNOWLEDGE_NODE-434",
"text": "string \" , 92 \" ui \" : { 93 \" create_view \" : { 94 \" is_hidden \" : true 95 } , 96 \" detail_view \" : { 97 \" is_hidden \" : true 98 } , 99 \" display_name \" : \" string \" , 100 \" filter_view \" : { 101 \" is_hidden \" : true 102 } , 103 \" group_name \" : \" string \" , 104 \" is_active_in_detail_view \" : true , 105 \" is_bulk_action_enabled \" : true , 106 \" is_groupable \" : true , 107 \" is_hidden \" : true , 108 \" is_hidden_during_create \" : true , 109 \" is_read_only \" : true , 110 \" is_required \" : true ,",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1633_KNOWLEDGE_NODE-426",
"text": "89 \" string \" : {} 90 } , 91 \" origin \" : \" string \" , 92 \" ui \" : { 93 \" create_view \" : { 94 \" is_hidden \" : true 95 } , 96 \" detail_view \" : { 97 \" is_hidden \" : true 98 } , 99 \" display_name \" : \" string \" , 100 \" filter_view \" : { 101 \" is_hidden \" : true 102 } , 103 \" group_name \" : \" string \" , 104 \" is_active_in_detail_view \" : true , 105 \" is_bulk_action_enabled \" : true , 106 \" is_groupable \" : true , 107 \" is_hidden \" : true , 108 \" is_hidden_during_create \" : true , 109 \"",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1831_KNOWLEDGE_NODE-436",
"text": "\" , 100 \" filter_view \" : { 101 \" is_hidden \" : true 102 } , 103 \" group_name \" : \" string \" , 104 \" is_active_in_detail_view \" : true , 105 \" is_bulk_action_enabled \" : true , 106 \" is_groupable \" : true , 107 \" is_hidden \" : true , 108 \" is_hidden_during_create \" : true , 109 \" is_read_only \" : true , 110 \" is_required \" : true , 111 \" is_shown_in_summary \" : true , 112 \" is_sortable \" : true , 113 \" list_view \" : { 114 \" is_hidden \" : true 115 } , 116 \" placeholder \" : \" string \" , 117 \"",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1612_KNOWLEDGE_NODE-7",
"text": "\"create_view\": { \\n 31| \"is_hidden\": true \\n 32| }, \\n 33| \"detail_view\": { \\n 34| \"is_hidden\": true \\n 35| }, \\n 36| \"display_name\": \"foo\", \\n 37| \"filter_view\": { \\n 38| \"is_hidden\": true \\n 39| }, \\n 40| \"group_name\": \"foo\", \\n 41| \"is_active_in_detail_view\": true, \\n 42|",
"title": "List Schemas Stock (POST) (Beta) — DevRev | Docs"
},
{
"id": "ART-1829_KNOWLEDGE_NODE-435",
"text": "\" is_hidden \" : true 98 } , 99 \" display_name \" : \" string \" , 100 \" filter_view \" : { 101 \" is_hidden \" : true 102 } , 103 \" group_name \" : \" string \" , 104 \" is_active_in_detail_view \" : true , 105 \" is_bulk_action_enabled \" : true , 106 \" is_groupable \" : true , 107 \" is_hidden \" : true , 108 \" is_hidden_during_create \" : true , 109 \" is_read_only \" : true , 110 \" is_required \" : true , 111 \" is_shown_in_summary \" : true , 112 \" is_sortable \" : true , 113 \" list_view \" : { 114 \" is_hidden \"",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1831_KNOWLEDGE_NODE-426",
"text": "\" is_hidden \" : true 98 } , 99 \" display_name \" : \" string \" , 100 \" filter_view \" : { 101 \" is_hidden \" : true 102 } , 103 \" group_name \" : \" string \" , 104 \" is_active_in_detail_view \" : true , 105 \" is_bulk_action_enabled \" : true , 106 \" is_groupable \" : true , 107 \" is_hidden \" : true , 108 \" is_hidden_during_create \" : true , 109 \" is_read_only \" : true , 110 \" is_required \" : true , 111 \" is_shown_in_summary \" : true , 112 \" is_sortable \" : true , 113 \" list_view \" : { 114 \" is_hidden \"",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1827_KNOWLEDGE_NODE-426",
"text": "\" : true 95 } , 96 \" detail_view \" : { 97 \" is_hidden \" : true 98 } , 99 \" display_name \" : \" string \" , 100 \" filter_view \" : { 101 \" is_hidden \" : true 102 } , 103 \" group_name \" : \" string \" , 104 \" is_active_in_detail_view \" : true , 105 \" is_bulk_action_enabled \" : true , 106 \" is_groupable \" : true , 107 \" is_hidden \" : true , 108 \" is_hidden_during_create \" : true , 109 \" is_read_only \" : true , 110 \" is_required \" : true , 111 \" is_shown_in_summary \" : true , 112 \" is_sortable \" : true",
"title": "Update — DevRev | Docs"
}
] |
ebc7a938-42b8-42c9-b335-cc3e9bc24cb7
|
create user for bot integration and get API token
|
[
{
"id": "ART-1384_KNOWLEDGE_NODE-0",
"text": "b'[](/public/api-reference/auth-tokens/create)\\n\\nPublic\\n\\n[API Reference](/public/api-reference/getting-started)[Auth Tokens](/public/api-reference/auth-tokens/create)\\n\\n# Create Auth Token\\n\\nPOST\\n\\nhttps://api.devrev.ai/auth-tokens.create\\n\\nTry it\\n\\nCreates a JWT corresponding to the requested token type for the authenticated user.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\nact_asstringOptional`format: \"id\"`\\n\\nThe unique ID of the Dev user or the service account to",
"title": "Create Auth Token — DevRev | Docs"
},
{
"id": "ART-15513_KNOWLEDGE_NODE-13",
"text": "for a session token:\\n\\n##### \\n\\nMake sure that you 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| >",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-1194_KNOWLEDGE_NODE-0",
"text": "b'Create Auth Token | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[auth-tokens](/api-reference/auth-tokens/security-tokens)\\n\\nCreate Auth Token\\n=================\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/auth-tokens.create\\n\\nPOST\\n\\n/auth-tokens.create\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/auth-tokens.create \\\\ |\\n| > | -H \"Authorization: Bearer",
"title": "Create Auth Token | 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-15515_KNOWLEDGE_NODE-10",
"text": "and go to the **Settings** page.\\n2. Open the **Plug Tokens** page.\\n3. Under the **Application access tokens** panel, click **New token** and copy the token that\\xe2\\x80\\x99s displayed.\\n\\n##### \\n\\nEnsure that you copy the generated application access token, as you cannot view it again.\\n\\n#### Exchange your AAT for a session token\\n\\nTo proceed with identifying the user, you need to exchange your AAT for a session token. This step helps you identify a user of your own system within the",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-15443_KNOWLEDGE_NODE-0",
"text": "b'Create Rev User | 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-users](/api-reference/rev-users/create)\\n\\nCreate Rev User\\n===============\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/rev-users.create\\n\\nPOST\\n\\n/rev-users.create\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/rev-users.create \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -H",
"title": "Create Rev User | DevRev | Docs"
},
{
"id": "ART-15507_KNOWLEDGE_NODE-11",
"text": "**Settings** page.\\n2. Open the **Plug Tokens** page.\\n3. Under the **Application access tokens** panel, click **New token** and copy the token that\\xe2\\x80\\x99s displayed.\\n\\n##### \\n\\nEnsure that you copy the generated application access token, as you cannot view it again.\\n\\n#### Exchange your AAT for a session token\\n\\nTo proceed with identifying the user, you need to exchange your AAT for a session token. This step helps you identify a user of your own system within the DevRev",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-15513_KNOWLEDGE_NODE-12",
"text": "tokens** panel, click **New token** and copy the token that\\xe2\\x80\\x99s displayed.\\n\\n##### \\n\\nEnsure that you copy the generated application access token, as you cannot view it again.\\n\\n#### Exchange your AAT for a session token\\n\\nTo proceed with identifying the user, you need to exchange your AAT for a session token. This step helps you identify a user of your own system within the DevRev platform.\\n\\nHere is a simple example of an API request to the DevRev backend to exchange your AAT",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-2895_KNOWLEDGE_NODE-3",
"text": "follow these steps:\\n\\n## Generate an application access token\\n\\n 1. In DevRev, go to **Settings > Support > PLuG Tokens** through the settings icon on the top-left corner.\\n 2. Under the **Application access tokens** panel, click **New token** and copy the token that\\xe2\\x80\\x99s displayed.\\n\\n#####\\n\\nEnsure you copy your access token, as you will not be able to view it again.\\n\\n## Generate a session token\\n\\n#####\\n\\nFor security reasons, this call should be made from the server side so",
"title": "Identify your users with PLuG — DevRev | Docs"
},
{
"id": "ART-1384_KNOWLEDGE_NODE-6",
"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/auth-tokens.create\\n\\n[code]\\n\\n $| curl -X POST https://api.devrev.ai/auth-tokens.create \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer <token>\" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{}\\'\\n[/code] \\n \\nTry it\\n\\n201authTokensCreateExample\\n\\n[code]\\n\\n 1| { \\n",
"title": "Create Auth Token — 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-15370_KNOWLEDGE_NODE-0",
"text": "b'Create Dev User | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[dev-users](/api-reference/dev-users/product-builders-and-service-providers)\\n\\nCreate Dev User\\n===============\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/dev-users.create\\n\\nPOST\\n\\n/dev-users.create\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/dev-users.create \\\\ |\\n| > | -H \"Authorization: Bearer",
"title": "Create Dev User | DevRev | Docs"
},
{
"id": "ART-2933_KNOWLEDGE_NODE-18",
"text": "-X POST https://api.devrev.ai/rev-users.create \\\\ |\\n | > | -H \"Authorization: Bearer <apiKey>\" \\\\ |\\n | > | -H \"Content-Type: application/json\" \\\\ |\\n | > | -d \\'{ |\\n | > | \"rev_org\": \"<rev org display-id>\" |\\n | > | }\\' |\\n ```\\n\\n You receive the following response:\\n\\n ```\\n | | |\\n | --- | --- |\\n | 1 | { |\\n | 2 | \"rev_user\": { |\\n | 3 | \"created_by\": { |\\n | 4 | \"type\": \"dev_user\", |\\n | 5 | \"display_id\": \"DEVU-1\", |\\n | 6 | \"display_name\": \"someorg\",",
"title": "Account creation | DevRev | Docs"
},
{
"id": "ART-4118_KNOWLEDGE_NODE-0",
"text": "b'[](/beta/api-reference/dev-users/create)\\n\\nBeta\\n\\n[API Reference](/beta/api-reference/accounts/create)[Dev Users](/beta/api-reference/dev-users/activate)\\n\\n# Create Dev User\\n\\nPOST\\n\\nhttps://api.devrev.ai/dev-users.create\\n\\nTry it\\n\\nCreates a Dev user for a Dev organization.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\nemailstringRequired`format: \"text\"`\\n\\nEmail of the Dev user.\\n\\nstateenumRequired\\n\\nAllowed values:",
"title": "Create Dev User (Beta) — DevRev | Docs"
},
{
"id": "ART-15506_KNOWLEDGE_NODE-6",
"text": "[here](https://devrev.ai/docs/product/grow).\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl --location \\'https://api.devrev.ai/auth-tokens.create\\' \\\\ |\\n| > | --header \\'accept: application/json, text/plain, */*\\' \\\\ |\\n| > | --header \\'authorization: <AAT>\\' \\\\ |\\n| > | --header \\'content-type: application/json\\' \\\\ |\\n| > | --data-raw \\'{ |\\n| > | \"rev_info\": { |\\n| > | \"user_ref\": \"example@devrev.ai\", |\\n| > | \"account_ref\": \"devrev.ai\", |\\n| > | \"workspace_ref\": \"devrev-dev\", |\\n| > |",
"title": "Identify your users with Plug | 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-1955_KNOWLEDGE_NODE-45",
"text": "creating system user token\\n\\n Privileges: token object ['CREATE']\\n* *Conversation Admin:* Contains privileges on conversations.\\n\\n Privileges: conversation object ['READ', 'UPDATE', 'DELETE', 'CREATE']\\n* *Artifact Admin Reader:* Contains unconditional read privileges on artifacts.\\n\\n Privileges: artifact object ['READ']\\n* *devu Admin:* Contains privileges for admins on devu.\\n\\n Privileges: devu object ['CREATE', 'READ', 'UPDATE', 'DELETE']\\n* *revu Admin:* Contains privileges for",
"title": "Default privileges by group | Roles | Computer by DevRev | DevRev"
},
{
"id": "ART-1302_KNOWLEDGE_NODE-58",
"text": "Reference auth-tokens Create.\\n\\nPOST https:// api.devrev.ai / auth-tokens.create\\nCreates a JWT corresponding to the requested token type for the authenticated user.\\nRequest.\\n\\nThis endpoint expects an object.\\nact_as string Optional\\nThe unique ID of the Dev user or the service account to impersonate.\\naud list of strings Optional\\nThe expected audience values with respect to the token.\\nclient_id string Optional\\n\\nAn identifier that represents the application which is requesting the",
"title": "Export — DevRev | Docs"
},
{
"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-16579_KNOWLEDGE_NODE-10",
"text": "`DevRev.identifyVerifiedUser(userID, sessionToken)` method.\\n\\n##### \\n\\nFor security reasons, it is **strongly recommended** that the token exchange is executed on your backend to prevent exposing your application access token (AAT).\\n\\n#### Generate an AAT\\n\\n1. Open the DevRev web app at [https://app.devrev.ai](https://app.devrev.ai/) and go to the **Settings** page.\\n2. Open the **Plug Tokens** page.\\n3. Under the **Application access tokens** panel, click **New token** and copy the token",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-1781_KNOWLEDGE_NODE-53",
"text": "api.devrev.ai / auth-tokens.create\\nCreates a JWT corresponding to the requested token type for the authenticated user.\\nRequest.\\n\\nThis endpoint expects an object.\\nact_as string Optional\\nThe unique ID of the Dev user or the service account to impersonate.\\naud list of strings Optional\\nThe expected audience values with respect to the token.\\nclient_id string Optional\\n\\nAn identifier that represents the application which is requesting the token. If no client_id is present in the request to",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1308_KNOWLEDGE_NODE-55",
"text": "Reference auth-tokens Create.\\n\\nPOST https:// api.devrev.ai / auth-tokens.create\\nCreates a JWT corresponding to the requested token type for the authenticated user.\\nRequest.\\n\\nThis endpoint expects an object.\\nact_as string Optional\\nThe unique ID of the Dev user or the service account to impersonate.\\naud list of strings Optional\\nThe expected audience values with respect to the token.\\nclient_id string Optional\\n\\nAn identifier that represents the application which is requesting the",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1780_KNOWLEDGE_NODE-53",
"text": "Reference auth-tokens Create.\\n\\nPOST https:// api.devrev.ai / auth-tokens.create\\nCreates a JWT corresponding to the requested token type for the authenticated user.\\nRequest.\\n\\nThis endpoint expects an object.\\nact_as string Optional\\nThe unique ID of the Dev user or the service account to impersonate.\\naud list of strings Optional\\nThe expected audience values with respect to the token.\\nclient_id string Optional\\n\\nAn identifier that represents the application which is requesting the",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1301_KNOWLEDGE_NODE-58",
"text": "Reference auth-tokens Create.\\n\\nPOST https:// api.devrev.ai / auth-tokens.create\\nCreates a JWT corresponding to the requested token type for the authenticated user.\\nRequest.\\n\\nThis endpoint expects an object.\\nact_as string Optional\\nThe unique ID of the Dev user or the service account to impersonate.\\naud list of strings Optional\\nThe expected audience values with respect to the token.\\nclient_id string Optional\\n\\nAn identifier that represents the application which is requesting the",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-15506_KNOWLEDGE_NODE-4",
"text": "RevUser Session Token(5) Return Session Token(6) Call plugSDK.init() with token\\n\\nGenerate an application access token\\n------------------------------------\\n\\n1. In DevRev, go to **Settings > Support > Plug Tokens** through the settings icon on the top-left corner.\\n2. Under the **Application access tokens** panel, click **New token** and copy the token that\\xe2\\x80\\x99s displayed.\\n\\n##### \\n\\nEnsure you copy your access token, as you cannot view it again.\\n\\nGenerate a session",
"title": "Identify your users with Plug | DevRev | Docs"
},
{
"id": "ART-12992_KNOWLEDGE_NODE-4",
"text": "Error\\n\\n500\\n\\nInternal Server Error\\n\\n503\\n\\nService Unavailable Error\\n\\nPOST\\n\\n/dev-users.create\\n\\n[code]\\n\\n $| curl -X POST https://api.devrev.ai/dev-users.create \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer <token>\" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"email\": \"foo\", \\n >| \"state\": \"shadow\" \\n >| }\\'\\n[/code] \\n \\nTry it\\n\\n201devUsersCreateExample\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2|",
"title": "Create Dev User — DevRev | Docs"
},
{
"id": "ART-4118_KNOWLEDGE_NODE-2",
"text": "properties\\n\\nfull_namestringOptional`format: \"text\"`\\n\\nFull name of the Dev user.\\n\\nreports_tostringOptional`format: \"id\"`\\n\\nThe ID of the user that the user reports to.\\n\\n### Response\\n\\nResponse object for request to create a new Dev user for a Dev organization.\\n\\ndev_userobject\\n\\nShow 20 properties\\n\\nPOST\\n\\n/dev-users.create\\n\\n[code]\\n\\n $| curl -X POST https://api.devrev.ai/dev-users.create \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer <token>\" \\\\ \\n >| -H",
"title": "Create Dev User (Beta) — DevRev | Docs"
},
{
"id": "ART-15513_KNOWLEDGE_NODE-11",
"text": "and the exchanged session token to the `DevRev.identifyVerifiedUser(userId: String, sessionToken: String)` method.\\n\\n##### \\n\\nFor security reasons, it is **strongly recommended** that the token exchange is executed on your backend to prevent exposing your application access token (AAT).\\n\\n#### Generate an AAT\\n\\n1. Open the DevRev web app at [https://app.devrev.ai](https://app.devrev.ai/) and go to the **Settings** page.\\n2. Open the **Plug Tokens** page.\\n3. Under the **Application access",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-5151_KNOWLEDGE_NODE-2",
"text": "Error\\n\\nPOST\\n\\n/service-accounts.create\\n\\n[code]\\n\\n $| curl -X POST https://api.devrev.ai/service-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\\n201serviceAccountsCreateExample\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"service_account\": { \\n 3| \"id\": \"foo\", \\n 4| \"created_by\":",
"title": "Create Service Account — 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-1786_KNOWLEDGE_NODE-55",
"text": "an application access token (AAT).\\nrefresh_token string Optional\\nA token to refresh the issued token.\\nscope string Optional\\nThe scopes associated with the issued token. A space-delimited list of values in which the order of values does not matter.\\nPOST / auth-tokens.create\\ncURL\\n$ curl -X POST https://api.devrev.ai/auth-tokens.create \\\\ > -H \" Authorization: Bearer <token> \" \\\\ > -H \" Content-Type: application/json \" \\\\ > -d \\' {} \\'\\n200 Successful 1 { 2 \" access_token \" : \" access_token",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1787_KNOWLEDGE_NODE-55",
"text": "an application access token (AAT).\\nrefresh_token string Optional\\nA token to refresh the issued token.\\nscope string Optional\\nThe scopes associated with the issued token. A space-delimited list of values in which the order of values does not matter.\\nPOST / auth-tokens.create\\ncURL\\n$ curl -X POST https://api.devrev.ai/auth-tokens.create \\\\ > -H \" Authorization: Bearer <token> \" \\\\ > -H \" Content-Type: application/json \" \\\\ > -d \\' {} \\'\\n200 Successful 1 { 2 \" access_token \" : \" access_token",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1304_KNOWLEDGE_NODE-57",
"text": "objects\\nThe POST policy form data.\\nShow 2 properties\\nurl string\\nThe URL that the file\\'s data should be uploaded to.\\nAPI Reference auth-tokens Create.\\n\\nPOST https:// api.devrev.ai / auth-tokens.create\\nCreates a JWT corresponding to the requested token type for the authenticated user.\\nRequest.\\n\\nThis endpoint expects an object.\\nact_as string Optional\\nThe unique ID of the Dev user or the service account to impersonate.\\naud list of strings Optional\\nThe expected audience values with",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1194_KNOWLEDGE_NODE-4",
"text": "values:urn:devrev:params:oauth:grant-type:token-issueurn:ietf:params:oauth:grant-type:token-exchange\\n\\nrequested\\\\_token\\\\_typeenumOptional\\n\\nThe type of the requested token.\\n\\nShow 17 enum values\\n\\nrev\\\\_infoobjectOptional\\n\\nCarries info corresponding to the Rev user to be provisioned and/or\\nissue a Rev session token.\\n\\nShow 9 properties\\n\\nscopestringOptional`format: \"text\"`\\n\\nThe requested set of scopes associated with the issued token. A\\nspace-delimited list of values in which the",
"title": "Create Auth Token | DevRev | Docs"
},
{
"id": "ART-1194_KNOWLEDGE_NODE-2",
"text": "user.\\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\\nact\\\\_asstringOptional`format: \"id\"`\\n\\nThe unique ID of the Dev user or the service account to\\nimpersonate.\\n\\naudlist of stringsOptional\\n\\nThe expected audience values with respect to the token.\\n\\nclient\\\\_idstringOptional`format: \"text\"`\\n\\nAn identifier that represents the application which is",
"title": "Create Auth Token | DevRev | Docs"
},
{
"id": "ART-1509_KNOWLEDGE_NODE-52",
"text": "\\\\ > -H \" Authorization: Bearer <token> \" \\\\ > -H \" Content-Type: application/json \" \\\\ > -d \\' { > \"id\": \"ARTIFACT-12345\" > } \\'\\n200 Successful 1 { 2 \" form_data \" : [ 3 { 4 \" key \" : \" key \" , 5 \" value \" : \" value \" 6 } 7 ] , 8 \" url \" : \" url \" 9 }\\nAPI Reference auth-tokens Create.\\n\\nPOST https:// api.devrev.ai / auth-tokens.create\\nCreates a JWT corresponding to the requested token type for the authenticated user.\\nRequest.\\n\\nThis endpoint expects an object.\\nact_as string",
"title": "Prepare — DevRev | Docs"
},
{
"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-15506_KNOWLEDGE_NODE-5",
"text": "token\\n------------------------\\n\\n##### \\n\\nFor security reasons, this API call must be made from the server side to prevent exposing your application access token (AAT).\\n\\nUsing the `rev_info` method, you can generate and recognize a user within the DevRev system by providing relevant user details. This method enables you to convey information systematically, ensuring alignment between your DevRev CRM and the structured data model. For information regarding terminologies, click",
"title": "Identify your users with Plug | DevRev | Docs"
},
{
"id": "ART-15454_KNOWLEDGE_NODE-1",
"text": "\"Authorization: Bearer <token>\" \\\\ |\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{ |\\n| > | \"display_name\": \"string\" |\\n| > | }\\' |\\n```\\n\\n[Try it](/api-reference/service-accounts/create?explorer=true)\\n\\n201Created\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"service_account\": { |\\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\":",
"title": "Create Service Account | DevRev | Docs"
},
{
"id": "ART-1785_KNOWLEDGE_NODE-51",
"text": "key \" , 5 \" value \" : \" value \" 6 } 7 ] , 8 \" url \" : \" url \" 9 }\\nAPI Reference auth-tokens Create.\\n\\nPOST https:// api.devrev.ai / auth-tokens.create\\nCreates a JWT corresponding to the requested token type for the authenticated user.\\nRequest.\\n\\nThis endpoint expects an object.\\nact_as string Optional\\nThe unique ID of the Dev user or the service account to impersonate.\\naud list of strings Optional\\nThe expected audience values with respect to the token.\\nclient_id string Optional\\n\\nAn",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-12992_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)[Dev Users](/public/api-reference/dev-users/activate)\\n\\n# Create Dev User\\n\\nPOST\\n\\nhttps://api.devrev.ai/dev-users.create\\n\\nTry it\\n\\nCreates a Dev user for a Dev organization.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\nemailstringRequired`format: \"text\"`\\n\\nEmail of the Dev",
"title": "Create Dev User — 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-4118_KNOWLEDGE_NODE-3",
"text": "\"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"email\": \"email\", \\n >| \"state\": \"shadow\" \\n >| }\\'\\n[/code] \\n \\nTry it\\n\\n201Created\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"dev_user\": { \\n 3| \"id\": \"id\", \\n 4| \"created_by\": { \\n 5| \"type\": \"dev_user\", \\n 6| \"id\": \"id\", \\n 7| \"display_id\": \"display_id\", \\n 8| \"display_name\": \"display_name\", \\n 9| \"display_picture\": { \\n 10|",
"title": "Create Dev User (Beta) — DevRev | Docs"
},
{
"id": "ART-1384_KNOWLEDGE_NODE-2",
"text": "of days. In practice, the value should be based on the usage of the token.\\n\\ngrant_typeenumOptional\\n\\nAllowed values: urn:devrev:params:oauth:grant-type:token-issueurn:ietf:params:oauth:grant-type:token-exchange\\n\\nSpecifies the process of obtaining a token.\\n\\nrequested_token_typeenumOptional\\n\\nThe type of the requested token.\\n\\nShow 17 enum values\\n\\nrev_infoobjectOptional\\n\\nCarries info corresponding to the Rev user to be provisioned and/or issue a Rev session token.\\n\\nShow 9",
"title": "Create Auth Token — DevRev | Docs"
},
{
"id": "ART-15454_KNOWLEDGE_NODE-0",
"text": "b'Create Service 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)[service-accounts](/api-reference/service-accounts/create)\\n\\nCreate Service Account\\n======================\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/service-accounts.create\\n\\nPOST\\n\\n/service-accounts.create\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/service-accounts.create \\\\ |\\n| > | -H",
"title": "Create Service Account | DevRev | Docs"
},
{
"id": "ART-1782_KNOWLEDGE_NODE-52",
"text": "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.\\nAPI Reference auth-tokens Create.\\n\\nPOST https:// api.devrev.ai / auth-tokens.create\\nCreates a JWT corresponding to the requested token type for the authenticated user.\\nRequest.\\n\\nThis endpoint expects an object.\\nact_as string Optional\\nThe unique ID of the Dev user or the service account to",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1805_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.\\nAPI Reference auth-tokens Create.\\n\\nPOST https:// api.devrev.ai / auth-tokens.create\\nCreates a JWT corresponding to the requested token type for the authenticated user.\\nRequest.\\n\\nThis endpoint expects an object.\\nact_as string Optional\\nThe unique ID of the Dev user or the service account",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1591_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.\\nAPI Reference auth-tokens Create.\\n\\nPOST https:// api.devrev.ai / auth-tokens.create\\nCreates a JWT corresponding to the requested token type for the authenticated user.\\nRequest.\\n\\nThis endpoint expects an object.\\nact_as string Optional\\nThe unique ID of the Dev user or the service account",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1803_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.\\nAPI Reference auth-tokens Create.\\n\\nPOST https:// api.devrev.ai / auth-tokens.create\\nCreates a JWT corresponding to the requested token type for the authenticated user.\\nRequest.\\n\\nThis endpoint expects an object.\\nact_as string Optional\\nThe unique ID of the Dev user or the service account",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1792_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.\\nAPI Reference auth-tokens Create.\\n\\nPOST https:// api.devrev.ai / auth-tokens.create\\nCreates a JWT corresponding to the requested token type for the authenticated user.\\nRequest.\\n\\nThis endpoint expects an object.\\nact_as string Optional\\nThe unique ID of the Dev user or the service account",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1825_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.\\nAPI Reference auth-tokens Create.\\n\\nPOST https:// api.devrev.ai / auth-tokens.create\\nCreates a JWT corresponding to the requested token type for the authenticated user.\\nRequest.\\n\\nThis endpoint expects an object.\\nact_as string Optional\\nThe unique ID of the Dev user or the service account",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1652_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.\\nAPI Reference auth-tokens Create.\\n\\nPOST https:// api.devrev.ai / auth-tokens.create\\nCreates a JWT corresponding to the requested token type for the authenticated user.\\nRequest.\\n\\nThis endpoint expects an object.\\nact_as string Optional\\nThe unique ID of the Dev user or the service account",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1607_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.\\nAPI Reference auth-tokens Create.\\n\\nPOST https:// api.devrev.ai / auth-tokens.create\\nCreates a JWT corresponding to the requested token type for the authenticated user.\\nRequest.\\n\\nThis endpoint expects an object.\\nact_as string Optional\\nThe unique ID of the Dev user or the service account",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1575_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.\\nAPI Reference auth-tokens Create.\\n\\nPOST https:// api.devrev.ai / auth-tokens.create\\nCreates a JWT corresponding to the requested token type for the authenticated user.\\nRequest.\\n\\nThis endpoint expects an object.\\nact_as string Optional\\nThe unique ID of the Dev user or the service account",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1593_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.\\nAPI Reference auth-tokens Create.\\n\\nPOST https:// api.devrev.ai / auth-tokens.create\\nCreates a JWT corresponding to the requested token type for the authenticated user.\\nRequest.\\n\\nThis endpoint expects an object.\\nact_as string Optional\\nThe unique ID of the Dev user or the service account",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1637_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.\\nAPI Reference auth-tokens Create.\\n\\nPOST https:// api.devrev.ai / auth-tokens.create\\nCreates a JWT corresponding to the requested token type for the authenticated user.\\nRequest.\\n\\nThis endpoint expects an object.\\nact_as string Optional\\nThe unique ID of the Dev user or the service account",
"title": "Delete — DevRev | Docs"
}
] |
bbd30769-6f0e-4d61-abcb-fbe933593257
|
modify a vista to manage tickets in a shared view
|
[
{
"id": "ART-1955_KNOWLEDGE_NODE-75",
"text": "Field Access:* Ticket admin field access role\\n\\n Privileges: ticket object None\\n* *Contact Admin Field Access:* Contact Admin field access role\\n\\n Privileges: revu object None\\n* *Vista Creator:* A role that allows a user to create a vista\\n\\n Privileges: vista object ['CREATE']\\n* *Vista Owner:* A role that allows the creator to view, edit and delete a vista\\n\\n Privileges: vista object ['READ', 'UPDATE', 'DELETE']\\n* *Issue Admin Field Access:* Issue admin field access role\\n\\n",
"title": "Default privileges by group | Roles | 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"
}
] |
5b10870e-a5d5-41d3-a77e-d707af0754aa
|
DevRev AI support agent assistance chat assistance
|
[
{
"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-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-13178_KNOWLEDGE_NODE-24",
"text": "Agentic AI offers a proven solution.\\n\\n 1. Technical support improves with agentic AI capabilities. [DevRev\\xe2\\x80\\x99s support](/support) agents diagnose and resolve technical issues by analyzing error reports, system information, and knowledge bases. They guide users through troubleshooting steps and automatically document resolution paths. \\nUnlike traditional systems, these AI agents leverage retrieval augmented generation to access information across multiple sources, delivering",
"title": "Understanding Agentic AI: Capabilities and Implications for the Future"
},
{
"id": "ART-15153_KNOWLEDGE_NODE-4",
"text": "without expanding their team size.\\n\\nThe solution: Redefining support with DevRev\\n--------------------------------------------\\n\\nDeepdub selected DevRev to transform their customer support through conversational AI and a comprehensive knowledge system. The implementation included:\\n\\n* Building an extensive knowledge base from existing information\\n* Deploying PLuG live chat to make self-service the preferred choice\\n* Creating automation for common support questions\\n* Generating new",
"title": "Deepdub scales global AI support with DevRev’s conversational platform and intelligent knowledge automation"
},
{
"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-1771_KNOWLEDGE_NODE-7",
"text": "queries instantly, which frees up our human support agents to promptly address more complex issues.\\n\\n![]()\\n\\nAnkur ShresthaCo-Founder of Tough Trucks for Kids\\n\\nThe impact: Automation, scalability, measurable results\\n-------------------------------------------------------\\n\\n#### Powerful AI automation\\n\\nDevRev\\'s Conversational AI agent intelligently handles 85-90% of routine customer inquiries without human intervention, allowing the support team to focus on more complex issues that",
"title": "ToughTrucksForKids.com achieves dramatic efficiency gains and customer satisfaction through AI-powered support automation"
},
{
"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-1987_KNOWLEDGE_NODE-25",
"text": "Knowledge base, while keeping a support agent subscribed to conversations. If it cannot answer a certain query or you request it to connect to the team, it will redirect it to the default owner of the conversation.\\n\\nWhen looking for a source to inform its answer, it will prioritize the QA pairs, which are intended to serve as definitive answers to commonly repeated questions.\\n\\n![]()\\n\\nFor Computer to suggest articles, you need to add articles to your DevRev instance. Refer to",
"title": "Turing AI agent | Computer for Support Teams | DevRev"
},
{
"id": "ART-1027_KNOWLEDGE_NODE-9",
"text": "workflows** that streamline ticket triaging and severity assessment.\\n\\n### AI-powered deflection at scale\\n\\nAI answering has stabilized around 32\\xe2\\x80\\x9340% of all inquiries, with complex queries intelligently routed to human agents. **Computer CX Agents** for free vs. paid customers optimize deflection strategies for each segment, delivering tailored support while maximizing efficiency.\\n\\nDevRev has enabled us to streamline access to technical documentation, automate common developer",
"title": "Descope streamlines support at scale with automation, AI, and unified collaboration"
},
{
"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-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-4171_KNOWLEDGE_NODE-3",
"text": "insights\\n--------------------------------\\n\\n### Resolve tickets more efficiently with AI-powered assistance\\n\\n[Book a Demo](/request-a-demo)[Discover Turing AI](/agent-os)\\n\\nTuring AI identifies recurring patterns in support queries to suggest recommended next steps, similar tickets, and related articles so your agents are empowered to tackle every query\\n\\n![]()\\n\\nDevRev has centralized our workflows. Our team love it because it allows us to support our customers",
"title": "Make customer support real-time and personalized"
},
{
"id": "ART-1840_KNOWLEDGE_NODE-12",
"text": "allowing customers to receive faster assistance\\n* **20% decrease in operational costs**, driven by automation and AI-powered efficiencies\\n* **15% shorter resolution cycles**, helping the team close tickets more quickly\\n* **Higher agent productivity**, thanks to AI-suggested replies that reduce the time spent on drafting responses\\n* **Improved customer satisfaction**, with accurate answers delivered through AI chat and a growing self-service knowledge base\\n* **Deeper visibility through",
"title": "Revolutionising health tech support: how Binah.ai cut response times by 50% with DevRev"
},
{
"id": "ART-1987_KNOWLEDGE_NODE-24",
"text": "(Beta)](#goaloriented-mode-beta)\\n\\n1. [Documentation](/docs)\\n3. [Computer for Support Teams](/docs/product/support)\\n[Turing AI agent](/docs/product/conversational-bot)\\n\\nComputer for Your Customers and Turing\\n======================================\\n\\nUsing Turing, Computer can be used to deflect user queries in conversation or to suggest articles from your knowledge base for resolving tickets. It will try to answer customer queries based on the articles and QA pairs provided in the",
"title": "Turing AI agent | Computer for Support Teams | DevRev"
},
{
"id": "ART-15153_KNOWLEDGE_NODE-7",
"text": "Q&As from completed support conversations, with over 2,000 AI-generated entries improving the knowledge base. When similar questions arise, customers receive immediate answers without needing human intervention.\\n\\n### Scalable solution for growth\\n\\nThe platform effectively supports:\\n\\n* 24/7 global support coverage\\n* Tens of thousands of platform users through PLuG live chat\\n\\n### Minimized business impact\\n\\nBy connecting all their support information through DevRev, Deepdub provides",
"title": "Deepdub scales global AI support with DevRev’s conversational platform and intelligent knowledge automation"
},
{
"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-15716_KNOWLEDGE_NODE-14",
"text": "AI Bot \\xe2\\x80\\x93 Turing\\n\\nYes! DevRev offers an AI-powered assistant called Turing , which can answer questions, suggest articles, summarize conversations, and more. You can read more about it in the documentation: [https://docs.devrev.ai/product/conversational-bot](https://docs.devrev.ai/product/conversational-bot)\\n\\n4.\\xe2\\x80\\x82Difference Between Runnables and Features\\n\\nA feature is a unit of configuration or capability in the product, often representing a user-facing function or",
"title": "Support queries related playbook"
},
{
"id": "ART-1969_KNOWLEDGE_NODE-27",
"text": "that provides the first line of response from articles uploaded into your knowledge base.\\n\\nYou can also customize the Plug widget to make announcements or highlight something to your customers.\\n\\n\\xf0\\x9f\\x93\\xa8 Inbox\\n-------\\n\\nThe [Support Inbox](../product/inbox) is where conversations started by your customers appear\\xe2\\x80\\x94whether they use Plug, email, Slack, or another integration.\\n\\nSlash commands are available in conversations to provide AI assistance to customer experience",
"title": "Computer for Support Teams | DevRev"
},
{
"id": "ART-16789_KNOWLEDGE_NODE-6",
"text": "\"Computer vs DevRev\" \"What\\'s the difference between Computer and DevRev?\" \"DevRev rebranding\"\\n\\nAnswer: Computer is DevRev\\'s new unified AI teammate product. Computer is the base product that everything else builds on, with specialized apps like Computer for Support Teams, Computer for Builders, Computer for User Insights and specialized AI agent- Computer for Your Customers (Computer Customer Experience Agent) as add-ons.Q: What happened to DevRev\\'s other products?\\n\\nAlternative",
"title": "Computer General FAQs"
},
{
"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-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-1987_KNOWLEDGE_NODE-26",
"text": "[articles](./articles) for more information.\\n\\nOnce you have added your knowledge base, Turing can be switched on in two modes: suggestion or auto-response. You can configure Turing in **Settings > Turing Answers** and turn on the **Turing Answers** toggle.\\n\\nSuggest-only mode\\n-----------------\\n\\nComputer only suggests an answer to the user query. A support agent can accept or make edits to the answer, then send it to the user.\\n\\nContent-powered mode\\n--------------------\\n\\nComputer",
"title": "Turing AI agent | Computer for Support Teams | DevRev"
},
{
"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"
},
{
"id": "ART-1027_KNOWLEDGE_NODE-5",
"text": "centralized platform for its support team, enabling scalable, product-led support tailored for fast-growing, API-first companies. With DevRev\\xe2\\x80\\x99s agentic AI capabilities, Descope shifted from manual triage to autonomous systems that learn, act, and continuously improve.\\n\\nKey solution pillars included:\\n\\n* A unified inbox integrating Slack, email, and in-app conversations\\n* Automated journey orchestration to triage, route, and resolve issues with Computer CX Agents\\n* AI workflows",
"title": "Descope streamlines support at scale with automation, AI, and unified collaboration"
},
{
"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-3038_KNOWLEDGE_NODE-8",
"text": "accelerating both support and engineering workflows.\\n\\nBolt also began leveraging **Agent Studio for Computer**, introducing four specialized AI agents: one each for Merchants, Shoppers, Mobile App users, and Developers (via their documentation site). These agents allow Bolt to scale intelligent support and self-service across their dual customer base and technical ecosystem, while reinforcing DevRev\\xe2\\x80\\x99s AI-native approach.\\n\\nOn the product and engineering side, Bolt now uses AI",
"title": "Bolt unifies support and product to deliver seamless commerce"
},
{
"id": "ART-1987_KNOWLEDGE_NODE-27",
"text": "automatically replies to the user query before it gets assigned to support. It goes through the knowledge base (articles and QAs), generates an answer, and checks with the user if the answer is useful or not.\\n\\n* If Computer doesn't understand the query, it gives the user an option to rephrase the question and ask again.\\n* If the user marks the answer as useful, Computer asks the user if they have more questions, then resolves the conversation.\\n* If the user marks the answer as not useful,",
"title": "Turing AI agent | Computer for Support Teams | DevRev"
},
{
"id": "ART-4167_KNOWLEDGE_NODE-1",
"text": "resolutions by up to 10x.\\n\\nComputer\\xe2\\x80\\x99s customer experience agent is a problem solver that clears tickets with ease.\\n\\n### Next-gen customer support\\n\\nNext-gen customer support\\n\\nStart with Computer\\xe2\\x80\\x99s battle-tested CX agent that has instant, accurate answers to customer questions.\\n\\n![]()\\n\\n### Take action\\n\\n### Build agent teams\\n\\nMeet your customers where they are, in your voice.\\n\\nTrain Computer on your brand\\xe2\\x80\\x99s voice, no matter where you deploy it.",
"title": "Computer for Your Customers: AI Self-Service Support | DevRev"
},
{
"id": "ART-3012_KNOWLEDGE_NODE-0",
"text": "b'Get-Reply Recommendations | 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)[recommendations](/beta/api-reference/recommendations/chat-completions)\\n\\nGet-Reply Recommendations\\n=========================\\n\\nBeta\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/recommendations.get-reply\\n\\nPOST\\n\\n/recommendations.get-reply\\n\\ncURL\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST",
"title": "Get-Reply Recommendations | DevRev | Docs"
},
{
"id": "ART-15510_KNOWLEDGE_NODE-9",
"text": "(conversations) dialog supported by our DevRev SDK. The support chat feature can be shown as a modal screen from the top-most screen.\\n\\n##### \\n\\nThis functionality requires 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```\\n| | |\\n| --- | --- |\\n| 1 | DevRev.showSupport(successCallback, errorCallback) |\\n```\\n\\n### Creating a new support",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-1840_KNOWLEDGE_NODE-11",
"text": "customers find answers faster.\\n\\nOne of the early \\xe2\\x80\\x9cwow\\xe2\\x80\\x9d moments for the team came when they simply input their website URL into Computer and instantly had a fully functional AI-based chatbot offering fast, human-like support, powered by their own public knowledge.\\n\\nData-Backed Transformation\\n--------------------------\\n\\nAfter implementing DevRev, Binah.ai experienced measurable improvements across their support operations:\\n\\n* **50% reduction in response times**,",
"title": "Revolutionising health tech support: how Binah.ai cut response times by 50% with DevRev"
}
] |
3043c0f9-2607-4b34-9491-b8ba302b9ce6
|
AirSync Jira Datacenter mapping error something went wrong
|
[
{
"id": "ART-2053_KNOWLEDGE_NODE-60",
"text": "the mapping phase in the initial import, one can opt out of the permission AirSync by deselecting **Authorization Policy** option, additionally groups and group members can also be deselected. As project roles are mapped to DevRev groups, deselecting groups and group members also prevents project roles from being imported.\\n\\n![]()\\n\\nFor Jira Data Center, the permissions AirSync is not yet supported.\\n\\nAirSync Jira scope and limitations\\n----------------------------------\\n\\nThe following is",
"title": "Jira Software AirSync | AirSync | Snap-ins | DevRev"
},
{
"id": "ART-2053_KNOWLEDGE_NODE-54",
"text": "the AirSync functionality.\\n\\nAdminister Jira global permission is required for:\\n\\n* Custom field extraction - without extracting custom fields AirSync is unable to load them into DevRev, which might become problematic especially on reverse syncs if some of these fields are deemed required by Jira on issue creation.\\n* User extraction (Jira Data Center only) - admin permissions are required to access the application roles, which contain the users that have access to the Jira application.",
"title": "Jira Software AirSync | AirSync | Snap-ins | DevRev"
},
{
"id": "ART-17232_KNOWLEDGE_NODE-3",
"text": "process.\\n\\nThere are several reasons why some mappings might be unavailable:\\n\\n1. A common reason is mismatch of types. For example, if a DevRev field is expected to be `rich_text`,\\n but the field is set as `text` mapping to some fields is unavailable.\\n Refer to the [supported types](/public/airsync/metadata-extraction#declare-fields-for-each-record-type)\\n section and the general DevRev documentation for more information.\\n2. Only references can be mapped to references. Ensure that",
"title": "Mapping reasons | DevRev | Docs"
},
{
"id": "ART-16749_KNOWLEDGE_NODE-1",
"text": "request\"\\n}\\n\\nHow to Fix:\\n\\nRefresh the page to load the latest blueprint and status versions.\\n\\nComplete your field mappings again.\\n\\nSubmit the mappings \\xe2\\x80\\x94 the request should now succeed.'",
"title": "Troubleshooting Airdrop Mapping Error: “Something Went Wrong”"
},
{
"id": "ART-16749_KNOWLEDGE_NODE-0",
"text": "b'This error usually occurs when the mapping request is sent with stale data. It happens when the blueprint or status version in your browser is outdated compared to the server.\\n\\nTo confirm:\\n\\nOpen the Network tab in your browser\\xe2\\x80\\x99s developer tools.\\n\\nCheck the response to the low-code POST request.\\n\\nResponse should look like this:{\\n \"message\": \"recipe-manager-RecipeManagerInvalidArgument-Unspecified: blueprint or status version changed: was 9_9 on the server and 8_8 in the",
"title": "Troubleshooting Airdrop Mapping Error: “Something Went Wrong”"
},
{
"id": "ART-17218_KNOWLEDGE_NODE-8",
"text": "|\\n```\\n\\n[3](/airsync/initial-domain-mapping#use-the-chef-ui)\\n\\n### Use the Chef UI\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | chef-cli configure-mappings --env prod |\\n```\\n\\nIf your org is not in `US-East-1`, you h ave to override an environment variable to make sure the tool reaches the right server. For example:\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | ACTIVE_PARTITION=dvrv-in-1 chef-cli configure-mappings --env prod |\\n```\\n\\nThe options are: `dvrv-us-1`, `dvrv-eu-1`, `dvrv-in-1`, and",
"title": "Initial domain mapping | DevRev | Docs"
},
{
"id": "ART-17232_KNOWLEDGE_NODE-4",
"text": "source system fields are correctly\\n mapped to reference fields in DevRev.\\n3. Support for the `struct` type is limited. Marking a field as a struct in the metadata schema will\\n make it unavailable for mapping outside of using the custom jq transformation method.\\n Refer to the [metadata tips](/public/airsync/faq#metadata-extraction) for more information.\\n4. Links are supported only on works and conversations.\\n\\nTransformation methods\\n----------------------\\n\\nThe following tables",
"title": "Mapping reasons | DevRev | Docs"
},
{
"id": "ART-17217_KNOWLEDGE_NODE-7",
"text": "file, |\\n| 43 | initialDomainMapping: { |\\n| 44 | /* your initial domain mapping JSON here */ |\\n| 45 | }, |\\n| 46 | // options: {}, |\\n| 47 | }); |\\n| 48 | } |\\n| 49 | }; |\\n| 50 | |\\n| 51 | export default run; |\\n```\\n\\n##### \\n\\nYou must pass the `initialDomainMapping` parameter to\\n`spawn` when running extraction phases. This ensures the correct\\ndomain mapping is installed and used by the snap-in.\\n\\nWas this page helpful?\\n\\nYesNo\\n\\n[Previous](/airsync/manifest)[#### External sync units",
"title": "Extraction phases | DevRev | Docs"
}
] |
5cf34928-8946-43dc-bb10-2bf6a178340e
|
synchronize AI agent created tickets to Hubspot
|
[
{
"id": "ART-2038_KNOWLEDGE_NODE-26",
"text": "Attachment on Note | Attachment on Comment | \\xe2\\x9c\\x85 |\\n| User | DevUser | \\xe2\\x9c\\x85 |\\n| Ticket | Ticket | \\xe2\\x9d\\x8c |\\n| Product | Part | \\xe2\\x9d\\x8c |\\n| Timeline | Timeline | \\xe2\\x9d\\x8c |\\n| Conversation | Conversation | \\xe2\\x9d\\x8c |\\n| Custom Object | Custom Object | \\xe2\\x9d\\x8c |\\n\\nImporting from Hubspot\\n----------------------\\n\\nFollow the steps below to import from Hubspot:\\n\\n![]()\\n\\nFor best results, AirSyncs should be done using an administrator account on the",
"title": "Hubspot AirSync | AirSync | Snap-ins | DevRev"
}
] |
5bdfbf16-2fa4-4cf9-b4cb-ea5c93cb6ba9
|
how to create a view
|
[
{
"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-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-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-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-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-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"
}
] |
07cada46-4975-4849-81d5-caa4069861a7
|
shortcut to go to next ticket in a view
|
[
{
"id": "ART-1963_KNOWLEDGE_NODE-26",
"text": "Use Shift + Escape on Windows, Linux, and macOS.\\n\\n**Ticket and Conversations shortcuts:**\\n\\n* Toggle list or chat view: Use Shift + V on Windows, Linux, and macOS.\\n* Select next ticket: Use Alt + Up/Down Arrow on Windows and Linux, or Option + Up/Down Arrow on macOS.\\n\\n### Text editor keyboard shortcuts\\n\\n**Basic commands:**\\n\\n* Copy: Use Control + C on Windows and Linux, or Cmd + C on macOS.\\n* Cut: Use Control + X on Windows and Linux, or Cmd + X on macOS.\\n* Paste: Use Control + V on",
"title": "Accessing DevRev | Computer by DevRev | DevRev"
}
] |
46a0d571-8a05-4c99-8c78-c76bff44a2cb
|
create personal canned response in DevRev
|
[
{
"id": "ART-1549_KNOWLEDGE_NODE-374",
"text": "endpoint returns an object.\\npreference object\\nShow variant\\nAPI Reference question-answers Create Question Answer.\\n\\nPOST https://api.devrev.ai / question-answers.create\\n\\nCreates a question-answer.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nanswer string Required\\n\\nAnswer of the question-answer.\\n\\napplies_to_parts list of strings Required\\n\\nThe parts that the question-answer applies to.\\n\\nowned_by list of strings Required\\n\\nThe users that own the question-answer.\\n\\nquestion",
"title": "List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1551_KNOWLEDGE_NODE-374",
"text": "endpoint returns an object.\\npreference object\\nShow variant\\nAPI Reference question-answers Create Question Answer.\\n\\nPOST https://api.devrev.ai / question-answers.create\\n\\nCreates a question-answer.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nanswer string Required\\n\\nAnswer of the question-answer.\\n\\napplies_to_parts list of strings Required\\n\\nThe parts that the question-answer applies to.\\n\\nowned_by list of strings Required\\n\\nThe users that own the question-answer.\\n\\nquestion",
"title": "Update (Beta) — DevRev | Docs"
},
{
"id": "ART-1562_KNOWLEDGE_NODE-375",
"text": "endpoint returns an object.\\npreference object\\nShow variant\\nAPI Reference question-answers Create Question Answer.\\n\\nPOST https://api.devrev.ai / question-answers.create\\n\\nCreates a question-answer.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nanswer string Required\\n\\nAnswer of the question-answer.\\n\\napplies_to_parts list of strings Required\\n\\nThe parts that the question-answer applies to.\\n\\nowned_by list of strings Required\\n\\nThe users that own the question-answer.\\n\\nquestion",
"title": "Get (Beta) — 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"
}
] |
76fa42d8-29ee-481a-b8af-9b0514670ec3
|
how to activate a user
|
[
{
"id": "ART-15377_KNOWLEDGE_NODE-1",
"text": "\"Authorization: Bearer <token>\" \\\\ |\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{ |\\n| > | \"id\": \"string\" |\\n| > | }\\' |\\n```\\n\\n[Try it](/api-reference/dev-users/activate?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"invite_sent\": true |\\n| 3 | } |\\n```\\n\\nActivates the requested user.\\n\\n### Headers\\n\\nAuthorizationstringRequired\\n\\nBearer authentication of the form `Bearer <token>`, where token is your auth token.\\n\\n### Request\\n\\nThis",
"title": "Activate Dev Users | DevRev | Docs"
},
{
"id": "ART-2902_KNOWLEDGE_NODE-0",
"text": "b'[](/beta/api-reference/dev-users/activate)\\n\\nBeta\\n\\n[API Reference](/beta/api-reference/accounts/create)[Dev Users](/beta/api-reference/dev-users/activate)\\n\\n# Activate Dev Users\\n\\nPOST\\n\\nhttps://api.devrev.ai/dev-users.activate\\n\\nTry it\\n\\nActivates the requested user.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\nidstringRequired`format: \"id\"`\\n\\nThe ID for the Dev user.\\n\\ngroupslist of stringsOptional\\n\\nIDs of the groups assigned to user during activation.\\n\\n###",
"title": "Activate Dev Users (Beta) — DevRev | Docs"
},
{
"id": "ART-12989_KNOWLEDGE_NODE-2",
"text": "stringsOptional\\n\\nIDs of the groups assigned to user during activation.\\n\\n### Response\\n\\nThe response to activate the Dev user.\\n\\ninvite_sentboolean\\n\\nWhether an invitation has been sent to the Dev user.\\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 Error\\n\\nPOST\\n\\n/dev-users.activate\\n\\n[code]\\n\\n $| curl -X POST",
"title": "Activate Dev Users — DevRev | Docs"
},
{
"id": "ART-2902_KNOWLEDGE_NODE-1",
"text": "Response\\n\\nThe response to activate the Dev user.\\n\\ninvite_sentboolean\\n\\nWhether an invitation has been sent to the Dev user.\\n\\nPOST\\n\\n/dev-users.activate\\n\\ncURL\\n\\n[code]\\n\\n $| curl -X POST https://api.devrev.ai/dev-users.activate \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer <token>\" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"id\": \"id\" \\n >| }\\'\\n[/code] \\n \\nTry it\\n\\n200Successful\\n\\n[code]\\n\\n 1| { \\n",
"title": "Activate Dev Users (Beta) — DevRev | Docs"
},
{
"id": "ART-12989_KNOWLEDGE_NODE-3",
"text": "https://api.devrev.ai/dev-users.activate \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer <token>\" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"id\": \"foo\" \\n >| }\\'\\n[/code] \\n \\nTry it\\n\\n200devUsersActivateExample\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"invite_sent\": true \\n 3| }\\n[/code] \\n \\n[Create Dev UserUp Next](/public/api-reference/dev-users/create)\\n\\n[Built",
"title": "Activate Dev Users — DevRev | Docs"
},
{
"id": "ART-15377_KNOWLEDGE_NODE-0",
"text": "b'Activate Dev Users | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[dev-users](/api-reference/dev-users/product-builders-and-service-providers)\\n\\nActivate Dev Users\\n==================\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/dev-users.activate\\n\\nPOST\\n\\n/dev-users.activate\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/dev-users.activate \\\\ |\\n| > | -H",
"title": "Activate Dev Users | DevRev | Docs"
},
{
"id": "ART-15377_KNOWLEDGE_NODE-2",
"text": "endpoint expects an object.\\n\\nidstringRequired`format: \"id\"`\\n\\nThe ID for the Dev user.\\n\\ngroupslist of stringsOptional\\n\\nIDs of the groups assigned to user during activation.\\n\\n### Response\\n\\nThe response to activate the Dev user.\\n\\ninvite\\\\_sentboolean\\n\\nWhether an invitation has been sent to the Dev user.\\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",
"title": "Activate Dev Users | DevRev | Docs"
},
{
"id": "ART-12989_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)[Dev Users](/public/api-reference/dev-users/activate)\\n\\n# Activate Dev Users\\n\\nPOST\\n\\nhttps://api.devrev.ai/dev-users.activate\\n\\nTry it\\n\\nActivates the requested user.\\n\\n### Request\\n\\nThis endpoint expects an object.\\n\\nidstringRequired`format: \"id\"`\\n\\nThe ID for the Dev user.\\n\\ngroupslist of",
"title": "Activate Dev Users — DevRev | Docs"
},
{
"id": "ART-4061_KNOWLEDGE_NODE-10",
"text": "\\n 93| \"email\": \"foo\", \\n 94| \"full_name\": \"foo\", \\n 95| \"state\": \"active\" \\n 96| }, \\n 97| \"skills\": [ \\n 98| { \\n 99| \"name\": \"foo\" \\n 100| } \\n 101| ], \\n 102| \"state\": \"active\" \\n 103| } \\n 104| }\\n[/code] \\n \\n[Update Dev UserUp Next](/public/api-reference/dev-users/update)\\n\\n[Built",
"title": "Update Dev Users Self — DevRev | Docs"
},
{
"id": "ART-15457_KNOWLEDGE_NODE-5",
"text": "| \"email\": \"string\", |\\n| 70 | \"full_name\": \"string\", |\\n| 71 | \"state\": \"active\" |\\n| 72 | }, |\\n| 73 | \"state\": \"active\" |\\n| 74 | } |\\n| 75 | } |\\n```\\n\\nUpdates the system user.\\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 ID of system user to update.\\n\\ndisplay\\\\_namestringOptional`format: \"text\"`\\n\\nUpdated",
"title": "Update Sys User | 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"
}
] |
f0c38c57-771a-41d7-9ba2-1d68f3bc2f73
|
create custom object Values in DevRev
|
[
{
"id": "ART-15502_KNOWLEDGE_NODE-5",
"text": "marketing campaigns on DevRev. This guide goes through the process of creating a \\xe2\\x80\\x9cCampaign\\xe2\\x80\\x9d custom object with relevant fields.\\n\\nAll DevRev objects require a schema. First, create a schema for the \\xe2\\x80\\x9cCampaign\\xe2\\x80\\x9d custom object. Make sure to replace the `<TOKEN>` with your API token.\\n\\n### Create custom objects\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl --location \\'https://api.devrev.ai/schemas.custom.set\\' \\\\ |\\n| > | --header \\'Content-Type:",
"title": "Custom objects | DevRev | Docs"
},
{
"id": "ART-15502_KNOWLEDGE_NODE-8",
"text": "> | \"field_type\": \"enum\", |\\n| > | \"description\": \"Target audience for the campaign\", |\\n| > | \"allowed_values\": [ |\\n| > | \"Professionals\", |\\n| > | \"Students\" |\\n| > | ] |\\n| > | } |\\n| > | ] |\\n| > | }\\' |\\n```\\n\\nNote that for custom object schemas, `is_custom_leaf_type` must be set to `true` to\\ndifferentiate it from standard DevRev object schemas.\\n\\nOnce the schema is created, you can create a custom object of type \\xe2\\x80\\x9cCampaign\\xe2\\x80\\x9d:\\n\\n```\\n| | |\\n| --- | --- |\\n| $ |",
"title": "Custom objects | DevRev | Docs"
},
{
"id": "ART-2638_KNOWLEDGE_NODE-4",
"text": "Response\\n\\nSuccess.\\n\\ncustom_objectobject\\n\\nShow 11 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/custom-objects.create\\n\\ncURL\\n\\n[code]\\n\\n $| curl -X POST https://api.devrev.ai/custom-objects.create \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer <token>\" \\\\ \\n >| -H \"Content-Type:",
"title": "Create Custom Object (Beta) — DevRev | Docs"
},
{
"id": "ART-15502_KNOWLEDGE_NODE-20",
"text": "these variants. If you want to create a\\ncampaign custom object with subtype \\xe2\\x80\\x9csocial\\\\_media\\xe2\\x80\\x9d, you can do so as follows:\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl --location \\'https://api.devrev.ai/custom-objects.create\\' \\\\ |\\n| > | --header \\'Content-Type: application/json\\' \\\\ |\\n| > | --header \\'Accept: application/json\\' \\\\ |\\n| > | --header \\'Authorization: Bearer <TOKEN>\\' \\\\ |\\n| > | --data \\'{ |\\n| > | \"leaf_type\": \"campaign\", |\\n| > | \"custom_schema_spec\": {",
"title": "Custom objects | DevRev | Docs"
},
{
"id": "ART-15502_KNOWLEDGE_NODE-9",
"text": "curl --location \\'https://api.devrev.ai/custom-objects.create\\' \\\\ |\\n| > | --header \\'Content-Type: application/json\\' \\\\ |\\n| > | --header \\'Accept: application/json\\' \\\\ |\\n| > | --header \\'Authorization: Bearer <TOKEN>\\' \\\\ |\\n| > | --data \\'{ |\\n| > | \"leaf_type\": \"campaign\", |\\n| > | \"custom_schema_spec\": { |\\n| > | \"tenant_fragment\": true |\\n| > | }, |\\n| > | \"custom_fields\": { |\\n| > | \"tnt__name\": \"Summer Sale 2023\", |\\n| > | \"tnt__start_date\": \"2023-06-01\", |\\n| > | \"tnt__end_date\":",
"title": "Custom objects | DevRev | Docs"
},
{
"id": "ART-2683_KNOWLEDGE_NODE-10",
"text": "\\'https://api.devrev.ai/custom-objects.create\\' \\\\ \\n ---|--- \\n >| --header \\'Content-Type: application/json\\' \\\\ \\n >| --header \\'Accept: application/json\\' \\\\ \\n >| --header \\'Authorization: Bearer <TOKEN>\\' \\\\ \\n >| --data \\'{ \\n >| \"leaf_type\": \"campaign\", \\n >| \"unique_key\": \"CAMP-001\", \\n >| \"custom_schema_spec\": { \\n >| \"tenant_fragment\": true \\n >| }, \\n >| \"custom_fields\": { \\n >| \"tnt__name\": \"Summer",
"title": "Custom objects (Beta) — DevRev | Docs"
},
{
"id": "ART-1564_KNOWLEDGE_NODE-109",
"text": "custom-objects.count\\n\\nCounts custom objects.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nleaf_type string Required\\n\\nLeaf type to filter.\\n\\nfilters list of any Optional\\n\\nList of filters to apply.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\ncount long\\n\\nThe count of custom objects.\\n\\nAPI Reference customization Custom Objects Create.\\n\\nPOST https://api.devrev.ai / custom-objects.create\\n\\nCreates a custom object.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nleaf_type",
"title": "List (Beta) — DevRev | Docs"
},
{
"id": "ART-1545_KNOWLEDGE_NODE-109",
"text": "custom-objects.count\\n\\nCounts custom objects.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nleaf_type string Required\\n\\nLeaf type to filter.\\n\\nfilters list of any Optional\\n\\nList of filters to apply.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\ncount long\\n\\nThe count of custom objects.\\n\\nAPI Reference customization Custom Objects Create.\\n\\nPOST https://api.devrev.ai / custom-objects.create\\n\\nCreates a custom object.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nleaf_type",
"title": "Create (Beta) — DevRev | Docs"
},
{
"id": "ART-1566_KNOWLEDGE_NODE-109",
"text": "custom-objects.count\\n\\nCounts custom objects.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nleaf_type string Required\\n\\nLeaf type to filter.\\n\\nfilters list of any Optional\\n\\nList of filters to apply.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\ncount long\\n\\nThe count of custom objects.\\n\\nAPI Reference customization Custom Objects Create.\\n\\nPOST https://api.devrev.ai / custom-objects.create\\n\\nCreates a custom object.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nleaf_type",
"title": "Transition (Beta) — DevRev | Docs"
},
{
"id": "ART-1549_KNOWLEDGE_NODE-109",
"text": "custom-objects.count\\n\\nCounts custom objects.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nleaf_type string Required\\n\\nLeaf type to filter.\\n\\nfilters list of any Optional\\n\\nList of filters to apply.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\ncount long\\n\\nThe count of custom objects.\\n\\nAPI Reference customization Custom Objects Create.\\n\\nPOST https://api.devrev.ai / custom-objects.create\\n\\nCreates a custom object.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nleaf_type",
"title": "List Post (Beta) — DevRev | Docs"
},
{
"id": "ART-1562_KNOWLEDGE_NODE-109",
"text": "custom-objects.count\\n\\nCounts custom objects.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nleaf_type string Required\\n\\nLeaf type to filter.\\n\\nfilters list of any Optional\\n\\nList of filters to apply.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\ncount long\\n\\nThe count of custom objects.\\n\\nAPI Reference customization Custom Objects Create.\\n\\nPOST https://api.devrev.ai / custom-objects.create\\n\\nCreates a custom object.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nleaf_type",
"title": "Get (Beta) — DevRev | Docs"
},
{
"id": "ART-2683_KNOWLEDGE_NODE-6",
"text": "objects\\n\\n[code]\\n\\n $| curl --location \\'https://api.devrev.ai/schemas.custom.set\\' \\\\ \\n ---|--- \\n >| --header \\'Content-Type: application/json\\' \\\\ \\n >| --header \\'Accept: application/json\\' \\\\ \\n >| --header \\'Authorization: Bearer <TOKEN>\\' \\\\ \\n >| --data \\'{ \\n >| \"type\": \"tenant_fragment\", \\n >| \"description\": \"Attributes for Campaign\", \\n >| \"leaf_type\": \"campaign\", \\n >| \"fields\": [ \\n >| { \\n >|",
"title": "Custom objects (Beta) — DevRev | Docs"
},
{
"id": "ART-15324_KNOWLEDGE_NODE-5",
"text": "must have the corresponding schema specified; omission results\\nin a Bad Request error. If a custom schema is not included in the\\nspecifier, it remains unchanged. For surfaces with human interactors,\\nit is recommended to provide tenant\\\\_fragment: true and\\nvalidate\\\\_required\\\\_fields: true.\\n\\nShow 4 properties\\n\\nstagestringOptional`format: \"id\"`\\n\\nThe stage of the custom object.\\n\\nstage\\\\_validation\\\\_optionslist of enumsOptional\\n\\nThe type of stage validations options when creating a",
"title": "Create Custom Object | DevRev | Docs"
},
{
"id": "ART-15343_KNOWLEDGE_NODE-0",
"text": "b'Set Schemas Custom | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[customization](/api-reference/customization/custom-objects-count)\\n\\nSet Schemas Custom\\n==================\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/schemas.custom.set\\n\\nPOST\\n\\n/schemas.custom.set\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/schemas.custom.set \\\\ |\\n| > | -H \"Authorization:",
"title": "Set Schemas Custom | DevRev | Docs"
},
{
"id": "ART-15324_KNOWLEDGE_NODE-6",
"text": "custom\\nobject.\\n\\nAllowed values:allow\\\\_non\\\\_start\\n\\ntitlestringOptional`format: \"text\"`\\n\\nTitle of the custom object.\\n\\nunique\\\\_keystringOptional`format: \"text\"`\\n\\nThe unique key of the custom object.This can be used to hold an\\nexternal reference to another object.\\n\\n### Response\\n\\nSuccess.\\n\\ncustom\\\\_objectobject\\n\\nShow 10 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",
"title": "Create Custom Object | DevRev | Docs"
}
] |
4cbaa340-5a11-48d8-bb17-164c5ab8bb62
|
Warning while loading opportunities error when creating new opportunity with Salesforce org connection
|
[
{
"id": "ART-17569_KNOWLEDGE_NODE-2",
"text": "connection:\\n\\nOpen a Support Case w/ SFDC Support.\\n\\nAsk to have the API Access Control feature enabled\\n\\nOnce enabled, go to the system user in SFDC and select the appropriate profle/permission set and go to System Permissions.\\n\\nCheck the box that says \"Use Any API client\"\\n\\nThis is a setting that wouldn\\'t be available without the API Access Control feature.\\n\\nRetry creating the connection after you\\'ve completed the previous steps.'",
"title": "Issues with Salesforce OAuth connection"
},
{
"id": "ART-17219_KNOWLEDGE_NODE-18",
"text": "|\\n| 13 | \"category\":\"issue\" |\\n| 14 | }, |\\n| 15 | \"comments\":{ |\\n| 16 | \"name\":\"Comment\" |\\n| 17 | } |\\n| 18 | }, |\\n| 19 | \"record_type_categories\":{ |\\n| 20 | \"issue\":{ |\\n| 21 | \"are_record_type_conversions_possible\":true |\\n| 22 | } |\\n| 23 | } |\\n| 24 | } |\\n```\\n\\n[5](/airsync/metadata-extraction#mark-record-types-as-loadable)\\n\\n### Mark record types as loadable\\n\\nThe record types that will be used in a 2-way sync must be marked with `is_loadable`.\\nThis will allow AirSync to load",
"title": "Metadata extraction | DevRev | Docs"
}
] |
7a7aed97-34d9-4a5d-9cff-432cbbadd696
|
enable omnipresent agent experience within the app
|
[
{
"id": "ART-15490_KNOWLEDGE_NODE-3",
"text": "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```\\n\\nTo toggle `searchAgent`, call the following method on any event required:\\n\\n```\\n| |\\n| --- |\\n| window.plugSDK.toggleSearchAgent(); |\\n```\\n\\nTo prefill search input from outside the window,",
"title": "Install Plug search | 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-15490_KNOWLEDGE_NODE-5",
"text": "shared any information.\\n\\nAfter integrating the Plug widget, you can personalize and contextualize customer engagement. Learn how to [identify your customers](/sdks/web/user-identity) and update their information.\\n\\nBind a hotkey to toggle search agent\\n------------------------------------\\n\\nYou can bind the `toggleSearchAgent` method to a hotkey, such as `Cmd + K` (or `Ctrl + K` for Windows), to toggle the search agent. Here\\xe2\\x80\\x99s an example implementation:\\n\\n###### Setup\\n\\n######",
"title": "Install Plug search | 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-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-15498_KNOWLEDGE_NODE-6",
"text": "FooApplication : Application() { |\\n| 4 | |\\n| 5 | override fun onCreate() { |\\n| 6 | super.onCreate() |\\n| 7 | DevRev.configure( |\\n| 8 | context = this, |\\n| 9 | appId = \"<APP_ID>\" |\\n| 10 | ) |\\n| 11 | } |\\n| 12 | } |\\n```\\n\\n1. In the `onCreate` method of your `Application`, configure the DevRev SDK with the required parameters using the credentials obtained earlier.\\n2. Ensure that the custom application is specified in the `AndroidManifest.xml`, as shown below:\\n\\n```\\n| | |\\n| --- |",
"title": "Quickstart guide | 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-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-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-1463_KNOWLEDGE_NODE-3",
"text": "section, generate the necessary credentials for SDK usage. Remember to save both the App ID. and App Secret. as they are required in the SDK configuration.\\n\\nAcquire the Your Unique App ID. (referred to as supportID in the code) by visiting the PLuG Settings. page.\\n\\nInitialization.\\n\\nAfter obtaining the necessary credentials, proceed to configure the DevRev SDK within your application.\\n\\nInitialization of the SDK is accomplished by invoking the configuration method:\\n1 DevRev. configure (",
"title": "Integrate PLuG with your iOS app — 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-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-2894_KNOWLEDGE_NODE-6",
"text": "considered an anonymous user. Anonymous users are the users that come to your site and haven\\xe2\\x80\\x99t yet logged in or shared any information.\\n\\nAfter integrating the PLuG widget, you can personalize and contextualize customer engagement. Learn how to [identify your customers](/public/sdks/web/user-identity) and update their information.\\n\\n## Bind a hotkey to toggle search agent\\n\\nYou can bind the `toggleSearchAgent` method to a hotkey, such as `Cmd + K` (or `Ctrl + K` for Windows), to",
"title": "Install PLuG search — DevRev | Docs"
},
{
"id": "ART-1474_KNOWLEDGE_NODE-6",
"text": "the application should utilize the showSupport API, as shown below:\\n\\n1 DevRev. showSupport (context: Context ) Support button.\\n\\nThe mobile SDK also offers a support button that can be integrated into your application. To include it on the current screen, add the following code to your XML layout:\\n\\n<ai.devrev.sdk..view.FloatingActionButton android:id=\"@+id/_fab\" android:layout_width=\"wrap_content\" android:layout_height=\"wrap_content\" android:layout_margin=\"24dp\"",
"title": "Integrate PLuG with your Android app — DevRev | Docs"
},
{
"id": "ART-15515_KNOWLEDGE_NODE-24",
"text": "method:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | DevRev.showSupport(from:isAnimated:) |\\n```\\n\\n* When a `UIViewController` is passed as the `from` parameter, the screen is shown modally.\\n* When a `UINavigationController` is passed as the `from` parameter, the screen is pushed onto the navigation stack.\\n\\nIf you want to display the support chat screen from the top-most view controller, use the following method:\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | DevRev.showSupport(isAnimated:) |\\n```\\n\\nTo",
"title": "Features | DevRev | Docs"
},
{
"id": "ART-2893_KNOWLEDGE_NODE-1",
"text": "ID\\n\\nYou can access your app ID from your DevRev account by following these steps:\\n\\n 1. In DevRev, go to **Settings > Support > PLuG Settings** via the settings icon in the top-left corner.\\n\\n 2. If the PLuG feature is not already enabled, click **Enable PLuG**.\\n\\n 3. Under the **Configuration** tab, copy the **Unique App ID**.\\n\\n###### Setup\\n\\n###### Setup for React\\n\\nPlace the following code in the `<head>` section of your HTML page:\\n\\n[code]\\n\\n 1| <script \\n ---|--- \\n",
"title": "Install the Web SDK — DevRev | Docs"
}
] |
e80f2dd2-c7d5-496f-9b12-9eee4a8720c9
|
check schema of subtype of a ticket
|
[
{
"id": "ART-1632_KNOWLEDGE_NODE-0",
"text": "b'List Schemas Subtypes | 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)[customization](/beta/api-reference/customization/custom-objects-count)\\n\\nList Schemas Subtypes\\n=====================\\n\\nBeta\\n\\nCopy page\\n\\nGET\\n\\nhttps://api.devrev.ai/schemas.subtypes.list\\n\\nGET\\n\\n/schemas.subtypes.list\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl https://api.devrev.ai/schemas.subtypes.list \\\\",
"title": "List Schemas Subtypes | DevRev | Docs"
},
{
"id": "ART-15332_KNOWLEDGE_NODE-18",
"text": "| \"use_shorthand_notation\": true |\\n| 298 | } |\\n| 299 | } |\\n| 300 | ], |\\n| 301 | \"subtype\": \"string\", |\\n| 302 | \"subtype_display_name\": \"string\" |\\n| 303 | } |\\n| 304 | } |\\n```\\n\\nGets the aggregated schema.\\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\\ncustom\\\\_schema\\\\_fragmentslist of stringsOptional\\n\\nThe custom schema fragment IDs which are to",
"title": "Get Schemas Aggregated (POST) | DevRev | Docs"
},
{
"id": "ART-1614_KNOWLEDGE_NODE-0",
"text": "b'List Schemas Subtypes (POST) | 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)[customization](/beta/api-reference/customization/custom-objects-count)\\n\\nList Schemas Subtypes (POST)\\n============================\\n\\nBeta\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/schemas.subtypes.list\\n\\nPOST\\n\\n/schemas.subtypes.list\\n\\ncURL\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST",
"title": "List Schemas Subtypes (POST) | DevRev | Docs"
},
{
"id": "ART-1819_KNOWLEDGE_NODE-224",
"text": "schemas.subtypes.list\\nLists subtypes.\\nRequest.\\n\\nThis endpoint expects an object.\\nleaf_type string Optional\\nLeaf type for which subtypes are required.\\nleaf_types list of strings Optional\\nList of leaf types for which subtypes are required.\\nResponse.\\n\\nThis endpoint returns an object.\\nsubtypes list of objects\\nList of subtypes.\\nShow 4 properties\\nAPI Reference customization Custom Stages Create.\\n\\nPOST https:// api.devrev.ai / stages.custom.create\\nCreates a custom",
"title": "Sla Trackers Get — DevRev | Docs"
},
{
"id": "ART-1614_KNOWLEDGE_NODE-1",
"text": "https://api.devrev.ai/schemas.subtypes.list \\\\ |\\n| > | -H \"Authorization: Bearer <token>\" \\\\ |\\n| > | -H \"Content-Type: application/json\" \\\\ |\\n| > | -d \\'{}\\' |\\n```\\n\\n[Try it](/beta/api-reference/customization/subtypes-list-post?explorer=true)\\n\\n200Successful\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | { |\\n| 2 | \"subtypes\": [ |\\n| 3 | { |\\n| 4 | \"fragment_id\": \"string\", |\\n| 5 | \"leaf_type\": \"string\", |\\n| 6 | \"value\": \"string\", |\\n| 7 | \"display_name\": \"string\" |\\n| 8 | } |\\n| 9 | ] |\\n| 10 |",
"title": "List Schemas Subtypes (POST) | DevRev | Docs"
},
{
"id": "ART-1637_KNOWLEDGE_NODE-224",
"text": "schemas.subtypes.list\\nLists subtypes.\\nRequest.\\n\\nThis endpoint expects an object.\\nleaf_type string Optional\\nLeaf type for which subtypes are required.\\nleaf_types list of strings Optional\\nList of leaf types for which subtypes are required.\\nResponse.\\n\\nThis endpoint returns an object.\\nsubtypes list of objects\\nList of subtypes.\\nShow 4 properties\\nAPI Reference customization Custom Stages Create.\\n\\nPOST https:// api.devrev.ai / stages.custom.create\\nCreates a custom",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1597_KNOWLEDGE_NODE-224",
"text": "schemas.subtypes.list\\nLists subtypes.\\nRequest.\\n\\nThis endpoint expects an object.\\nleaf_type string Optional\\nLeaf type for which subtypes are required.\\nleaf_types list of strings Optional\\nList of leaf types for which subtypes are required.\\nResponse.\\n\\nThis endpoint returns an object.\\nsubtypes list of objects\\nList of subtypes.\\nShow 4 properties\\nAPI Reference customization Custom Stages Create.\\n\\nPOST https:// api.devrev.ai / stages.custom.create\\nCreates a custom",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1593_KNOWLEDGE_NODE-318",
"text": "subtype \" : \" string \" , 35 \" tags \" : [ 36 { 37 \" tag \" : { 38 \" name \" : \" string \" , 39 \" display_id \" : \" string \" , 40 \" id \" : \" string \" 41 } , 42 \" value \" : \" string \" 43 } 44 ] , 45 \" created_by \" : { 46 \" type \" : \" dev_user \" , 47 \" display_name \" : \" string \" , 48 \" display_picture \" : { 49 \" display_id \" : \" string \" , 50 \" id \" : \" string \" 51 } , 52 \" email \" : \" string \" , 53 \" full_name \" : \" string \" , 54 \" state \" : \" active \" , 55 \" display_id \" : \" string \" , 56 \" id \" : \"",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1509_KNOWLEDGE_NODE-226",
"text": "schemas.subtypes.list\\nLists subtypes.\\nRequest.\\n\\nThis endpoint expects an object.\\nleaf_type string Optional\\nLeaf type for which subtypes are required.\\nleaf_types list of strings Optional\\nList of leaf types for which subtypes are required.\\nResponse.\\n\\nThis endpoint returns an object.\\nsubtypes list of objects\\nList of subtypes.\\nShow 4 properties\\nAPI Reference customization Custom Stages Create.\\n\\nPOST https:// api.devrev.ai / stages.custom.create\\nCreates a custom",
"title": "Prepare — DevRev | Docs"
},
{
"id": "ART-1821_KNOWLEDGE_NODE-224",
"text": "schemas.subtypes.list\\nLists subtypes.\\nRequest.\\n\\nThis endpoint expects an object.\\nleaf_type string Optional\\nLeaf type for which subtypes are required.\\nleaf_types list of strings Optional\\nList of leaf types for which subtypes are required.\\nResponse.\\n\\nThis endpoint returns an object.\\nsubtypes list of objects\\nList of subtypes.\\nShow 4 properties\\nAPI Reference customization Custom Stages Create.\\n\\nPOST https:// api.devrev.ai / stages.custom.create\\nCreates a custom",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1836_KNOWLEDGE_NODE-224",
"text": "schemas.subtypes.list\\nLists subtypes.\\nRequest.\\n\\nThis endpoint expects an object.\\nleaf_type string Optional\\nLeaf type for which subtypes are required.\\nleaf_types list of strings Optional\\nList of leaf types for which subtypes are required.\\nResponse.\\n\\nThis endpoint returns an object.\\nsubtypes list of objects\\nList of subtypes.\\nShow 4 properties\\nAPI Reference customization Custom Stages Create.\\n\\nPOST https:// api.devrev.ai / stages.custom.create\\nCreates a custom",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1591_KNOWLEDGE_NODE-224",
"text": "schemas.subtypes.list\\nLists subtypes.\\nRequest.\\n\\nThis endpoint expects an object.\\nleaf_type string Optional\\nLeaf type for which subtypes are required.\\nleaf_types list of strings Optional\\nList of leaf types for which subtypes are required.\\nResponse.\\n\\nThis endpoint returns an object.\\nsubtypes list of objects\\nList of subtypes.\\nShow 4 properties\\nAPI Reference customization Custom Stages Create.\\n\\nPOST https:// api.devrev.ai / stages.custom.create\\nCreates a custom",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1602_KNOWLEDGE_NODE-2",
"text": "DONs which are to be aggregated.\\n\\ncustom_schema_spec.appslist of stringsOptional\\n\\nList of apps.\\n\\ncustom_schema_spec.subtypestringOptional`format: \"text\"`\\n\\nName of the subtype.\\n\\nis_custom_leaf_typebooleanOptional\\n\\nWhether the leaf type corresponds to a custom object.\\n\\nleaf_typestringOptional`format: \"text\"`\\n\\nThe leaf type. Used for inferring the default stage diagram and tenant fragment ID.\\n\\nstock_schema_fragment_idstringOptional`format: \"id\"`\\n\\nThe stock schema fragment which",
"title": "Get Schemas Aggregated (Beta) — DevRev | Docs"
},
{
"id": "ART-1833_KNOWLEDGE_NODE-448",
"text": "medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the provided types.\\nAllowed values: issue opportunity task ticket\\nResponse.\\n\\nThis endpoint returns",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1790_KNOWLEDGE_NODE-226",
"text": "Optional\\nLeaf type for which subtypes are required.\\nleaf_types string Optional\\nList of leaf types for which subtypes are required.\\nResponse.\\n\\nThis endpoint returns an object.\\nsubtypes list of objects\\nList of subtypes.\\nShow 4 properties\\nAPI Reference customization Subtypes List Post.\\n\\nPOST https:// api.devrev.ai / schemas.subtypes.list\\nLists subtypes.\\nRequest.\\n\\nThis endpoint expects an object.\\nleaf_type string Optional\\nLeaf type for which subtypes are required.\\nleaf_types list",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1305_KNOWLEDGE_NODE-231",
"text": "schemas.subtypes.list\\nLists subtypes.\\nRequest.\\n\\nThis endpoint expects an object.\\nleaf_type string Optional\\nLeaf type for which subtypes are required.\\nleaf_types list of strings Optional\\nList of leaf types for which subtypes are required.\\nResponse.\\n\\nThis endpoint returns an object.\\nsubtypes list of objects\\nList of subtypes.\\nShow 4 properties\\nAPI Reference customization Custom Stages Create.\\n\\nPOST https:// api.devrev.ai / stages.custom.create\\nCreates a custom",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1649_KNOWLEDGE_NODE-224",
"text": "schemas.subtypes.list\\nLists subtypes.\\nRequest.\\n\\nThis endpoint expects an object.\\nleaf_type string Optional\\nLeaf type for which subtypes are required.\\nleaf_types list of strings Optional\\nList of leaf types for which subtypes are required.\\nResponse.\\n\\nThis endpoint returns an object.\\nsubtypes list of objects\\nList of subtypes.\\nShow 4 properties\\nAPI Reference customization Custom Stages Create.\\n\\nPOST https:// api.devrev.ai / stages.custom.create\\nCreates a custom",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1824_KNOWLEDGE_NODE-223",
"text": "Reference customization Subtypes List.\\n\\nGET https:// api.devrev.ai / schemas.subtypes.list\\nLists subtypes.\\nQuery parameters.\\n\\nleaf_type string Optional\\nLeaf type for which subtypes are required.\\nleaf_types string Optional\\nList of leaf types for which subtypes are required.\\nResponse.\\n\\nThis endpoint returns an object.\\nsubtypes list of objects\\nList of subtypes.\\nShow 4 properties\\nAPI Reference customization Subtypes List Post.\\n\\nPOST https:// api.devrev.ai /",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1651_KNOWLEDGE_NODE-223",
"text": "Reference customization Subtypes List.\\n\\nGET https:// api.devrev.ai / schemas.subtypes.list\\nLists subtypes.\\nQuery parameters.\\n\\nleaf_type string Optional\\nLeaf type for which subtypes are required.\\nleaf_types string Optional\\nList of leaf types for which subtypes are required.\\nResponse.\\n\\nThis endpoint returns an object.\\nsubtypes list of objects\\nList of subtypes.\\nShow 4 properties\\nAPI Reference customization Subtypes List Post.\\n\\nPOST https:// api.devrev.ai /",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-15341_KNOWLEDGE_NODE-4",
"text": "them.\\n\\nsubtypelist of stringsOptional\\n\\nThe list of subtypes.\\n\\ntypeslist of stringsOptional\\n\\nFilters for custom schema fragment of the provided types.\\n\\n### Response\\n\\nSuccess.\\n\\nresultlist of objects\\n\\nThe custom schema fragments.\\n\\nShow 1 properties\\n\\nnext\\\\_cursorstring or null`format: \"text\"`\\n\\nThe cursor used to iterate subsequent results in accordance to the\\nsort order. If not set, then no later elements exist.\\n\\nprev\\\\_cursorstring or null`format: \"text\"`\\n\\nThe cursor",
"title": "List Schemas Custom | DevRev | Docs"
},
{
"id": "ART-1805_KNOWLEDGE_NODE-450",
"text": "medium\\nticket.sla_summary.stage enum Optional\\nFilters for records with any of the provided SLA stages.\\nAllowed values: breached completed paused running warning\\nticket.source_channel string Optional\\nFilters for tickets with any of the provided source channels.\\nticket.subtype string Optional\\nFilters for tickets with any of the provided subtypes.\\ntype enum Optional\\nFilters for work of the provided types.\\nAllowed values: issue opportunity task ticket\\nResponse.\\n\\nThis endpoint returns",
"title": "List Post — DevRev | Docs"
}
] |
5e6aa22c-f5bf-414d-8a49-8953a9747d59
|
update ticket tags group stage
|
[
{
"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-1637_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-2040_KNOWLEDGE_NODE-27",
"text": "| \\xe2\\x9c\\x85 | \\xe2\\x9c\\x85 |\\n| Category/Status of Ticket | State/Stage of Ticket | \\xe2\\x9c\\x85 | \\xe2\\x9c\\x85 |\\n| Attachments on Ticket | Attachments on Ticket | \\xe2\\x9c\\x85 | \\xe2\\x9c\\x85 |\\n| Tag on Ticket | Tag on Ticket | \\xe2\\x9c\\x85 | \\xe2\\x9d\\x8c |\\n| Organization | Account | \\xe2\\x9c\\x85 | \\xe2\\x9d\\x8c |\\n| Agent | DevUser | \\xe2\\x9c\\x85 | \\xe2\\x9d\\x8c |\\n| End User | Contact | \\xe2\\x9c\\x85 | \\xe2\\x9d\\x8c |\\n| Chat | Conversation | \\xe2\\x9d\\x8c | \\xe2\\x9d\\x8c |\\n| Conversation |",
"title": "Zendesk AirSync | AirSync | Snap-ins | DevRev"
},
{
"id": "ART-1787_KNOWLEDGE_NODE-105",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1595_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1833_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1593_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1607_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1806_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Self Post — DevRev | Docs"
},
{
"id": "ART-1823_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1782_KNOWLEDGE_NODE-103",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1641_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1649_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1802_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1829_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1830_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1822_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1446_KNOWLEDGE_NODE-9",
"text": "\"stage\": { \\n 92| \"name\": \"foo\" \\n 93| }, \\n 94| \"tags\": [ \\n 95| { \\n 96| \"tag\": { \\n 97| \"display_id\": \"foo\", \\n 98| \"id\": \"foo\", \\n 99| \"name\": \"foo\" \\n 100| }, \\n 101| \"value\": \"foo\" \\n 102| } \\n 103| ], \\n 104| \"target_close_date\": \"2023-01-01T12:00:00.000Z\", \\n 105| \"title\": \"foo\", \\n 106| \"developed_with\": [ \\n 107| { \\n",
"title": "Update Work — DevRev | Docs"
},
{
"id": "ART-1819_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Sla Trackers Get — DevRev | Docs"
},
{
"id": "ART-1305_KNOWLEDGE_NODE-108",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1592_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1825_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1303_KNOWLEDGE_NODE-106",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Export Post — DevRev | Docs"
},
{
"id": "ART-1651_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1824_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1591_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1836_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1827_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1654_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1801_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1818_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Sla Trackers Get Post — DevRev | Docs"
},
{
"id": "ART-1837_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1509_KNOWLEDGE_NODE-103",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Prepare — DevRev | Docs"
},
{
"id": "ART-1588_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1609_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1575_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1633_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "List — DevRev | Docs"
},
{
"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-1579_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1590_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1650_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1831_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1784_KNOWLEDGE_NODE-103",
"text": "the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow property\\ntitle string Optional\\nThe updated title of the conversation.\\nuser_sessions object Optional\\nShow property\\nResponse.\\n\\nThis",
"title": "Locate Post — DevRev | Docs"
},
{
"id": "ART-1653_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1597_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-4133_KNOWLEDGE_NODE-19",
"text": "validations options when updating the stage or\\nthe stage diagram of an incident.\\n\\nAllowed values:allow\\\\_invalid\\\\_transition\\n\\nstaged\\\\_infoobjectOptional\\n\\nUpdate object for StagedInfo.\\n\\nShow 4 properties\\n\\nsync\\\\_metadataobjectOptional\\n\\nShow 4 properties\\n\\ntagsobjectOptional\\n\\nShow 1 properties\\n\\ntarget\\\\_close\\\\_datestringOptional`format: \"date-time\"`\\n\\nTimestamp when the incident is expected to be resolved.\\n\\ntitlestringOptional`format: \"text\"`\\n\\nTitle of the",
"title": "Update Incident | DevRev | Docs"
},
{
"id": "ART-1835_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1655_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1834_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1306_KNOWLEDGE_NODE-106",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1639_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Export Post — DevRev | Docs"
},
{
"id": "ART-1652_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1805_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1605_KNOWLEDGE_NODE-101",
"text": "conversation to update.\\napplies_to_parts object Optional\\nShow property\\ndescription string Optional\\nThe updated description for the conversation.\\ngroup string Optional\\nThe group that the conversation is associated with.\\nis_spam boolean Optional\\nWhether the conversation is spam.\\nmetadata object Optional\\nShow property\\nstage object Optional\\nUpdates an object\\'s stage.\\nShow 2 properties\\nstatus string Optional\\nThe updated status of the conversation.\\ntags object Optional\\nShow",
"title": "Create — DevRev | Docs"
}
] |
129b4dcf-9d29-4b30-b8eb-044171daf2a6
|
how to become a partner of DevRev
|
[
{
"id": "ART-15615_KNOWLEDGE_NODE-4",
"text": "dedicated partner support to accelerate growth. Additionally, partners benefit from co-marketing opportunities, shared resources, and collaboration with DevRev to expand market reach and build sustainable business value. For detailed information, please contact [partnerships@devrev.ai](mailto:partnerships@devrev.ai)\\n\\nApplication & Onboarding\\n\\nQ: How do I apply to become a DevRev partner?\\n\\nA: The DevRev Partner Program is currently by invite only. If you are interested in becoming a",
"title": "Partner FAQs"
},
{
"id": "ART-15615_KNOWLEDGE_NODE-5",
"text": "partner, please fill out the application form located on the DevRev Partners page ([https://devrev.ai/partners](https://devrev.ai/partners)). Our partner team will review your submission and contact you if there is a fit. For any questions or to express your interest directly, email [partnerships@devrev.ai](mailto:partnerships@devrev.ai)\\n\\nQ: What is the onboarding process for new partners?\\n\\nA: Once your application is accepted, you will participate in a structured onboarding process that",
"title": "Partner FAQs"
},
{
"id": "ART-15615_KNOWLEDGE_NODE-1",
"text": "Programs are designed for organizations seeking to collaborate with DevRev by delivering services, integrations, or solutions powered by our platform. Partners receive access to resources, technical enablement, and business support to drive shared growth. For more information, contact [partnerships@devrev.ai](mailto:partnerships@devrev.ai)\\n\\nQ: Who is eligible to join the DevRev Partner Program?\\n\\nA: The DevRev Partner Program welcomes a wide range of organizations, including cloud providers,",
"title": "Partner FAQs"
},
{
"id": "ART-15615_KNOWLEDGE_NODE-0",
"text": "b'Program Basics\\n\\nQ: Do you have a partner program?\\n\\nA: Yes! DevRev offers a comprehensive Partner Program designed for organizations interested in collaborating on services, integrations, or go-to-market initiatives. To learn more or explore partnership opportunities, please reach out to us at [partnerships@devrev.ai](mailto:partnerships@devrev.ai) or visit us at [https://devrev.ai/partners](https://devrev.ai/partners)\\n\\nQ: What is the DevRev Partner Program?\\n\\nA: The DevRev Partner",
"title": "Partner FAQs"
},
{
"id": "ART-15615_KNOWLEDGE_NODE-3",
"text": "reviewed by our partner team to ensure strong alignment and shared success.For more information, contact [partnerships@devrev.ai](mailto:partnerships@devrev.ai)\\n\\nQ: What are the core benefits of joining the program?\\n\\nA: Partners in the DevRev Partner Programs gain access to exclusive commission rates and financial incentives, including potential marketing funds to support joint campaigns and demand generation. The program also offers comprehensive technical enablement, training, and",
"title": "Partner FAQs"
},
{
"id": "ART-15615_KNOWLEDGE_NODE-14",
"text": "contact: Prospective partners can email [partnerships@devrev.ai](mailto:partnerships@devrev.ai) for any inquiries or support needs.\\n\\nAfter onboarding or once a partnership is established: Each partner is assigned a dedicated partner manager who serves as the primary point of contact for ongoing support and issue resolution.\\n\\nPartner Portal: Onboarded partners gain access to the DevRev Partner Portal, where they can raise support tickets, track requests, and access resources at any",
"title": "Partner FAQs"
},
{
"id": "ART-15615_KNOWLEDGE_NODE-9",
"text": "implementation, and customer success activities. The program also fosters collaboration and resource sharing, helping partners expand their market reach and drive sustainable business growth. For tailored support, partners can reach out to the Partner Support team at [partnerships@devrev.ai](mailto:partnerships@devrev.ai)\\n\\nQ: Can partners collaborate with DevRev on product development or integrations?\\n\\nA: Yes, DevRev partners can collaborate on building integrations, developing solutions,",
"title": "Partner FAQs"
},
{
"id": "ART-15615_KNOWLEDGE_NODE-8",
"text": "models or to discuss your organization\\xe2\\x80\\x99s fit, contact [partnerships@devrev.ai](mailto:partnerships@devrev.ai)\\n\\nQ: How does DevRev support partners in growing their business?\\n\\nA: DevRev supports partners by providing access to exclusive financial incentives, comprehensive technical enablement, and ongoing training to ensure partners are equipped for success. Partners benefit from joint go-to-market initiatives, co-marketing opportunities, and dedicated support for pre-sales,",
"title": "Partner FAQs"
},
{
"id": "ART-15615_KNOWLEDGE_NODE-7",
"text": "[partnerships@devrev.ai](mailto:partnerships@devrev.ai)Program Structure & Collaboration\\n\\nQ: What types of partnerships does DevRev offer?\\n\\nA: DevRev offers a range of partnership models, including referral and reselling partnerships, as well as opportunities for organizations focused on services, integrations, consulting, or joint go-to-market initiatives. Each partnership is structured to support mutual growth, market expansion, and business success. For details on available partnership",
"title": "Partner FAQs"
},
{
"id": "ART-15615_KNOWLEDGE_NODE-19",
"text": "region, please contact [partnerships@devrev.ai](mailto:partnerships@devrev.ai).We maintain an updated directory and can facilitate introductions as needed.\\n\\nQ: Where can I find more information or get in touch?A: For more information or to discuss partnership opportunities, visit the DevRev Partners page or contact [partnerships@devrev.ai](mailto:partnerships@devrev.ai).Note: For the most up-to-date information and specific inquiries, always refer to the official DevRev Partners page or",
"title": "Partner FAQs"
},
{
"id": "ART-15615_KNOWLEDGE_NODE-10",
"text": "and delivering services that leverage our platform. We work closely with select partners to co-create offerings, support implementation, and drive innovation for mutual growth. For partnership opportunities related to product development or integrations, please contact [partnerships@devrev.ai](mailto:partnerships@devrev.ai)Revenue & Incentives\\n\\nQ: What commission rates or incentives are available to partners?\\n\\nA: Commission rates and incentives are designed based on partner\\xe2\\x80\\x99s &",
"title": "Partner FAQs"
},
{
"id": "ART-15615_KNOWLEDGE_NODE-11",
"text": "its engagement type. These details are discussed individually with partners after onboarding and once mutual fit and partnership terms are established. For more information, please contact [partnerships@devrev.ai](mailto:partnerships@devrev.ai)\\n\\nQ: How are commissions and incentives tracked and paid out?\\n\\nA:Commissions and incentives are tracked using dedicated dashboards and regular partner updates. Payouts are processed according to the terms agreed upon during onboarding and are",
"title": "Partner FAQs"
},
{
"id": "ART-1480_KNOWLEDGE_NODE-7",
"text": "DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram",
"title": "Commands — DevRev | Docs"
},
{
"id": "ART-13013_KNOWLEDGE_NODE-8",
"text": "DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram",
"title": "Get Org Schedule Fragment — DevRev | Docs"
},
{
"id": "ART-1673_KNOWLEDGE_NODE-9",
"text": "DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram",
"title": "List States Custom (POST) (Beta) — DevRev | Docs"
},
{
"id": "ART-4071_KNOWLEDGE_NODE-27",
"text": "[Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Create Conversation — DevRev | Docs"
},
{
"id": "ART-2894_KNOWLEDGE_NODE-11",
"text": "[Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Install PLuG search — DevRev | Docs"
},
{
"id": "ART-12462_KNOWLEDGE_NODE-4",
"text": "[Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Troubleshooting — DevRev | Docs"
},
{
"id": "ART-1367_KNOWLEDGE_NODE-6",
"text": "[Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Pagination — DevRev | Docs"
},
{
"id": "ART-1405_KNOWLEDGE_NODE-11",
"text": "DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram",
"title": "Update Part — DevRev | Docs"
},
{
"id": "ART-13045_KNOWLEDGE_NODE-10",
"text": "DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram",
"title": "Get Web Crawler Job — DevRev | Docs"
},
{
"id": "ART-4087_KNOWLEDGE_NODE-9",
"text": "DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram",
"title": "Update Group — DevRev | Docs"
},
{
"id": "ART-4169_KNOWLEDGE_NODE-8",
"text": "Atomicwork\\n\\n### Join DevRev\\xe2\\x80\\x99s global partner network of 100+ VCs, accelerators, incubators, angel investors, and startup communities across 87 countries.\\n\\n![]()\\n\\n![]()\\n\\n![]()\\n\\n![]()\\n\\n![]()\\n\\n![]()\\n\\n![]()\\n\\n![]()\\n\\n![]()\\n\\n![]()\\n\\n![]()\\n\\n![]()\\n\\n![]()\\n\\n![]()\\n\\n![]()\\n\\n![]()\\n\\n[Become a DevRev Partner](/startups/vc)\\n\\nDevRev for StartupsExplore Startup PerksFuel your startup journey with curated startup offers\\n\\n[Discover Perks](/startups/perks)\\n\\nLEARNING",
"title": "DevRev For Startups"
},
{
"id": "ART-2644_KNOWLEDGE_NODE-12",
"text": "DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram",
"title": "Get Custom Object (POST) (Beta) — DevRev | Docs"
},
{
"id": "ART-12969_KNOWLEDGE_NODE-6",
"text": "DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram",
"title": "Info Auth Tokens — DevRev | Docs"
},
{
"id": "ART-1391_KNOWLEDGE_NODE-6",
"text": "DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram",
"title": "Delete Auth Token — DevRev | Docs"
},
{
"id": "ART-13008_KNOWLEDGE_NODE-8",
"text": "DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram",
"title": "Count Meetings (POST) — DevRev | Docs"
},
{
"id": "ART-13034_KNOWLEDGE_NODE-6",
"text": "DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram",
"title": "Create Snap Widget — DevRev | Docs"
},
{
"id": "ART-2712_KNOWLEDGE_NODE-11",
"text": "DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram",
"title": "Create SLA — DevRev | Docs"
},
{
"id": "ART-12586_KNOWLEDGE_NODE-10",
"text": "[The Book of DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](/partners)\\n * [Startup Program](/startups)\\n\\nCompany\\n\\n * [About](/about)\\n * [People](/people)\\n * [Careers](/careers)\\n * [Places](/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium ](https://medium.com/devrev)\\n * [Linkedin",
"title": "DevRev Careers | SEO Content Marketer"
},
{
"id": "ART-1489_KNOWLEDGE_NODE-15",
"text": "DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram",
"title": "Upgrade snap-ins — DevRev | Docs"
},
{
"id": "ART-1442_KNOWLEDGE_NODE-21",
"text": "DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram",
"title": "Get Work — DevRev | Docs"
},
{
"id": "ART-12988_KNOWLEDGE_NODE-7",
"text": "DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram",
"title": "Get Dev Org — DevRev | Docs"
},
{
"id": "ART-4076_KNOWLEDGE_NODE-30",
"text": "DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram",
"title": "List Conversations (POST) — DevRev | Docs"
},
{
"id": "ART-4099_KNOWLEDGE_NODE-11",
"text": "DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram",
"title": "Get Rev User (POST) — DevRev | Docs"
},
{
"id": "ART-13042_KNOWLEDGE_NODE-13",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Update Survey — DevRev | Docs"
},
{
"id": "ART-1407_KNOWLEDGE_NODE-11",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Create Rev Org — DevRev | Docs"
},
{
"id": "ART-1610_KNOWLEDGE_NODE-14",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Get Schemas Stock (POST) (Beta) — DevRev | Docs"
},
{
"id": "ART-12456_KNOWLEDGE_NODE-31",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Features — DevRev | Docs"
},
{
"id": "ART-12978_KNOWLEDGE_NODE-10",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Get Code Change (POST) — DevRev | Docs"
},
{
"id": "ART-13047_KNOWLEDGE_NODE-11",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "List Web Crawler Jobs — DevRev | Docs"
},
{
"id": "ART-1675_KNOWLEDGE_NODE-9",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "List Stages Custom (Beta) — DevRev | Docs"
},
{
"id": "ART-1370_KNOWLEDGE_NODE-8",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "List Artifacts (POST) — DevRev | Docs"
},
{
"id": "ART-12448_KNOWLEDGE_NODE-6",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Migration guide — DevRev | Docs"
},
{
"id": "ART-4084_KNOWLEDGE_NODE-8",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "List Groups Members — DevRev | Docs"
},
{
"id": "ART-2633_KNOWLEDGE_NODE-14",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "List SLA Trackers — DevRev | Docs"
},
{
"id": "ART-4085_KNOWLEDGE_NODE-10",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "List Groups Members (POST) — DevRev | Docs"
},
{
"id": "ART-4072_KNOWLEDGE_NODE-6",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Delete Conversation — DevRev | Docs"
},
{
"id": "ART-2639_KNOWLEDGE_NODE-12",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Get Custom Object (Beta) — DevRev | Docs"
},
{
"id": "ART-4063_KNOWLEDGE_NODE-15",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Event Webhooks — DevRev | Docs"
},
{
"id": "ART-4225_KNOWLEDGE_NODE-13",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "List Surveys Responses — DevRev | Docs"
},
{
"id": "ART-12451_KNOWLEDGE_NODE-6",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Troubleshooting — DevRev | Docs"
},
{
"id": "ART-2642_KNOWLEDGE_NODE-6",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Delete Custom Object (Beta) — DevRev | Docs"
},
{
"id": "ART-4066_KNOWLEDGE_NODE-14",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Get Article — DevRev | Docs"
},
{
"id": "ART-1494_KNOWLEDGE_NODE-18",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Hooks — DevRev | Docs"
},
{
"id": "ART-1433_KNOWLEDGE_NODE-5",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Delete Timeline Entry — DevRev | Docs"
},
{
"id": "ART-4057_KNOWLEDGE_NODE-7",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "List Dev Orgs Auth Connections (POST) — DevRev | Docs"
},
{
"id": "ART-13006_KNOWLEDGE_NODE-12",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Create Meeting — DevRev | Docs"
},
{
"id": "ART-12968_KNOWLEDGE_NODE-10",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Update Metric Definition — DevRev | Docs"
},
{
"id": "ART-13014_KNOWLEDGE_NODE-12",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "List Meetings (POST) — DevRev | Docs"
},
{
"id": "ART-4104_KNOWLEDGE_NODE-11",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Get Service Account (POST) — DevRev | Docs"
},
{
"id": "ART-2714_KNOWLEDGE_NODE-9",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Get SLA (POST) — DevRev | Docs"
},
{
"id": "ART-13002_KNOWLEDGE_NODE-12",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Update Directory — DevRev | Docs"
},
{
"id": "ART-1403_KNOWLEDGE_NODE-11",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Self Dev User — DevRev | Docs"
},
{
"id": "ART-4077_KNOWLEDGE_NODE-28",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Update Conversation — DevRev | Docs"
},
{
"id": "ART-2893_KNOWLEDGE_NODE-9",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Install the Web SDK — DevRev | Docs"
},
{
"id": "ART-1467_KNOWLEDGE_NODE-5",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Service level agreement — DevRev | Docs"
},
{
"id": "ART-13003_KNOWLEDGE_NODE-11",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Get Directory (POST) — DevRev | Docs"
},
{
"id": "ART-1364_KNOWLEDGE_NODE-8",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Errors — DevRev | Docs"
},
{
"id": "ART-13016_KNOWLEDGE_NODE-10",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Create Org Schedule Fragment — DevRev | Docs"
},
{
"id": "ART-1384_KNOWLEDGE_NODE-10",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Create Auth Token — DevRev | Docs"
},
{
"id": "ART-12452_KNOWLEDGE_NODE-9",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Migration guide — DevRev | Docs"
},
{
"id": "ART-1679_KNOWLEDGE_NODE-10",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "List States Custom (Beta) — DevRev | Docs"
},
{
"id": "ART-1443_KNOWLEDGE_NODE-8",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Get Webhook (POST) — DevRev | Docs"
},
{
"id": "ART-1622_KNOWLEDGE_NODE-14",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Get Schemas Aggregated (POST) (Beta) — DevRev | Docs"
},
{
"id": "ART-1477_KNOWLEDGE_NODE-22",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Snap-in V1 manifest — DevRev | Docs"
},
{
"id": "ART-13011_KNOWLEDGE_NODE-10",
"text": "* [Events](https://devrev.ai/events)\\n * [News](https://devrev.ai/blog?category=news)\\n * [Case Studies](https://devrev.ai/case-study)\\n * [Documentation](https://docs.devrev.ai/)\\n * [API Reference](https://docs.devrev.ai/api/)\\n * [The Book of DevRev](https://thebook.devrev.ai/)\\n * [Partner Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n *",
"title": "Update Meeting — DevRev | Docs"
},
{
"id": "ART-12985_KNOWLEDGE_NODE-11",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "Get Command (POST) — DevRev | Docs"
},
{
"id": "ART-1366_KNOWLEDGE_NODE-8",
"text": "Program](https://devrev.ai/partners)\\n * [Startup Program](https://devrev.ai/startups)\\n\\nCompany\\n\\n * [About](https://devrev.ai/about)\\n * [People](https://devrev.ai/people)\\n * [Careers](https://devrev.ai/careers)\\n * [Places](https://devrev.ai/places)\\n * [Invest](https://revd.devrev.ai/)\\n * [What Why How](https://devrev.ai/what-why-how)\\n\\nConnect\\n\\n * [Contact ](mailto:humansofdevrev@devrev.ai)\\n * [Instagram ](https://www.instagram.com/devrev)\\n * [Medium",
"title": "For Developers — DevRev | Docs"
}
] |
472c4905-eb02-44bc-be71-eef5496d99ad
|
update multiple tickets status in DevRev without going through individually
|
[
{
"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"
},
{
"id": "ART-1821_KNOWLEDGE_NODE-470",
"text": "Reference works Update.\\n\\nPOST https:// api.devrev.ai / works.update\\nUpdates a work item\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\nIssue Show 21 properties\\nOR\\nNone Show 17 properties\\nOR\\nOpportunity Show 21 properties\\nOR\\nTask Show 19 properties\\nOR\\nTicket Show 25 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nwork object\\nShow 4 variants\\nBuilt with'",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1788_KNOWLEDGE_NODE-469",
"text": "Reference works Update.\\n\\nPOST https:// api.devrev.ai / works.update\\nUpdates a work item\\'s information.\\nRequest.\\n\\nThis endpoint expects an object.\\nIssue Show 21 properties\\nOR\\nNone Show 17 properties\\nOR\\nOpportunity Show 21 properties\\nOR\\nTask Show 19 properties\\nOR\\nTicket Show 25 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nwork object\\nShow 4 variants\\nBuilt with'",
"title": "Get Post — DevRev | Docs"
},
{
"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"
}
] |
2558f7d0-edf0-4e7a-a7bb-5201b93aeac8
|
auto-assign tickets to available agents
|
[
{
"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-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"
},
{
"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-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"
}
] |
745722d9-8013-46da-ad99-4e39b0b10542
|
build snap-kit based widgets on plug
|
[
{
"id": "ART-1484_KNOWLEDGE_NODE-3",
"text": "elements for creating custom user interface using snap-kit.\\n\\n## Structure\\n\\nThe snap-kit JSON has a top-level structure with `object`, `body`, `type`, and `snap_kit_body` fields. The `snap_kit_body` field contains information regarding snap-kit\\xe2\\x80\\x99s structure.\\n\\nThe `snap_kit_body` field has the following properties:\\n\\n * `snap_in_id`: A unique identifier for the snap-kit.\\n * `snap_in_action_name`: The name of the action this snap-kit represents.\\n * `body`: An object that",
"title": "Snapkit — DevRev | Docs"
},
{
"id": "ART-15522_KNOWLEDGE_NODE-1",
"text": "Components\\n===============\\n\\nCopy page\\n\\nSnap components enable adding custom UI components defined by snap-kit to the DevRev UI.\\nThese components can be used to display data or interact with the user.\\nSnap components are defined in the snap-in manifest file. DevRev UI renders these components based on the defined configuration.\\n\\nEach snap-component has the following properties:\\n\\n* `surface` : The surface where the snap component can be displayed.\\n* `snap_kit_action_name` : The name",
"title": "Snap Components | DevRev | Docs"
},
{
"id": "ART-1290_KNOWLEDGE_NODE-2",
"text": "interface using snap-kit.\\n\\nStructure\\n---------\\n\\nThe snap-kit JSON has a top-level structure with `object`, `body`, `type`, and `snap_kit_body` fields. The `snap_kit_body` field contains information regarding snap-kit\\xe2\\x80\\x99s structure.\\n\\nThe `snap_kit_body` field has the following properties:\\n\\n* `snap_in_id`: A unique identifier for the snap-kit.\\n* `snap_in_action_name`: The name of the action this snap-kit represents.\\n* `body`: An object that holds the actual snap-kit content in",
"title": "Snapkit | DevRev | Docs"
},
{
"id": "ART-2814_KNOWLEDGE_NODE-2",
"text": "development](/public/snapin-development/concepts)[References](/public/snapin-development/references/cli-install)\\n\\n#\\n\\nSnap Components\\n\\nSnap components enable adding custom UI components defined by snap-kit to the DevRev UI. These components can be used to display data or interact with the user. Snap components are defined in the snap-in manifest file. DevRev UI renders these components based on the defined configuration.\\n\\nEach snap-component has the following properties:\\n\\n * `surface`",
"title": "Snap Components — DevRev | Docs"
},
{
"id": "ART-13034_KNOWLEDGE_NODE-2",
"text": "the snap widget is shared with.\\n\\nShow 2 properties\\n\\n### Response\\n\\nSuccess.\\n\\nsnap_widgetobject\\n\\nShow property\\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/snap-widgets.create\\n\\n[code]\\n\\n $| curl -X POST https://api.devrev.ai/snap-widgets.create \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer <token>\" \\\\ \\n",
"title": "Create Snap Widget — DevRev | Docs"
},
{
"id": "ART-15458_KNOWLEDGE_NODE-0",
"text": "b'Create Snap Widget | DevRev | Docs\\n\\n[![]()![]()](https://developer.devrev.ai/)\\n\\nPublic\\n\\nPublic\\n\\nSearch\\n\\n`/`\\n\\n[API Reference](/api-reference/getting-started)[snap-widgets](/api-reference/snap-widgets/create)\\n\\nCreate Snap Widget\\n==================\\n\\nCopy page\\n\\nPOST\\n\\nhttps://api.devrev.ai/snap-widgets.create\\n\\nPOST\\n\\n/snap-widgets.create\\n\\n```\\n| | |\\n| --- | --- |\\n| $ | curl -X POST https://api.devrev.ai/snap-widgets.create \\\\ |\\n| > | -H \"Authorization: Bearer <token>\"",
"title": "Create Snap Widget | DevRev | Docs"
},
{
"id": "ART-1846_KNOWLEDGE_NODE-7",
"text": "organization and user. It is called when the configuration page is first loaded.\\n* `snap_in_configuration_handler`: This function processes the user and organization configuration options. It is triggered when actions are performed on the organization or user configuration snap-kit.\\n\\nConfiguration functions\\n-----------------------\\n\\nThe configuration functions should return a valid snap-kit JSON that defines the layout and elements of the custom configuration page. Here\\xe2\\x80\\x99s an",
"title": "Customizing snap-in configuration | DevRev | Docs"
},
{
"id": "ART-1558_KNOWLEDGE_NODE-442",
"text": "ID of the snap-in to update.\\n\\ninputs_values map from strings to any Optional\\n\\nThe updated values of the inputs.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nsnap_in object\\nShow 7 properties\\nAPI Reference snap-widgets Create.\\n\\nPOST https://api.devrev.ai / snap-widgets.create\\n\\nCreate a snap widget object.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nEmail Preview\\n\\nAn email preview widget.\\n\\nShow 19 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nsnap_widget",
"title": "Metric Definitions List (Beta) — DevRev | Docs"
},
{
"id": "ART-1560_KNOWLEDGE_NODE-445",
"text": "ID of the snap-in to update.\\n\\ninputs_values map from strings to any Optional\\n\\nThe updated values of the inputs.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nsnap_in object\\nShow 7 properties\\nAPI Reference snap-widgets Create.\\n\\nPOST https://api.devrev.ai / snap-widgets.create\\n\\nCreate a snap widget object.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nEmail Preview\\n\\nAn email preview widget.\\n\\nShow 19 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nsnap_widget",
"title": "Assign (Beta) — DevRev | Docs"
},
{
"id": "ART-1566_KNOWLEDGE_NODE-445",
"text": "ID of the snap-in to update.\\n\\ninputs_values map from strings to any Optional\\n\\nThe updated values of the inputs.\\n\\nResponse.\\n\\nThis endpoint returns an object.\\nsnap_in object\\nShow 7 properties\\nAPI Reference snap-widgets Create.\\n\\nPOST https://api.devrev.ai / snap-widgets.create\\n\\nCreate a snap widget object.\\n\\nRequest.\\n\\nThis endpoint expects an object.\\nEmail Preview\\n\\nAn email preview widget.\\n\\nShow 19 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nsnap_widget",
"title": "Transition (Beta) — DevRev | Docs"
},
{
"id": "ART-1640_KNOWLEDGE_NODE-1",
"text": "Response\\n\\nSuccess.\\n\\nsnap_widgetobject\\n\\nShow 2 variants\\n\\nPOST\\n\\n/snap-widgets.create\\n\\ncURL\\n\\n[code]\\n\\n $| curl -X POST https://api.devrev.ai/snap-widgets.create \\\\ \\n ---|--- \\n >| -H \"Authorization: Bearer <token>\" \\\\ \\n >| -H \"Content-Type: application/json\" \\\\ \\n >| -d \\'{ \\n >| \"type\": \"email_preview\", \\n >| \"name\": \"name\" \\n >| }\\'\\n[/code] \\n \\nTry it\\n\\n201Created\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2|",
"title": "Create Snap Widget (Beta) — DevRev | Docs"
},
{
"id": "ART-1484_KNOWLEDGE_NODE-192",
"text": "button](/public/snapin-development/references/snapkit#toggle-button)\\n * [Upload input](/public/snapin-development/references/snapkit#upload-input)\\n\\n_Example_\\n\\n[code]\\n\\n 1| { \\n ---|--- \\n 2| \"action_id\": \"user_form\", \\n 3| \"alignment\": \"end\", \\n 4| \"direction\": \"row\", \\n 5| \"elements\": [ \\n 6| { \\n 7| \"element\": { \\n 8| \"action_id\": \"name\", \\n 9| \"min_length\": 10, \\n 10| \"placeholder\": { \\n 11|",
"title": "Snapkit — DevRev | Docs"
},
{
"id": "ART-15522_KNOWLEDGE_NODE-4",
"text": "snap_kit_body: |\\n| 17 | { |\\n| 18 | \"snaps\":[] |\\n| 19 | } |\\n```\\n\\nFormat of context passed to snap-kit action\\n-------------------------------------------\\n\\n```\\n| | |\\n| --- | --- |\\n| 1 | // The payload contains details and values of the snap-kit from which the action was invoked. |\\n| 2 | interface Payload { |\\n| 3 | action: { |\\n| 4 | block_id: string; |\\n| 5 | id: string; |\\n| 6 | timestamp: number; |\\n| 7 | type: string; |\\n| 8 | value: string; |\\n| 9 | }; |\\n| 10 | action_id:",
"title": "Snap Components | DevRev | Docs"
},
{
"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-1607_KNOWLEDGE_NODE-393",
"text": "snap-in to update.\\ninputs_values map from strings to any Optional\\nThe updated values of the inputs.\\nResponse.\\n\\nThis endpoint returns an object.\\nsnap_in object\\nShow 7 properties\\nAPI Reference snap-widgets Create.\\n\\nPOST https:// api.devrev.ai / snap-widgets.create\\nCreate a snap widget object.\\nRequest.\\n\\nThis endpoint expects an object.\\nEmail Preview Show 19 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nsnap_widget object\\nShow variant\\nAPI Reference surveys",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1588_KNOWLEDGE_NODE-393",
"text": "snap-in to update.\\ninputs_values map from strings to any Optional\\nThe updated values of the inputs.\\nResponse.\\n\\nThis endpoint returns an object.\\nsnap_in object\\nShow 7 properties\\nAPI Reference snap-widgets Create.\\n\\nPOST https:// api.devrev.ai / snap-widgets.create\\nCreate a snap widget object.\\nRequest.\\n\\nThis endpoint expects an object.\\nEmail Preview Show 19 properties\\nResponse.\\n\\nThis endpoint returns an object.\\nsnap_widget object\\nShow variant\\nAPI Reference surveys",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1290_KNOWLEDGE_NODE-191",
"text": "\"remote\", |\\n| 4 | \"type\": \"user_picker\", |\\n| 5 | \"value\": [\"don:identity:dvrv-us-1:devo/H66a8LUt:devu/5\"], |\\n| 6 | \"timestamp\": \"2023-07-12T08:32:15.001Z\" |\\n| 7 | } |\\n```\\n\\nExample snap-kit\\n----------------\\n\\nIn this updated JSON, the `divider` component is added to create a visual separation. The `checkboxes` component allows for selecting multiple options. The `part_picker` component allows for selecting parts, and the `tag_picker` component allows for selecting tags. You can",
"title": "Snapkit | DevRev | Docs"
}
] |
03b9886d-c7f4-4786-a830-4abcbc7860ab
|
find issues assigned to particular team member
|
[
{
"id": "ART-1244_KNOWLEDGE_NODE-17",
"text": "stringsOptional\\n\\nFilters for issues with any of the provided Rev organizations.\\n\\nissue.sla\\\\_summary.stagelist of enumsOptional\\n\\nFilters for records with any of the provided SLA stages.\\n\\nAllowed values:breachedcompletedpausedrunningwarning\\n\\nissue.sprintlist of stringsOptional\\n\\nFilters for issues with any of the sprint.\\n\\nmodified\\\\_bylist of stringsOptional\\n\\nFilters for work modified by any of these users.\\n\\nowned\\\\_bylist of stringsOptional\\n\\nFilters for work owned by any of",
"title": "Export Works | DevRev | Docs"
},
{
"id": "ART-1994_KNOWLEDGE_NODE-38",
"text": "To help visualize sprint progress by viewing scope change over time and changes in work remaining over time. A line represents total incomplete issues over time as well as a specific line to represent how much work is left on issues directly linked to customer asks.\\n* **Filters for focused analysis and retrospection**: Ability to apply filters at the top of the page for **Part**, **Owner**, and **Priority**. This enhanced feature provides you with greater control and flexibility when analyzing",
"title": "Sprint mode | Computer for Builders | DevRev"
},
{
"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-1832_KNOWLEDGE_NODE-451",
"text": "any of the sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1838_KNOWLEDGE_NODE-444",
"text": "Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string Optional\\nFilters for work reported by",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1994_KNOWLEDGE_NODE-35",
"text": "the workspace can view the sprint board in **Sprint Boards** even if it's not exclusively shared with you. You can pin the sprint board for easy access and share the URL too which is under **Share** > **Copy Link**. To grant write permission, click **Share** and enter the email or name of the person.\\n\\n![]()\\n\\n* You can go to **Settings** on the left of the **Insights** button on top to change **Duration** of the sprint and **Define backlog** by adding issue filters like **Part, Owner, Tags,",
"title": "Sprint mode | Computer for Builders | DevRev"
},
{
"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-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-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-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-1304_KNOWLEDGE_NODE-447",
"text": "sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1779_KNOWLEDGE_NODE-444",
"text": "sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1785_KNOWLEDGE_NODE-442",
"text": "sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1302_KNOWLEDGE_NODE-448",
"text": "sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string",
"title": "Export — DevRev | Docs"
},
{
"id": "ART-1792_KNOWLEDGE_NODE-446",
"text": "sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1819_KNOWLEDGE_NODE-446",
"text": "sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string",
"title": "Sla Trackers Get — DevRev | Docs"
},
{
"id": "ART-1806_KNOWLEDGE_NODE-448",
"text": "sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string",
"title": "Self Post — DevRev | Docs"
},
{
"id": "ART-1804_KNOWLEDGE_NODE-448",
"text": "sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string",
"title": "Self — DevRev | Docs"
},
{
"id": "ART-1592_KNOWLEDGE_NODE-445",
"text": "sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1786_KNOWLEDGE_NODE-443",
"text": "sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1783_KNOWLEDGE_NODE-442",
"text": "sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string",
"title": "Locate — DevRev | Docs"
},
{
"id": "ART-1784_KNOWLEDGE_NODE-442",
"text": "sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string",
"title": "Locate Post — DevRev | Docs"
},
{
"id": "ART-1802_KNOWLEDGE_NODE-448",
"text": "sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1790_KNOWLEDGE_NODE-443",
"text": "sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string",
"title": "List Post — DevRev | Docs"
},
{
"id": "ART-1308_KNOWLEDGE_NODE-445",
"text": "sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1301_KNOWLEDGE_NODE-448",
"text": "sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1605_KNOWLEDGE_NODE-444",
"text": "sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string",
"title": "Create — DevRev | Docs"
},
{
"id": "ART-1780_KNOWLEDGE_NODE-443",
"text": "sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string Optional\\nFilters for work owned by any of these users.\\nreported_by string",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1825_KNOWLEDGE_NODE-442",
"text": "warning\\nissue.sprint string Optional\\nFilters for issues with any of the sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1655_KNOWLEDGE_NODE-440",
"text": "warning\\nissue.sprint string Optional\\nFilters for issues with any of the sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1653_KNOWLEDGE_NODE-440",
"text": "warning\\nissue.sprint string Optional\\nFilters for issues with any of the sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1641_KNOWLEDGE_NODE-440",
"text": "warning\\nissue.sprint string Optional\\nFilters for issues with any of the sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1654_KNOWLEDGE_NODE-440",
"text": "warning\\nissue.sprint string Optional\\nFilters for issues with any of the sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1597_KNOWLEDGE_NODE-447",
"text": "warning\\nissue.sprint string Optional\\nFilters for issues with any of the sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1509_KNOWLEDGE_NODE-442",
"text": "warning\\nissue.sprint string Optional\\nFilters for issues with any of the sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string",
"title": "Prepare — DevRev | Docs"
},
{
"id": "ART-1306_KNOWLEDGE_NODE-445",
"text": "warning\\nissue.sprint string Optional\\nFilters for issues with any of the sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string",
"title": "List — DevRev | Docs"
},
{
"id": "ART-1636_KNOWLEDGE_NODE-451",
"text": "warning\\nissue.sprint string Optional\\nFilters for issues with any of the sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string",
"title": "Update — DevRev | Docs"
},
{
"id": "ART-1305_KNOWLEDGE_NODE-447",
"text": "warning\\nissue.sprint string Optional\\nFilters for issues with any of the sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1593_KNOWLEDGE_NODE-448",
"text": "warning\\nissue.sprint string Optional\\nFilters for issues with any of the sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string",
"title": "Get — DevRev | Docs"
},
{
"id": "ART-1577_KNOWLEDGE_NODE-448",
"text": "warning\\nissue.sprint string Optional\\nFilters for issues with any of the sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1834_KNOWLEDGE_NODE-450",
"text": "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 strings Optional\\nFields to",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1637_KNOWLEDGE_NODE-449",
"text": "warning\\nissue.sprint string Optional\\nFilters for issues with any of the sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string",
"title": "Delete — DevRev | Docs"
},
{
"id": "ART-1639_KNOWLEDGE_NODE-440",
"text": "warning\\nissue.sprint string Optional\\nFilters for issues with any of the sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string",
"title": "Export Post — DevRev | Docs"
},
{
"id": "ART-1826_KNOWLEDGE_NODE-443",
"text": "warning\\nissue.sprint string Optional\\nFilters for issues with any of the sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string",
"title": "Get Post — DevRev | Docs"
},
{
"id": "ART-1579_KNOWLEDGE_NODE-441",
"text": "warning\\nissue.sprint string Optional\\nFilters for issues with any of the sprint.\\nissue.subtype string Optional\\nFilters for issues with any of the provided subtypes.\\nopportunity.account string Optional\\nFilters for opportunities belonging to any of the provided accounts.\\nopportunity.contacts string Optional\\nFilters for opportunities with any of the provided contacts.\\nopportunity.subtype string Optional\\nFilters for opportunity with any of the provided subtypes.\\nowned_by string",
"title": "List Post — DevRev | Docs"
}
] |
e89b85e0-7b2e-4cd7-9cad-3c98bc520060
|
workflow reopen linked ticket when issue state changes to in_review and add internal note
|
[
{
"id": "ART-2009_KNOWLEDGE_NODE-27",
"text": "ticket is closed or reopened.\\n* Post in the linked conversation when a ticket is linked.\\n* Post in child issue timeline when parent issue is closed.\\n* Post in parent issue timeline when child issue is closed.\\n* Post to issue's timeline when linked ticket's severity is changed.\\n* Post in ticket's timeline when an issue linked to it is closed.\\n* Post in enhancement's timeline when any linked issue is *In Development*.\\n* Update ticket's stage when linked issue's state changes.\\n* Update",
"title": "Convergence | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2016_KNOWLEDGE_NODE-26",
"text": "of an issue changes then the changes are also reflected accordingly in issues/enhancements.\\n\\n1. Create the mapping in the CSV file in the format given below. The CSV file should contain the following columns:\\n\\n * Ticket Subtype\\n * Issue Stage or Enhancement Stage\\n * Ticket Stage\\n\\n Refer to the default stages documentation for each product feature:\\n\\n * [Issue stages](https://docs.devrev.ai/product/issues)\\n * [Ticket stages](https://docs.devrev.ai/product/tickets)\\n *",
"title": "StageFlow automator | Automate | Snap-ins | DevRev"
},
{
"id": "ART-2016_KNOWLEDGE_NODE-25",
"text": "more information, refer to the\\n[StageFlow Automator snap-in](https://marketplace.devrev.ai/custom-covergence) on the DevRev marketplace.\\n\\nInstallation\\n------------\\n\\n1. In DevRev, go to **Settings** > **Snap-ins** and click **Explore Marketplace** in the top-right corner.\\n2. In the DevRev marketplace, find **StageFlow Automator** and click **Install**.\\n\\nConfiguration\\n-------------\\n\\nYou need to create a mapping between the tickets and issues/enhancement stages so that when the stage",
"title": "StageFlow automator | Automate | Snap-ins | DevRev"
},
{
"id": "ART-16803_KNOWLEDGE_NODE-26",
"text": "Tickets\\n* Meetings\\n* Objects linked to issues\\n* Users\\n\\nTo configure a workspace object loop:\\n\\n1. On the **workflow canvas**, add an action step named **Loop for [Object]**, where [Object] is the entity you want to iterate over.\\n2. Apply **filter conditions** to refine the set of objects included in the loop and perform operations on them.\\n\\nAll **actions** inside the loop execute once per object that satisfies the filter conditions.\\n\\n### For Each\\n\\nThe **For Each** loop iterates",
"title": "Workflow nodes | Workflows | Computer by DevRev | DevRev"
}
] |
f0383078-1edf-47e8-b0c5-d26927af2d02
|
delete ticket without notifying customer
|
[
{
"id": "ART-1953_KNOWLEDGE_NODE-27",
"text": "conversation, ensuring seamless and continuous communication.\\n\\nBy default, notifications are sent from [notifications@devrev.ai](mailto:notifications@devrev.ai). 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"
}
] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.