Airtable integration

Feature Snapshot

Summary:
Airtable Integration enables LeadConduit to query data stored in your Airtable account, enriching and validating lead records by performing a dynamic table lookup.

Key Benefits:

Enrich lead data automatically with external information from Airtable.
Enable dynamic flow decisions based on real-time lookup results.
Centralize supplemental information to reduce manual data entry and improve data accuracy.

Typical Use Cases:

Validating postal codes against a store directory.
Appending store availability or status information to leads.
Filtering leads based on externally maintained data criteria.

How the Airtable Integration works?

The Airtable Integration is implemented as a Table Lookup within LeadConduit. It connects to your Airtable account using a Personal Access Token (PAT) and targets a specific Base ID and Table Name. You configure three key mapping fields:

Search Column Name: The name of the column in your Airtable table to search (for example, “postal_code”).
Search Value: The value to match in that column, typically mapped from a lead field (such as the lead’s postal code).
Result Column Name: The Airtable column from which to retrieve the desired data (for example, “store_available”).

When a lead is processed in your flow, LeadConduit uses these settings to query Airtable and append the resulting data to the lead record, allowing you to drive further flow logic based on this externally enriched information.

Step‑by‑Step Instructions

Open your LeadConduit flow and navigate to Edit Flow.
Click Add to Flow > Integration and search for “Airtable”; then select it.
When prompted, enter your Airtable Personal Access Token (PAT).
Provide your Airtable Base ID and Table Name exactly as they appear in your Airtable account.
Configure the lookup by specifying:
- Search Column Name: Enter the column name to search (e.g., “postal_code”).
- Search Value: Map this field with the value to search in the previously identified column; usually with one of your lead attribute (e.g., the lead’s postal code).
- Result Column Name: Enter the column name from which to retrieve the result (e.g., “store_available”).
Save the integration step and drag it into the appropriate position within your flow logic.
Run a test lead to ensure that the lookup returns the expected data and is appended to the lead record.

Expected Result:
The integration queries the designated Airtable table and appends the lookup result (e.g., “true” for an available store, “false” otherwise) to the lead record.

airtable step in a flow

Practical Example

Let’s say you have a call center that receives your leads and redirects them to the closest available store based on their postal code; the list of available stores with their corresponding postal codes is updated weekly in a table hosted by Airtable.

The table is composed of the following columns:

postal_code: Contains each Postal Code that can be addressed to a Store Number
store_number: Contains the Store’s identifier code
store_available: Contains a true or false value that specifies if the Store is available

If you want to send to the Call Center only leads that have a Postal Code that corresponds to a Store that is currently open, you should configure your integration as follows:

Search Column Name is the column’s name to search for the incoming value provided by the lead, in this case, the Postal Code, so we should type postal_code
Result Column Name is the column name from which the corresponding value will be retrieved and sent to LeadConduit; since we want to know if the selected store is open, we should type store_available
Search Value is the value to search in the previously identified column, so here, we should specify the data field provided by the lead, which contains the lead’s Postal Code; usually, the standard Postal Code field contains this information in LeadConduit

Based on that configuration, the integration will look for the provided Postal Code in the specified column and provide you the value under the store_available column in response; so if a store is closed, you’ll get false, and if a store is open, you’ll get true.

airtable event

You will then be able to create filters in your Flow based on those responses.

airtable filter

That will provide the following when the integration’s Result is false:

airtable outcome

Validation & Monitoring (optional)

Test the Setup: Submit test leads with the expected lookup values (e.g., postal codes) and verify in the lead details that the appended data matches the corresponding Airtable record.
Where to Monitor?: Check the LeadConduit Events tab to review the integration’s query responses and track lookup performance; custom reports can also be set up to monitor success versus failure rates.

Best Practices

Verify that your Airtable Personal Access Token, Base ID, and Table Name are entered exactly as they appear in your Airtable account.
Map the Search Value field to a reliable lead attribute to ensure consistent and accurate lookup results.
Test the integration thoroughly with sample leads before deploying it in production.
Use descriptive and consistent column names in Airtable to minimize confusion during troubleshooting.
Regularly review and update your mapping settings as your Airtable table structure evolves.

Troubleshooting

Symptom / Error	Likely Cause	Resolution
No data returned from lookup	Incorrect Base ID, Table Name, or Personal Access Token	Confirm the Airtable credentials and identifiers, and verify that the column names are accurate.
Unexpected or empty lookup value	Wrong Search Column Name or mismatched Search Value mapping	Check that the mapped lead field contains the correct value and adjust the mapping accordingly.
Integration error or timeout message	Network issues or misconfigured API parameters	Validate network connectivity and ensure that all API parameters are correctly configured.
Error indicating “invalid token”	Expired or invalid Personal Access Token (PAT)	Generate a new PAT from Airtable and update the integration settings with the new token.

Frequently Asked Questions (FAQ)

Q: What is the Airtable Personal Access Token (PAT) used for?
A: The PAT is used to securely authenticate API requests from LeadConduit to your Airtable account, ensuring that only authorized connections retrieve data.

Q: How do I find my Airtable Base ID and Table Name?
A: You can locate your Base ID and Table Name in your Airtable account. For detailed instructions, refer to Airtable’s support documentation at https://support.airtable.com/docs/finding-airtable-ids.

Q: What happens if the lookup does not find a matching record?
A: If no match is found, the integration returns an empty result. This outcome can be used in your flow’s logic to handle cases where external data is unavailable.

Q: Can I use dynamic values for the Search Value field?
A: Yes, it is recommended to map the Search Value to a dynamic lead field (such as postal code), ensuring that each lead triggers a lookup based on its specific data.

Glossary

Term	Definition
Airtable	A cloud-based platform that combines spreadsheet functionality with database capabilities.
Personal Access Token	A secure token generated by Airtable to authenticate API requests from external applications.
Base ID	The unique identifier of an Airtable base that contains the tables used for lookups.
Table Name	The specific name of the table in an Airtable base where your lookup data is stored.
Search Column Name	The column in the Airtable table that is searched for a match based on the supplied value.
Search Value	The value, typically mapped from lead data, that is used to search the specified Airtable column.
Result Column Name	The column in the Airtable table from which the lookup result is retrieved and appended to the lead.