View a form's integration destinations

How to see which external services a form sends data to

The Form Integrations page shows every external destination configured for a single form — Airtable bases, Slack channels, webhooks, Mailchimp lists, and any other connected service. Each destination appears as a card listing its name, provider, current on/off state, and the order it fires when someone submits the form. This page is the starting point for reviewing, editing, or reorganising where your form data goes after a visitor clicks Submit.

Note: Adding, editing, enabling, and removing destinations is currently in active development. The list view documented here is fully functional. Changes to individual destinations will be covered in a follow-up guide once those paths are stable.

What is this for?

The Form Integrations list gives you a single-glance answer to "where does this form's data go?" Use it any time you need to audit submission routing — before you launch a campaign, after you inherit a site from another admin, or when a contact reports their message wasn't received. The list also shows the firing order, which matters when you have set a Stop on Success flag: if the first destination receives the data without error, lower-priority destinations are skipped.

Good use cases

Example 1: Pre-launch audit for a campaign form. Your marketing team built a sign-up form two months ago and is about to promote it. Before the campaign goes live, open the form's integrations list and confirm the Mailchimp destination is enabled and the Airtable backup is second in order. Here is what a fully-configured list looks like:

Three destinations in priority order. Mailchimp fires first; because Stop on Success is on, if Mailchimp accepts the submission the Airtable row is still written (Stop on Success only skips lower entries, not the next-enabled one when the fired destination succeeds). The Slack notification is disabled and will not fire.

Example 2: Checking a newly inherited site. You have just taken over admin access for a client's site. Open each form's integrations list to see what is connected. Here is the empty state you will encounter on a fresh form that has no destinations yet:

An empty destinations list means every submission is stored in SGEN's submissions log only — nothing is forwarded automatically. If the client expected leads to flow into a CRM, the integration was never configured.

Example 3: Reviewing order after a destination was added mid-campaign. A teammate added a new Webhook destination yesterday. Open the integrations list and check the Order column. If the new destination is at position 1 and the existing Mailchimp destination is at position 2, you may need to reorder so Mailchimp still fires first. The order column shows the current sequence at a glance:

The webhook is at position 1, Mailchimp at position 2. If this is wrong, use Edit on each destination to adjust the order value before the next batch of submissions fires.

What NOT to use this for

• Reviewing individual submission data — this page shows routing configuration only. To see what was submitted, go to the Submissions view from the main Forms list.
• Checking whether a past submission actually reached a destination — the integrations list shows current config, not delivery history. Delivery logs are separate.
• Global reCAPTCHA or form-wide API key settings — those live in Settings, not per-form integrations.

How this connects to other features

• Forms — the integrations list is nested under a specific form. Navigate there via the Integrations button on the Forms list, or directly at /sg-admin/forms/<id>/integrations. There is no route to integrations without a parent form.
• Form Submissions — submissions are stored in SGEN regardless of integration status. Integrations are forwarding rules that fire in addition to local storage, not instead of it.
• Notifications — SGEN's built-in email notifications (admin alert + submitter confirmation) are configured inside the form's Mail Settings, not here. Form Integrations handle third-party forwarding; Notifications handle SGEN's own email dispatch.
• Tracking Consent — if your site uses Tracking Consent (cookie banner), note that form submission data is collected regardless of consent state — consent settings govern analytics scripts, not form storage or integrations.

Before you start

• You need admin access to /sg-admin/.
• The form you want to review must already exist. If the form does not exist yet, create it in the Forms area first.

Where to go

1. Go to Forms (/sg-admin/forms/).
2. Find the form in the list.
3. Click the Integrations button in that form's row actions.

The page loads at /sg-admin/forms/<id>/integrations and shows all destinations for that form.

What you see on this page

The integrations list is read-only. Each destination card shows:

• Destination name — the label you (or a previous admin) gave this destination when it was created.
• Provider — the service slug (airtable, slack, webhook, mailchimp, or similar).
• Order — the integer sequence in which destinations fire on submit. Lower numbers fire first.
• Status — Enabled (fires on submit) or Disabled (skipped, stays in the list for later).
• Stop on Success — when enabled on a destination, a successful dispatch to that destination prevents lower-order destinations from firing during the same submission. Used to avoid redundant data sends.
• Edit and Delete buttons — per-destination actions. Editing and deleting is functional once the destination editing paths are stable. Treat this page as your review view for now.

If the form has no destinations configured, the page shows a "No destinations yet" message with an Add Destination button.

What success looks like

You can reach the page and see the full list of destinations (or the empty state). The breadcrumb reads Dashboard / Forms / [Form Title] / Integrations, confirming you are on the right form. The Add Destination button is present. Navigating away via the breadcrumb takes you back to the Forms list without data loss.

What to do if it does not work

• You see a "Data not found" or 404 page — the form ID in the URL is invalid or that form was deleted. Return to the Forms list and navigate from there.
• You expected a destination to appear but it does not — the destination's provider may not be enabled in your site's integration configuration. Contact your site administrator to confirm which providers are active.
• The breadcrumb shows the wrong form title — the title shown is the form's saved name. If it looks wrong, verify you clicked Integrations on the intended form.

Next step

Once the per-destination editing paths are released, you will be able to add, enable/disable, reorder, and remove destinations from this same panel. Watch the What's New section for updates.