Skip to main content

Overview

Submission actions (post-actions) run automatically after a form is submitted. Use them to:
  • Send data to your CRM or backend
  • Notify your team via Slack
  • Send email alerts to team members
  • Trigger automation workflows

Action Types

Webhook Action

Send form data to any HTTP endpoint:

Webhook Payload

The webhook receives a POST request with this JSON body:

Custom Headers

Add authentication or custom headers:

Retry Logic

Webhooks automatically retry on failure: Status tracking:
  • pending — Initial state
  • webhook_success — Delivered successfully
  • webhook_failed — Failed after all retries

Slack Action

Send notifications to Slack channels:

Getting a Slack Webhook URL

  1. Go to Slack API Apps
  2. Create or select an app
  3. Navigate to Incoming Webhooks
  4. Activate and create a new webhook
  5. Choose the channel to post to
  6. Copy the webhook URL

Message Templates

Use {{fieldName}} to include form values:
Special variables:
  • {{fieldName}} — Any form field value
  • {{_toolName}} — The form tool’s name
Slack messages support markdown formatting: *bold*, _italic_, `code`, and line breaks with \n.

Max Length

Message templates have a maximum length of 2,000 characters.

Email Action

Email team members when forms are submitted:

Configuration

Finding User IDs

User IDs are the team members in your account. Find them in:
  • Settings → Team — View team members
  • Each member has a unique ID

Email Content

The email includes:
  • Form name and submission time
  • All form field values
  • Link to conversation history
  • Conversation context

Multiple Actions

Combine multiple post-actions:
Actions run in parallel for speed.

Form Execution Modes

Control how form submissions are processed:

Webhook Mode (Default)

Form data is sent to your server/webhook only.

Client Mode

Form is handled entirely by client-side JavaScript. No data sent to Ansa. See Triggering Forms in Code for client handlers.

Both Mode

Data is sent to webhook AND processed by client-side handler.

Complete Example

Full form with all post-action types:

Zapier

Make (Integromat)

HubSpot

Salesforce

Use Zapier or a middleware to transform the payload:

Monitoring Submissions

View all form submissions in the Leads dashboard: Leads dashboard
  • Filter by form/tool
  • View submission status (pending, success, failed)
  • See full conversation context
  • Export data for analysis

See Also