Notify Slack When a Ticket Is Created

Use this guide when the support team wants Slack alerts for new tickets.

The goal is a useful alert, not a noisy channel. Include enough ticket context for triage and avoid sending duplicate notifications for every small update.

Decide who should act on the alert before choosing the channel. A support triage channel usually works better than a broad company channel.

Setup Steps

1. Configure Slack as a notification channel if your workspace uses Slack webhooks.
2. Create or confirm the ticket workflow in CRM.
3. Open Workflows.
4. Create a workflow with a ticket-created trigger.
5. Add a Slack or notification action when that action is available in your workflow builder.
6. Include ticket subject, priority, status, and link fields in the message.
7. Publish the workflow.
8. Create a test ticket.
9. Review the workflow run and the Slack message.

Use a dedicated support or triage channel when possible. Avoid sending ticket alerts to a broad company channel unless the whole company is expected to act on new tickets.

Keep private customer details out of the Slack message unless that channel is approved for the same sensitivity as the ticket itself.

Before publishing, confirm who will respond to the alert and what the expected response time is. A notification without ownership can make the team feel informed while no one actually handles the ticket.

If Slack Is Not Available in the Builder

Use the notification-channel settings and integration docs to confirm Slack is connected. If the action is not available in the workflow builder yet, use an email or internal notification action instead and revisit the workflow after the Slack action is enabled.

Message Content Checklist

Include only the fields needed for triage:

• ticket subject
• priority and status
• customer or source when appropriate
• owner or queue
• link back to Agiled

Keep sensitive customer details inside Agiled unless the Slack channel is approved for that data.

Test The Alert

Create a test ticket with a clear subject and priority. Confirm the workflow run succeeded, the Slack message links back to Agiled, and the alert appears in the right channel. Then close or delete the test ticket if it should not remain in support reporting.

Test with at least one low-priority and one urgent ticket if conditions are used. This confirms the workflow posts only the tickets the team expects to see in Slack.

Avoid Noisy Alerts

Start with ticket-created alerts only. Add status, priority, or assignment alerts later only when the team has a clear reason to act on them. If the same ticket can trigger several workflows, include the workflow name or alert purpose in the message so the team can tell why it was posted.

Review the Slack message after the first real ticket. It should include enough context to triage without exposing private customer data that does not belong in Slack.

If the alert is noisy after the first week, add trigger conditions for priority, source, status, or ticket type instead of asking the team to ignore extra posts.

Review alert volume after the first few days. If support stops reacting to the channel, the workflow needs tighter conditions or a different destination.

Related Docs

• Notification Channels
• Tickets
• Create Workflow
• Workflow Runs