add item to timeline using snap-in trigger email to CC user on ticket
ART-1485_KNOWLEDGE_NODE-10
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
Snap-in triggered by a DevRev event — DevRev | Docs
ART-1485_KNOWLEDGE_NODE-8
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
Snap-in triggered by a DevRev event — DevRev | Docs
ART-1485_KNOWLEDGE_NODE-11
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
Snap-in triggered by a DevRev event — DevRev | Docs
ART-1277_KNOWLEDGE_NODE-28
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
Snap-in triggered by a DevRev event | DevRev | Docs
ART-1277_KNOWLEDGE_NODE-6
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
Snap-in triggered by a DevRev event | DevRev | Docs
ART-1278_KNOWLEDGE_NODE-22
"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
Snap-in triggered by an external source | DevRev | Docs
ART-1485_KNOWLEDGE_NODE-19
comment on a DevRev work item created.  \n    5|   - name: function_2  \n    6|     description:  \n    7|       Function to create a timeline entry comment on a DevRev work item on which  \n    8|       comment is added.\n[/code]  \n  \n[6](/public/snapin-development/tutorials/triggered-event#automations)\n\n### Automations\n\nWith the building blocks in place, the final piece of the puzzle involves defining automations. These automations encapsulate a trigger and a corresponding function that
Snap-in triggered by a DevRev event — DevRev | Docs
ART-1265_KNOWLEDGE_NODE-9
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![]()'
Restricted messages on a timeline | DevRev | Docs
ART-1277_KNOWLEDGE_NODE-14
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
Snap-in triggered by a DevRev event | DevRev | Docs
ART-1473_KNOWLEDGE_NODE-26
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
Snap-in triggered by an external source — DevRev | Docs
ART-1485_KNOWLEDGE_NODE-6
[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
Snap-in triggered by a DevRev event — DevRev | Docs
ART-1277_KNOWLEDGE_NODE-3
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
Snap-in triggered by a DevRev event | DevRev | Docs
ART-1265_KNOWLEDGE_NODE-1
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
Restricted messages on a timeline | DevRev | Docs
ART-1471_KNOWLEDGE_NODE-1
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
Restricted messages on a timeline — DevRev | Docs
ART-1277_KNOWLEDGE_NODE-25
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|  |
Snap-in triggered by a DevRev event | DevRev | Docs
ART-1265_KNOWLEDGE_NODE-6
"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":
Restricted messages on a timeline | DevRev | Docs