Turn your Airtable base into a simple customer data API. Capture new contacts, list all customers, look up one by ID, update details, or remove records. Ideal for teams that want a fast way to manage customer records without building a full backend.

Two webhook endpoints handle the work. One endpoint accepts requests to create new records and to return all rows from your Airtable table. The second endpoint uses a path ID to search by customer_id and then fetch, update, or delete the matching record. The flow uses Airtable nodes for create, search, update, and delete, and Respond to Webhook nodes to send clear replies. New records return status 201 with the created item. Reads, updates, and deletes return status 200 with the data so your app can use the response right away.

Setup is simple. You need an Airtable base and a personal access token. Map your table fields to match the expected inputs like email, phone, address, first_name, and last_name, and send requests to the provided webhook URLs. Teams can cut manual spreadsheet edits and speed up onboarding. Common uses include website forms that add leads to Airtable, support tools that look up or change a customer by ID, and admin panels that can remove outdated records.

• Two webhook endpoints power collection level and record level actions
• Create node maps query fields like email and phone into Airtable columns
• Get All node retrieves all records from the selected Airtable table
• Get Single node searches by customer_id using a filter formula and returns one match
• Update path modifies existing records after looking up the correct record ID
• Delete path removes a record after confirming the ID from a search step
• Respond to Webhook nodes return structured data with proper status codes including 201 for created

• Reduce manual record entry from hours to minutes by sending form data straight into Airtable
• Streamline customer data handling by up to 70 percent with clear endpoints for create, read, update, and delete
• Improve data accuracy by up to 90 percent by removing copy and paste between tools
• Speed developer integration with consistent HTTP 201 and 200 responses
• Handle five times more submissions by replacing spreadsheet logins with API calls

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Airtable. See the Tools Required section above for links to create accounts with these services.
3. In Airtable, create or choose a base and table for customer records. Add fields such as customer_id, first_name, last_name, email, phone, and address.
4. In your Airtable account, create a personal access token with read and write permissions for the target base. Copy the token to a safe place.
5. In n8n, open Credentials > New > search for Airtable. Create a new Airtable Token credential and paste your personal access token. Give the credential a clear name.
6. Open each Airtable node in the workflow and select your Airtable credential. Pick your base and table or paste the IDs. Confirm field names match your Airtable schema.
7. Review the Create node field mapping. It expects inputs from query parameters like email, phone, address, first_name, and last_name. Update mappings if your column names differ.
8. Open each Webhook node and copy the Production URL. One URL handles create and list actions. The other URL includes a path with an ID parameter for get, update, and delete actions.
9. Test create: send a POST request to the create URL with query parameters for the fields. Confirm the response code is 201 and the new row appears in Airtable.
10. Test list: send a GET request to the list URL. Confirm you receive status 200 and a list of records.
11. Test get one: send a GET request to the ID URL and include the customer_id in the path. Confirm you receive status 200 and one record.
12. Test update and delete on the ID URL using the correct HTTP method and body fields. Verify status 200 and confirm the change in Airtable.
13. Troubleshoot: if responses are empty, check that customer_id exists in Airtable and matches the path value. Confirm your Airtable token has access to the base and that field names match exactly.