Multi-Method API Endpoint for CRUD Operations - n8n Workflow

Backend developers needing to quickly prototype an API without writing custom server code.
Users looking for advanced examples of n8n node functionality, specifically multi-method webhooks and routing.
Anyone who uses n8n to connect frontend applications to database backends like Airtable.
Integration specialists searching for powerful n8n templates for custom API deployment and management.

Building robust applications often requires complex APIs that can handle standard CRUD (Create, Read, Update, Delete) operations. This specialized n8n workflow provides a complete solution, abstracting the underlying Airtable database and presenting a standard REST interface via a single n8n trigger. Instead of relying on external coding, this efficient n8n template uses multiple webhook configurations to route incoming traffic based on the HTTP method (GET, POST, PUT, DELETE) and path structure (with or without an ID parameter).

This approach demonstrates the power of the n8n node ecosystem, allowing users to deploy a full-featured API incredibly quickly using only n8n’s native capabilities. It saves time, reduces infrastructure overhead, and provides clear logic flow control within the n8n workflow environment.

This powerful n8n workflow utilizes two key n8n trigger nodes for intelligent routing based on the incoming request path:

1. List and Create Endpoint (/customers): The primary Webhook n8n trigger handles requests that do not target a specific record.

1. Specific Record Endpoint (/customers/:id): This secondary Webhook n8n trigger handles requests targeting an individual customer, identified by the dynamic id parameter.

Every operation in this n8n workflow concludes with a dedicated Respond to Webhook n8n node to ensure appropriate HTTP status codes and responses are returned to the API caller.

This n8n template requires minimal setup beyond importing the JSON and configuring credentials.

1. Import the n8n workflow: Copy the provided JSON data and paste it into your n8n instance via the "New" menu -> "Import from JSON".


2. Airtable Credential Setup: You must have an active Airtable account credential set up in n8n. Replace the existing placeholder credentials with your own active Airtable API token credentials linked to the base.


3. Airtable Base Configuration: Verify and update the Base ID and Table Name in all six Airtable n8n node instances to point to your specific customer database setup.


4. Activate the n8n trigger: Save and activate the n8n workflow. The Webhook URLs will now be live and ready to receive API requests for full CRUD operations.

Webhook (n8n trigger):
Function: Serves as the primary n8n trigger for LIST (GET) and CREATE (POST) operations on the base path (/customers). It leverages internal n8n routing logic based on the incoming HTTP method.
Key Configuration: Configured for multipleMethods: true and uses the response from subsequent nodes (responseMode: responseNode).
Webhook (with ID) (n8n trigger):
Function: The secondary n8n trigger that handles specific record operations (GET, PUT, DELETE) using the dynamic path /customers/:id.
Key Configuration: Explicitly allows GET, DELETE, and PUT methods, enabling precise control over the API interface within the n8n workflow.
Airtable (Create n8n node):
Function: Executes the CREATE operation. It maps incoming query parameters (like email, firstname, customerid) received by the n8n trigger directly to the Airtable fields.
Airtable (Get Single n8n node):
Function: Performs targeted search operations for retrieving a single record. It uses an advanced formula filter: =({customerid} = {{ $json.params.id }}) to ensure only the requested record matching the URL parameter is retrieved by this n8n node.
Airtable (Update n8n node):
Function: Updates an existing record. It uses customerid as the matching column to identify the row and updates fields using data provided in the API request.
Airtable (Delete n8n node):
Function: Deletes a record found by the preceding search step.
Respond to Webhook (n8n node):
Function: Essential for closing the synchronous API call. This n8n node returns data and sets appropriate HTTP status codes (e.g., 201, 200) crucial for proper API behavior, finalizing the execution of the entire n8n workflow.