# Zapier

Connect Form Plume submissions to Zapier and route them to thousands of apps. Set up the submission trigger or a signed webhook, then map your form fields.

[Zapier](https://zapier.com/) connects a Form Plume submission to thousands of other apps.

## Create the trigger

Choose the Form Plume submission trigger when it is available in Zapier. Until then, start the Zap with a webhook and use a [signed Form Plume webhook](/docs/integrations/webhooks) as the source.

## Capture a real sample

Send a representative test submission before mapping fields. Include optional values and files your production form may send.

A typical Zap sends each submission to a spreadsheet, CRM, or Slack channel. Every field on your form arrives as a separate value you can map into the destination app, so a "sync submissions to a sheet" Zap works the same way as one that posts to a chat room or creates a contact record.

Build the remaining Zap from that sample, turn it on, and send one more test through the published form.

## What data is available

Each submission gives Zapier the values people entered on your form, one per field, using the `name` attribute on each input as the key. Alongside those, Zapier receives the submission [metadata](/docs/submissions/metadata) Form Plume records, and any [file uploads](/docs/forms/file-uploads) arrive as attachment values you can pass through to the destination app.

If you would rather route submissions without Zapier, Form Plume also has native [Google Sheets](/docs/integrations/google-sheets) and [Slack](/docs/integrations/slack) integrations that skip the middle step.

Keep the webhook secret private and verify signatures before using sensitive submission data.