workflow trigger for new issue created and control to send slack message to assigned channel
ART-2035_KNOWLEDGE_NODE-51
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
Slack | Integrate | Snap-ins | DevRev
ART-2035_KNOWLEDGE_NODE-52
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
Slack | Integrate | Snap-ins | DevRev
ART-1284_KNOWLEDGE_NODE-15
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
Event sources | DevRev | Docs
ART-1478_KNOWLEDGE_NODE-18
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 ==
Event sources — DevRev | Docs
ART-1490_KNOWLEDGE_NODE-58
\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
Snap-in manifest — 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