Build an Endpoint to Perform CRUD Operations with Multiple HTTP Methods

This n8n workflow demonstrates how to create a versatile API endpoint that can handle different HTTP methods (GET, POST, PUT, DELETE) to perform CRUD (Create, Read, Update, Delete) operations, likely interacting with an external data source like Airtable.

What it does

This workflow provides a foundational structure for building a robust API endpoint:

1. Listens for incoming HTTP requests: It uses a Webhook node to act as a listener for various HTTP methods.
2. Provides a placeholder for data interaction: An Airtable node is included, suggesting that the workflow is designed to interact with an Airtable base for its CRUD operations.
3. Sends a response back to the caller: The "Respond to Webhook" node is ready to send a customized response based on the outcome of the operations.
4. Includes a Sticky Note for documentation: A sticky note is present, indicating that the workflow is designed with internal documentation in mind, likely to explain the logic for different HTTP methods.

Prerequisites/Requirements

• n8n Instance: You need a running n8n instance to import and execute this workflow.
• Airtable Account: An Airtable account and a configured Airtable credential in n8n are required if you intend to use the Airtable node for data storage.
• Basic API Knowledge: Understanding of HTTP methods (GET, POST, PUT, DELETE) and API concepts will be beneficial.

Setup/Usage

1. Import the workflow:
   • Copy the provided JSON code.
   • In your n8n instance, click "New" to create a new workflow.
   • Go to "File" > "Import from JSON" and paste the code.
2. Configure the Webhook Trigger:
   • Click on the "Webhook" node.
   • The "Webhook URL" will be automatically generated once you save and activate the workflow. This URL will be your API endpoint.
   • You will likely need to configure the "HTTP Method" to "All" or add conditional logic (e.g., an "IF" node) after the Webhook to branch based on the incoming HTTP method (GET, POST, PUT, DELETE) and then perform the corresponding Airtable operation.
3. Configure Airtable (if used):
   • Click on the "Airtable" node.
   • Select your Airtable credential or create a new one.
   • Configure the "Base ID", "Table Name", and the specific "Operation" (e.g., "Create", "Get", "Update", "Delete") based on the HTTP method received by the Webhook.
4. Configure Respond to Webhook:
   • Click on the "Respond to Webhook" node.
   • Customize the "Response Data" and "Status Code" to provide meaningful feedback to the API caller.
5. Add Logic for Different HTTP Methods:
   • Currently, the workflow only shows a basic connection. To handle multiple HTTP methods, you would typically add an "IF" node after the "Webhook" node.
   • The "IF" node would check {{$json.headers["x-n8n-http-method"]}} (or similar depending on how the method is passed) to determine the incoming HTTP method.
   • Based on the method, you would connect different branches, each leading to a specific Airtable operation (e.g., GET for reading, POST for creating, PUT for updating, DELETE for deleting).
6. Activate the workflow: Once configured, activate the workflow by toggling the switch in the top right corner of the n8n editor.
7. Test the endpoint: Use an API client (like Postman, Insomnia, or curl) to send requests to the generated Webhook URL with different HTTP methods and payloads to test its functionality.

This workflow serves as a starting point. You will need to expand the logic with conditional nodes and additional Airtable operations to fully implement CRUD functionality for each HTTP method.