Issue Created
Emit an event when an issue is created.
Ready-made Workflow
Send a Slack channel notification when a new Jira Cloud issue is created. Include the issue key, summary, project and issue type so your team can triage incoming work. Connect Jira and Slack, select a Jira site using Browse and choose a Slack channel. An optional JQL filter can restrict eligible projects; without a filter, new issues from the selected site are eligible. Wait for the Trigger to show Connected before creating a test issue. Existing issues and issue updates are not imported. Messages use plain text with link previews disabled. Descriptions, comments and attachments are not copied. Issue summaries become visible to channel members. This is a one-way notification, not a task or status sync. The fictional sample includes German characters. Manual reruns can send another notification.
What gets copied
FastHook recreates every Step, route, field mapping, and setting with new IDs in your workspace.
Emit an event when an issue is created.
Send text, Block Kit content, attachments, or a thread reply to a channel.
Before activation
Connect your own Jira account and review the provider settings used by this Workflow.
Connect your own Slack account and review the provider settings used by this Workflow.
Questions
No. FastHook creates a disconnected Draft. Connect your own Jira, Slack accounts before activation.
Yes. The copied Workflow is an editable Draft. Review every Step, input, mapping, and route before you activate it.
FastHook recreates the Trigger configuration, Action Steps, routes, and mappings with new IDs. Provider accounts, credentials, and secrets are never copied.
Only after you connect the required accounts, finish the configuration, and explicitly activate the Draft.