Yay Forms integrations: native connections, Zapier, Google Sheets and webhooks

The native Yay! Forms integrations list

Yay! Forms connects directly to 24 tools and channels listed on its integrations page as read on 3 October 2026, and reaches everything else through Zapier, Make or a webhook. Native means you set it up inside the form builder under Integrate, with no third-party automation account.

Several entries serve the Brazilian market. For a US small business the practical native set is Google Sheets, HubSpot, Mailchimp, ActiveCampaign, GoHighLevel, Slack and the tracking tools.

Google Sheets: setup steps from the help center

The Google Sheets integration writes each new response to a spreadsheet as it arrives. The official steps are:

1. Open or create a form and click Integrate at the top of the builder.
2. Find Google Sheets and click Set up.
3. Choose the Google account to connect.
4. Save the integration to create a new spreadsheet, or paste the URL of an existing one.

You can then switch the integration on or off and run a test from the three-dot menu. The help center notes that a test needs at least one completed response and sends the most recent one. The listing also says partial answers can be saved to the sheet after a set idle time. If you only need a one-off copy, the Results tab exports responses as a file you can import into Sheets or Excel.

Zapier and Make: reaching tools with no native connection

In Zapier, Yay! Forms acts as a trigger app. A new submission starts the Zap and the action happens in the other tool. Setup per the help center:

1. In Zapier, create a new Zap and search for Yay! Forms as the trigger.
2. Click Sign in and paste your Yay! Forms API token.
3. Generate that token from your Yay! Forms profile page, or from the Zapier entry in the form's Integrate tab.

The help center has separate walkthroughs for Pipedrive, Notion, Trello, Gmail, Google Calendar, Google Contacts, MailerLite, Mailchimp and HubSpot through Zapier or Make, and for n8n through a webhook. Zapier and Make are billed separately by those companies, so count their cost when you compare tools on our feedback tool alternatives page.

Webhooks: security options and payload versions

Webhooks post the submission data to a URL you control. You add one under Integrate, then Webhooks, then Add webhook. The help center documents these options:

• A secret that signs each payload with HMAC SHA256, so your server can confirm the sender
• An SSL verification setting for deliveries
• A custom header added to each request
• Run on previous responses, which replays older submissions
• A trigger condition, so the webhook fires only for certain answers
• Two payload formats, V1 and V2, with different answer structures

Trigger conditions are case-sensitive unless you tick the case-insensitive option. So a condition typed in a different case from the answer will not match. Integration logs are available for checking what was sent.

Which plan the integrations need

The pricing page lists API access and webhooks under features that all plans include. Google Analytics, Google Tag Manager and Facebook Pixel are named only on the Plus and Professional cards. Email, WhatsApp and Slack notifications are also named only on those cards, yet the same page's list of features in all plans includes them. One vendor comparison page describes the native CRM integrations as available on Plus. The pricing page does not state a plan for Google Sheets, Zapier or the CRM connections, so confirm in a trial account before buying Starter for an integration. Plan prices are on our Yay! Forms pricing page.

What to check after connecting

• Submit a real test response and confirm it lands in the destination with every field mapped.
• Decide whether incomplete responses should be sent. With that setting on, every active integration receives both the partial and the completed version unless you add a trigger condition.
• Check that an embedded form still passes UTM parameters, if you track sources.
• Read the integration log after the first live day.

If your stack depends on Salesforce or on payment data inside the form, Yay! Forms' own comparison page points to Typeform for those. For everyone else, sending responses to a sheet or CRM is the first step in closing the feedback loop.