Connect Zunoform to Twilio via Zapier
This is not a one-click native integration. Zunoform posts every completed response to a Zapier catch hook, and your Zap does the rest — so there is no Twilio button inside Zunoform and no OAuth connection between the two products. What you get instead is a webhook connection with field mapping you control in Zapier.
Sends an SMS when a response arrives — to your team, to the respondent, or to both, using the phone number they gave you.
The Zapier integration is on Zunoform’s free plan — 500 responses a month, no card. Webhooks by Zapier requires a paid Zapier plan; destination account requirements and task limits also apply.
Example workflow
Send a short acknowledgement after an enquiry
A service enquiry can trigger an SMS confirming that the request was received. Keep the message about receipt rather than promising an appointment or response time your team has not agreed to. Use a number you control for initial tests.
Prepare your Twilio account
Configure an appropriate Twilio sender and confirm the account can message the intended destinations. Collect phone numbers with country codes and a separate messaging preference. Check Twilio's current regional requirements before launch.
Four steps, start to finish
Start with a published Zunoform form, a Zapier plan that includes webhooks, and access to the destination account. Some destinations require additional permissions or setup.
Create a Zap with a Catch Hook trigger
In Zapier, create a new Zap and choose Webhooks by Zapier as the trigger app, then Catch Hook as the event. Zapier generates a URL for you and shows it on the next screen. Copy it.
Paste the URL on the Zapier card in Zunoform
Open your form in the Zunoform builder, go to the Integrations tab, and paste the URL on the Zapier card. We only accept an https address on zapier.com, so a typo is rejected rather than silently failing later.
Submit a test response so Zapier learns the shape
Publish the form and fill it in once yourself. Zapier's trigger step will pick that submission up as sample data — without it, the field list in the next step is empty and there is nothing to map.
Map your fields to Twilio
Add an action step and choose Twilio. Connect your account, then pick the action that sends an SMS from one of your Twilio numbers. Zapier's action list changes over time, so choose from what it shows you rather than hunting for an exact name. Drag your form's answers into the fields, test the Zap, and turn it on.
Suggested field mapping
Use this example to plan your form. Select the actual fields from your captured test response and the action available in your account; these are mapping suggestions, not a preconfigured Zap.
- Phone with country code
- Destination: Recipient
- Normalize the number to the format required by the action.
- SMS preference
- Destination: Filter before sending
- Only continue for the affirmative response.
- Fixed acknowledgement plus request reference
- Destination: Message body
- Keep sensitive form answers out of the message.
- Configured Twilio sender
- Destination: Sender
- Select a sender your Twilio account is permitted to use.
What Zapier receives
The payload includes formId, formName, responseId, submittedAt, status, answers and metadata. Answers are keyed by field ID, not by question label; inspect a test response to identify the answer you want. Multi-part answers can contain nested values, and uploads contain file references rather than binary attachments. Replacing a question can change its ID, so retest mappings after editing the form.
Delivery uses a background queue with retries for failed webhook requests. A successful hook does not confirm the later Twilio action succeeded. Check Zap history, and use responseId in a lookup or a processed-response log when duplicate processing would matter. Earlier responses are not automatically replayed when you connect the hook.
Test before sharing your form
Send a test to your own phone and confirm delivery status in Twilio, not just success in Zapier. Test a declined messaging preference and verify that no SMS is sent.
If the result is missing or wrong
For an undelivered message, inspect Twilio's delivery error and recipient format. Avoid repeated replays until the cause is fixed, as each successful send may create another message and charge.
Check the current Twilio actions in Zapier and Zapier’s webhook setup and plan requirements before configuring your account. Action availability and permissions depend on your connected account.
Questions people ask
Can I text the person who filled in the form?
Yes, if you collected a phone number and they agreed to be texted. Map their number to the recipient field. Getting consent for that is your responsibility, and an explicit question in the form is the cleanest way to have a record of it.
What does this cost?
Three separate bills, only one of which is zero. Zunoform's Zapier integration is free. Zapier charges tasks against your plan. Twilio charges per message and for the number.
Is this a native Zunoform integration?
No. Zunoform sends each completed response to your Zapier catch hook; you configure the destination and field mapping in Zapier. The Zunoform connection is included on Free, but Webhooks by Zapier requires a paid Zapier plan. Native options include Google Sheets and Zoho CRM on Free, with Slack, Notion, HubSpot, Mailchimp, Airtable and Excel on Pro. Form notification emails on Free require your own SMTP configuration; platform-sent form emails require Pro or Business.
Ready when you are
Better forms.
Better data.
Start with a conversation, a document or a single page.
Unlimited forms and 500 responses per month on Free.
No card required.
- No credit card
- Unlimited forms
- 500 responses / month