Actions14
- Item Actions
- Project Actions
- Other Actions
Overview
This node allows users to interact with the SwipeFlow API, specifically providing a generic API call operation under the 'Other' resource. It enables making arbitrary HTTP requests (GET, POST, PUT, PATCH, DELETE) to any endpoint within the SwipeFlow API, allowing flexible and advanced usage beyond predefined operations. This is useful for users who need to perform custom API requests that are not covered by the standard operations, such as accessing new or less common endpoints, or performing complex queries and updates.
Use Case Examples
- Making a GET request to retrieve data from a specific endpoint within a project.
- Sending a POST request with a JSON body to create or update resources in SwipeFlow.
- Using query parameters to filter or paginate results from the API.
Properties
| Name | Meaning |
|---|---|
| Project Name or ID | Select a project from your SwipeFlow account to scope the API request. You can choose from a list or specify an ID using an expression. |
| HTTP Method | The HTTP method to use for the API request, such as GET, POST, PUT, PATCH, or DELETE. |
| Endpoint | The API endpoint path after /v1/, for example, projects/{projectId}/items, specifying the resource to interact with. |
| Body (JSON) | The JSON-formatted request body for POST, PUT, or PATCH requests, containing data to send to the API. |
| Query Parameters (JSON) | JSON-formatted query parameters to include in the API request URL for filtering, pagination, or other purposes. |
Output
JSON
json- The JSON response from the SwipeFlow API corresponding to the requested resource or action.
Dependencies
- SwipeFlow API
- API authentication token (credential)
Troubleshooting
- Ensure the project ID is valid and accessible in your SwipeFlow account to avoid authorization errors.
- Verify the HTTP method and endpoint path are correct and supported by the SwipeFlow API to prevent 404 or method not allowed errors.
- Check the JSON syntax in the Body and Query Parameters fields to avoid malformed request errors.
- Handle API rate limits or network issues that may cause request failures by implementing retries or error handling in your workflow.
Links
- n8n Expressions Documentation - Guide on using expressions to dynamically specify property values.
- n8n Expressions Documentation - Guide on using expressions to dynamically specify property values.