Post to Slack

Slack is a connected account on the property. You connect channels on the Integrations page; each connected channel then appears as a choice when you add a “Post to Slack” action to an automation.

Connect a channel

1. Open Property > Integrations and click the Slack tile.

2. Click Connect. You are sent to Slack to authorise SnipForm for your workspace and choose one channel.

3. Back in SnipForm the channel is listed on the Slack tile. Repeat from step 2 to add more channels; each connection binds one channel, and they accumulate.

To stop posting into a channel, remove it from the Slack tile. Automations still pointing at it fail on their next run (and count toward auto-disable), so edit those automations first.

Note

If the Slack tile shows a waiting list instead of a Connect button, Slack is not yet enabled for your account. Join the list and you will be told when it is.

Add the action

In the automation builder, add Post to Slack and choose a channel from the dropdown. That is the whole configuration. The message is built from the run’s payload; there is no template to write.

What the message contains

Every message has the same shape, top to bottom:

Block	Content
Header	The automation’s name (or its trigger label if unnamed)
Headline	One line describing what happened, by trigger type: “Contact form received a submission”, “Purchase recorded: $49.99”, “Contact identified”, “Contact created”, “Visitor viewed /pricing”, or “Event signup fired”. If the automation has a conversion condition, a second line: “Conversion completed: name”
Fields	Up to 10 label/value pairs. Form submissions list their answers first; event automations list the event’s value and meta. Each value is truncated to 300 characters
Context	Channel name, country and landing path for the session, when known
Button	View session, linking to the session in the SnipForm dashboard

Slack caps a fields block at 10 pairs, so a 14-field form shows its first 10 answers. Use a webhook action when you need every field.

A run from the Test button posts a sample message with a fictional session (Jane Doe, Austin, landed on /pricing from Google Ads) so you can see the layout before any real traffic.

Example

An automation named “New demo request” on the “A form is submitted” trigger produces:

New demo request
*Demo request* received a submission
────────────────────────────
*Name*            *Email*
Jane Doe          [email protected]
*Company*         *Message*
Acme Ltd          We'd like a walkthrough next week.
Google Ads  ·  United States  ·  landed on /pricing
[ View session ]

Delivery and retries

Messages post through Slack’s incoming webhook for the channel. A failed post is retried like any action: immediately, then after 2 minutes, then after 15. If the channel has been disconnected in SnipForm, the delivery fails at once with “Slack channel is no longer connected” rather than posting into a stale hook.