How to integrate Unify with Airtable
To integrate Unify with Airtable, send a JSON POST from a Unify Play to an Airtable When webhook received trigger. Configure Create record to map the input into a review table. Give each new row a review status and an owner before deciding what happens after approval.[1][3][4]
- Connection
- Via webhook
- Automation
- Tool
- Airtable
- When webhook received
- Data flow
- Unify → Airtable
- JSON payload
At a glance
- Choose the reviewer and the decision each row supports
- Keep review status separate from the supplied prospect facts
- Test repeated arrivals before using the queue for live work
When this workflow makes sense
Start with the decision your team needs to make, then choose the connection that supports it.
A review queue is useful when the next step needs judgment: choosing an account approach, checking missing context, or agreeing who should follow up. Keep the facts supplied by Unify separate from the reviewer’s decision. A row marked Approved should have an agreed operational meaning; creating the row does not itself start outreach or return that decision to Unify.
A good fit when
RevOps and sales teams that already coordinate work in Airtable and want a human review step for selected prospects.
Reconsider the plan when
If nobody owns the queue or can explain what approval changes, define that process first. For records that belong directly in an existing CRM, assess the supported CRM connection as well.
Design the handoff
Use this framework to agree on the input, the next action, and who owns the result.
Suggested workflow design, based on the documented capabilities below.
| Stage | Decision to make |
|---|---|
| Review purpose | Write the question the reviewer should answer for each incoming prospect. |
| Record identity | Choose whether the queue represents people or companies and define how to recognize a repeat. |
| Ownership | Choose a reviewer and an initial status such as Needs review. |
| After approval | Define the next human action or separately configured automation; do not assume the status returns to Unify. |
Explore the scenarios
Choose the situation that fits your team and work through the proposed plan.
Open a scenario to explore its plan. Checklists track your selections in this page only.
Build a prospect review queue
The team wants to review selected prospects before deciding on follow-up.
Make the review decision visible. Incoming facts, reviewer notes, and approval status should be separate fields.
- Create a table with the proposed prospect fields and review status
- Map the webhook input with Create record and set Needs review
- Assign a reviewer and inspect a sample row together
Handle prospects already in the queue
The same person can reach the Play again while an earlier review is still open.
Choose a person or company identity deliberately and preserve prior review work. Handle multiple matches as an exception.
- Use Find records with the identity chosen for the queue
- Configure conditional handling for no match, an existing match, and ambiguous matches
- Test a repeated sample and confirm that the earlier review decision is preserved
Illustrative workflow, not a preconfigured automation. Complete these checks in your own account.
Define success before launch
Inspect the data and the intended outcome separately. Connection status is only the first check.
Expected, not tested
The destination table contains a sample prospect with the intended field values and a review status chosen by your team.
Inspect automation history and the created row. Receipt of a request and successful creation of a useful review record are separate checks.
Documentation-based reference. This workflow has not been tested end to end. Use a record or event you control before enabling live activity.
Questions answered
Common decisions when connecting Unify and Airtable.
How do I connect Unify to Airtable?
Send a Unify POST request to an Airtable When webhook received trigger. Test the trigger, then add the action your process needs.[3]
Does receiving a webhook automatically create a row?
Add and configure Create record to create a row. Map values from the trigger and set any fixed values, such as the review status, in that action.[4]
How should I handle a prospect already in Airtable?
Use Find records with a chosen identity field, then decide what should happen for zero, one, or multiple matches. An email may identify a person; a domain identifies a company. Choose according to your review process.[5]
Will an Airtable approval update Unify automatically?
No return path is established by this outbound webhook. Treat approval as a local review decision until a separate supported delivery path is designed and tested.[1]
What protects the Airtable webhook endpoint?
The generated URL grants access. This trigger does not verify webhook signatures; keep the URL private and assess whether that fits your requirements.[3]
Limits & decisions
Check these boundaries before designing a live workflow around the connection.
- Each resulting automation run consumes the workspace’s run allowance
- The review queue is an editorial example you configure, not a built-in Unify approval feature
- Repeated or concurrent arrivals require deliberate duplicate handling
- No live delivery, record creation, or approval workflow has been tested
What the connection supports
Understand the connection, the data involved, and the behavior that matters for a Unify + Airtable workflow.
POST / JSON
| Decision | What to know |
|---|---|
| Direction | Unify → Airtable[1] |
| Receiver | When webhook received automation trigger[3] |
| Record creation | A separate Create record action maps input values into table fields[4] |
| Matching | Find records can query the base using a dynamic condition[5] |
| Completion | Inspect the automation run and its action results[6] |
Technical setup reference
References and requirements for the Airtable connection.
Connection requirements and setup checklist
Before connecting
- A Unify Play with a Webhook action
- Owner or Creator permission in the target Airtable base
- A destination table with prospect fields and a proposed review status
Prepare the review queue
Create fields for name, email, company, domain, and review status in the destination table. Choose who will review new entries. These are suggested fields for this example.[4]
Create the receiving trigger
In Airtable Automations, add When webhook received and copy its URL.[3]
Create the review record
Add Create record, select the table, and map the trigger values to its fields. Set a static review status such as Needs review. Test the action, inspect the row, then turn on the automation when ready.[4]
Request configuration
- Method
POST- URL pattern
https://hooks.airtable.com/workflows/v1/genericWebhook/YOUR_GENERATED_PATH- Headers
Content-Type: application/json- Authentication
- Use authentication None for this trigger. Keep its generated URL private; anyone with it can trigger the automation.
Choose JSON as the body format. Unify sets Content-Type automatically. The receiver must respond within Unify’s 8-second timeout; request responses are not passed to later Play steps.[2]
Replace URL placeholders with the actual receiver URL from your account or deployed application. These example URLs are not working endpoints.
Example handoff payload
Start with a fictional prospect. Validate the resolved values before using a real record.
Inspect the sample payload and field mapping
{
"event": "prospect_handoff",
"prospect_name": "Alex Morgan",
"prospect_email": "alex@example.com",
"company_name": "Example Company",
"company_domain": "example.com"
}Fictional data. Replace sample values before using a real Play.
The keys are an example handoff format, not required Unify field names. Use the field mapping to distinguish record data from fixed settings. Select available fields in your Play and inspect Expand preview; do not replace configuration values with prospect data.[2]
| Payload field | Value to send |
|---|---|
event | A fixed label you choose for this workflow |
prospect_name | Use {{ person.first_name }} and {{ person.last_name }} for the prospect name |
prospect_email | Use {{ person.email }}; decide how to handle missing values |
company_name | Use {{ company.name }} |
company_domain | Use {{ company.domain }} |
In Create record, map prospect_name to Name, prospect_email to Email, company_name to Company, and company_domain to Domain. These column names are suggestions; select the actual fields in your base.
Troubleshooting
Start with the stage where the expected data or action stops appearing.
The request is rejected
Check POST, application/json, and a top-level JSON object. Keep the payload below 100 KB and traffic within five requests per second.[3]
Sources & review
Official documentation reviewed on September 15, 2026.
Technical claims link to primary documentation from Unify and the destination tool. Scenarios, field choices, and recovery plans are editorial implementation examples. Documentation review is separate from execution testing.
Documentation reviewed; end-to-end execution not tested. No named technical reviewer has signed off on these articles yet.
Content updated: . Report a correction to Unify with the tool name, source URL, and behavior you observed.
Keep exploring
