Slack and Front: New-Conversation Customer Alert Template

A webhook-triggered Spojit workflow that fires when Front opens a new customer conversation and posts the contact name, subject, and inbox to a Slack channel.

What It Builds

This template starts from a Webhook Trigger that Front calls the moment a new conversation lands in one of your inboxes. A Connector node on the front connector enriches the event with the conversation and contact details, then a Connector node on the slack connector uses send-message to post the contact name, subject line, and inbox into a channel of your choice. Your support team sees every new conversation in Slack without keeping the Front inbox open all day.

The Prompt

Paste this into Miraxa and it builds the workflow, connecting the tools for you:

Build a workflow with a Webhook trigger that fires when Front opens a new customer conversation. Use the front connector to look up the conversation and the contact, then use the slack connector to send a message to the #support channel with the contact name, the conversation subject, and the inbox name.

Connectors Used

  • Webhook trigger - Front posts the new-conversation event to the workflow's URL; verify it with a Slack or Custom signing connection.
  • front - get-conversation and get-contact read the subject, inbox, and contact name from the event; list-inboxes helps you confirm the inbox label.
  • slack - send-message posts the formatted alert to your support channel.

Customize It

Change #support in the prompt to the channel your team watches, and add or drop fields (for example the conversation tags or the assignee) from the message body. If you run several inboxes, ask Miraxa to route each inbox to a different Slack channel, or to add a Condition node that only alerts when the inbox name matches a specific queue. To verify the contact, swap get-contact for a list-contacts lookup by email in the same prompt.

Tips

  • Keep both front and slack nodes in Direct mode: the lookups and the post are predictable single-tool calls, so you avoid AI credits and get deterministic output.
  • Reference the trigger payload with {{ input }} when mapping the conversation id into get-conversation, so the right record is fetched on every run.
  • If the workflow needs to confirm the channel exists, ask Miraxa to add a list-channels step, or post by channel name directly in send-message.

Common Pitfalls

  • A Webhook trigger needs a signing connection to verify Front's request; without one the call is rejected. Set up the signing connection before you turn the workflow on.
  • The Slack channel must allow the connection to post. If send-message returns a not-in-channel result, invite the connection to the channel first.
  • Front can resend the same event; enable the trigger's event-id dedup so a single new conversation does not fire two Slack alerts.

Related

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.