A record for every form submission
Each submission a form tool posts becomes a row, with the fields mapped to your columns.
Build this workflowGive a workflow its own webhook address and anything that can send an HTTP request, a form, a store, a payment provider or your own code, can post to it. The workflow adds, updates or looks up records in your Airtable base. Describe it in plain words; AI builds it.
Pick one and it is handed to the builder as your first message, or describe your own.
Each submission a form tool posts becomes a row, with the fields mapped to your columns.
Build this workflowFind the record with the order’s id and update its status, or create it when it is new.
Build this workflowCheck the sender’s signature first, then write the customer, the amount and the date.
Build this workflowEach webhook trigger has a key, and the address is bound to it, so it does not change when you edit the workflow.
Stripe, GitHub, Shopify, Slack and any sender following the Standard Webhooks specification have their signatures verified before a run starts.
Each request the address receives is one run, however many Airtable records it writes. Free AI building and editing have weekly usage limits.
Pick one and Whenever’s AI writes it against your accounts. What comes back is the workflow’s code, yours to read and edit. Nothing here is a locked-down preset; every template is a first prompt.
Airtable automations can start from an incoming webhook. Use a workflow when the job needs more: checking a sender’s signature, reshaping the payload, deciding which record to update, or acting in another tool as well as Airtable.
Yes. An Airtable automation can send a request to the workflow’s webhook address, and the workflow can then act in any of your other tools.
No. Describe what should happen when the webhook arrives and Whenever writes the workflow. The code is there to read and export, but you never have to write it.
Demand checked 2026-09-30; product claims from the Whenever docs.
Describe what arrives and what should happen in your base. Whenever builds it and runs it the same way every time.