LogoLogo
Back to studio
  • Formsort documentation
  • โฉQuickstart
    • ๐ŸŸขGet started with Formsort
    • ๐ŸŽCore concepts
    • โ„น๏ธQuestion and content reference
    • ๐Ÿ“•Key terms
    • ๐Ÿž๏ธCreate your first flow
    • ๐Ÿ“–Add content and collect answers
      • ๐ŸคณCapture demographic data
      • โ„น๏ธAdd informational content
      • ๐Ÿ” Review your variable schema
    • ๐ŸŽจCreate a theme
      • Set brand guidelines
    • ๐ŸคนPersonalize your flow
      • ๐ŸŒŸTemplate your variables
      • ๐Ÿง Add conditional logic
      • ๐Ÿ’ซUsing conditional logic with Calculated and API variables
      • ๐Ÿ”šEnd the flow
    • ๐Ÿ”€Set up integrations
    • ๐Ÿš€Go live
      • Auditing your flow for content, functionality, and design
    • ๐Ÿ’ผCommon use cases
      • ๐Ÿ’”Disqualify responders
      • ๐Ÿ—“๏ธAdd a scheduling option
      • ๐Ÿ“„Allow responders to read and accept your company policies
  • ๐Ÿ—๏ธBuilding flows
    • Flows and variants
      • Flow starts
    • Adding content
      • Groups
      • Steps
        • Settings
        • Logic
        • Style
      • Questions
        • General Settings
        • Style
        • Address
        • Comparison
        • Confirmation
        • Date
        • Date & Time
        • Email address
        • File upload
        • Grid choice
        • Iframe
        • Image upload
        • Number
        • Payment
        • Phone number
        • Postal code
        • Question group
        • Region
        • Select
          • Providing choices via API or calculation
        • Signature
        • SSN
        • Text questions
        • Yes/No
      • Content
        • General Settings
        • Statement
        • Image
        • Video
        • Next button
        • Divider
        • Map
      • Endings
      • Using markdown
      • Using variable templating
        • Template formatting functions
      • Copy-pasting form content
      • Content library
    • Conditions and logic
      • Logical operator reference
      • Advanced logic
    • Variables (answers)
      • Variables from questions
      • Externally provided variables
      • Calculated variables
      • API lookups
      • System Library variables
      • Orphaned variables
    • Schemas
      • JSON Schemas
      • Validating flow schemas
    • Redirects
    • Styling and themes
      • CSS Reference
      • Overriding theme styling
      • Custom CSS overrides
      • Content area
      • Animations and transitions
      • Form Layout
      • Typography
        • Adobe Fonts
        • Hosting custom fonts
      • Color variables
      • Dimension variables
      • Question containers
      • Assets
      • Form Buttons
        • Select buttons
      • Inputs and dropdowns
      • Checkmarks
      • Tables
      • Sliders
      • Divider lines
      • Progress bar
      • Comparison cards
    • Variant settings
      • Form behavior for returning responders
      • Group ranking API
    • Publishing and versions
      • Preview window
      • Deploying
      • History
  • ๐Ÿ’พHandling data
    • Philosophy and data retention policy
    • Viewing form answers
    • Responder UUIDs
    • Environments
      • Loading different environments
    • Passing data in
      • URL parameters
      • POST body
      • Embed query parameters
    • Custom validators
    • Form answers and events
      • Analytics events
      • Signed requests
      • Event payload shape
      • Submission frequencies
      • Runtime error reporting
      • Admin API
      • Flow content data format
    • Integration reference
      • Amplitude
        • Amplitude cross domain tracking
      • BigQuery
      • FullStory
      • Google Analytics
        • Updating from Universal Analytics to GA4
      • Google Cloud Storage
      • Google Sheets
      • Google Tag Manager (GTM)
        • JavaScript triggered by flow events
      • Hubspot
      • Jornaya
      • Optimizely
      • PostgreSQL
      • Redshift
      • Rudderstack
      • S3
      • Salesforce
      • Segment
        • Segment Setup
        • Segment cross domain tracking
      • Stripe
      • TrustedForm
      • Webhooks
        • Zapier
  • ๐Ÿ“บGoing live
    • Custom domains
    • Built-in analytics
    • Embedding
      • Web-Embed API
        • React-embed
      • Adding authentication
      • Embedding forms in iOS and Android
      • Setting up a dev environment
    • Split testing
    • Preflight checklist
  • ๐ŸขTeams
    • Accounts
      • Roles and permissions
    • Events subscriptions
    • Workspace domain detection
Powered by GitBook
On this page
  • Setup
  • Step 1: Create Zap with Webhooks as the first trigger.
  • Step 2. Choose a Trigger Event
  • Step 3: Integrate Webhook in Formsort
  • Step 4. Send test request to Zapier
  • Step 5: Test trigger
  • Step 6: Customize data sent from Formsort to other apps
  • Step 7: Turn on your Zap!

Was this helpful?

  1. Handling data
  2. Integration reference
  3. Webhooks

Zapier

PreviousWebhooksNextCustom domains

Last updated 2 years ago

Was this helpful?

Like , is a dynamic integration option to store and send data from Formsort to other Apps. As long as an app is found in Zapier's library, you can use Zapier to seamlessly stream data collected from Formsort forms. That said, we currently do not support direct implementations with Zapier. However, it is simple and effective to integrate with Zapier through a Webhook! Follow the setup below to do just that!

Setup

Step 1: Create Zap with Webhooks as the first trigger.

Adding Webhooks as the first trigger for your Zap will give us the ability to send requests to Zapier through a Webhook integration, within the Formsort platform (more below on how to formally setup this integration).

Step 2. Choose a Trigger Event

The Trigger Event is what occurs once the Webhook receives a request from Formsort. This field has two relevant options, Catch Hook and Catch Raw Hook. These trigger events differ as follows:

  • Catch Hook parses individual fields from the body of the Formsort POST request. This allows you to customize exactly which fields you pass to other apps, and how you structure those fields.

  • Catch Raw Hook leaves the JSON request as-is, and includes all fields, including headers. Data can only be sent to other apps in that raw format.

Most users will want to choose the Catch Hook option. You'll use this option whenever the data needs to be easily comprehensible to human readers. If, for example, you wanted to pass the data to an email or a CMS, this option would serve your needs. If, however, you do want to preserve the response completely intact, Catch Raw Hook would be the preferred option.

For the rest of this walkthrough, we will assume the user chooses Catch Hook

Step 3: Integrate Webhook in Formsort

Now, we need to enable this Webhook within Formsort. First, copy the Custom Webhook URL from the Set up trigger option in Zapier.

If you receive a message that hooks.zapier.com cannot be added as a Webhook, be sure to add the 'hooks.zapier.com' domain in Account --> Security --> Allowed Webhook destinations --> + ADD ANOTHER DOMAIN.

Step 4. Send test request to Zapier

Use Send Test from the Formsort Studio to send a request to the Webhook URL.

Step 5: Test trigger

Back in Zapier, continue to the Test trigger option, and enable a test. Assuming you successfully sent the test to the Webhook from Formsort, the Zapier Webhook should successfully have found a request that contains fields found in the Formsort payload. These should contain fields like answers, responder_uuid, and variant_uuid. And, that's it! Your Zap is now ready to receive data from Formsort, through a Webhook. All that's left to now is to connect your Zap with other apps!

Step 6: Customize data sent from Formsort to other apps

At this point, you will add additional Apps to your Zap to receive form submission data from Formsort. While it is impossible to walk through every possible app you could integrate with, you will find all the individual fields parsed from the body of the Formsort request available in the actions for other apps. Using Slack as an example, the following screenshot shows that individual fields from the form submission data can be accessed and used for any Slack action:

Step 7: Turn on your Zap!

Now that your Zap is ready to receive data from Formsort through a Webhook, and you have other apps integrated into your Zap that will receive Formsort form submission data, it's time to turn your Zap on! You will first need to test whatever actions you setup in Zapier, then you will be prompted to enable your Zap.

If you do not turn your Zap on, then data from published Formsort form flows will not be received. Do not confuse the fact that your Zap receives requests from 'Send Test'

In Formsort, navigate to the Integrations tab for your flow (found at the Flow level, not at the Variant level), and then to the Webhooks option. Choose a posting frequency, then copy the Custom Webhook URL into the Webhook URL field:

After you've connected to Zapier via Webhook, if you have deployed flows previous to the integration, it is advisable to re- those flows.

๐Ÿ’พ
Webhooks
deploy
Segment
Zapier
Create Zap with Webhooks as first trigger
Step 2: Choose a Trigger Event
Copy Custom Webhook URL
Paste Custom Webhook URL into Form: Integrations --> Webhooks --> Webhook URL
Send Test to Zapier Webhook
hint
Sending form submission data to Slack through Zapier
Zapier On/Off toggle switch