Slack form integration
SagePigeon posts each submission from your website form into the Slack channel you choose. Every answer arrives labelled, and a button opens the full record in SagePigeon, where you can see whether anybody has replied. Slack is included on every plan, Free too.
What lands in the channel
A Slack message for a contact form called "Website contact form" looks like this:
New submission: Website contact form
Name Email
Priya Raman priya@example.com
Message
Could you cater a weekday lunch for 40 people in March?
[ Open in SagePigeon ]The header names the form, so one channel can take several forms and you can still tell them apart. Each field becomes a bold label with its value underneath, and Slack lays them out in two columns. Field names are turned into labels for you: email becomes "Email", event_date becomes "Event date", and eventDate becomes "Event Date".
A few limits come from Slack's message format and are applied before posting:
- The first 10 fields are shown. The rest are in the record behind the button.
- A value longer than 200 characters is cut and ends with "…".
- Slack's notification preview shows the plain line "New submission on Website contact form".
Fields that are not answers never reach Slack: the honeypot field, the captcha token and SagePigeon's own fields such as _redirect.
If you are building something that reads these messages, this is the payload SagePigeon sends to Slack's incoming webhook:
{
"text": "New submission on Website contact form",
"blocks": [
{ "type": "header", "text": { "type": "plain_text", "text": "New submission: Website contact form" } },
{ "type": "section", "fields": [
{ "type": "mrkdwn", "text": "*Name*\nPriya Raman" },
{ "type": "mrkdwn", "text": "*Email*\npriya@example.com" },
{ "type": "mrkdwn", "text": "*Message*\nCould you cater a weekday lunch for 40 people in March?" }
] },
{ "type": "actions", "elements": [
{ "type": "button", "text": { "type": "plain_text", "text": "Open in SagePigeon" }, "url": "https://…/app/forms/FORM_ID" }
] }
]
}Set it up
You need a Slack incoming webhook URL for the channel. Slack creates one when you add the Incoming Webhooks feature to a Slack app in your workspace; it starts with https://hooks.slack.com/services/.
- In SagePigeon, open the form and go to the Settings tab.
- Open Integrations. Under Chat destinations, press Add a destination.
- Leave the type on Slack and paste the webhook URL into the address field.
- Keep on ticked and press Save integrations.
- Go to the Setup tab and press Send a test submission. The message should appear in the channel within a few seconds.
To post the same form to two channels, add a second destination with the other channel's webhook URL. A form can have up to 10 destinations.
Plans
Slack is on Free, Pro and Scale. Free includes 500 submissions a month and 3 forms; every submission that is accepted is posted. Teams, Discord, Google Chat, Mattermost, Telegram and webhooks need Pro or Scale; on Free they show as "paid" in the type list. See pricing.
Limits and gotchas
- The address must be public and use https. SagePigeon checks the URL when you save and again before each post, and refuses anything that resolves to a private network.
- A refused post is tried again. If Slack answers with an error or takes longer than 10 seconds, SagePigeon tries the post again after 30 seconds, 2 minutes, 10 minutes and 15 minutes, 5 attempts in all. Only the Slack post is retried, so the email notification is never sent twice. Each attempt is in the submission's delivery log with the HTTP status.
- The submission is never lost. It is stored before anything is sent. If all 5 attempts fail, it shows as partly delivered and the form's Health tab counts it under "Not accepted on delivery".
- Test after you rotate the webhook in Slack. Slack disables an old URL when the app is removed or the webhook revoked. Every post to it fails with a 404 or 403 until you paste the new URL into the destination. Send a test afterwards.
- Drafts. If the form has unpublished changes, Save integrations saves into the draft. The destination starts posting once you publish the draft from the bar at the top of the form.
- Agency client logins can add their own Slack destinations to forms they can see, up to 5 per form, without seeing the ones your team set up.
Related
- Send website form submissions to Slack without a backend: the full walkthrough, from a plain HTML form to the first message.
- Contact form leads lost in a shared inbox: what happens after the Slack ping, and how SagePigeon knows a request was answered.
- Webhooks and chat in the docs
- All integrations