Actions12
Overview
This node allows you to create a new "Request" in Accelo via its API. It is designed for scenarios where you need to automate the creation of support tickets, service requests, or similar items within your Accelo workspace. For example, you could use this node to automatically generate a request when a customer submits a form, or when an issue is detected in another system.
Properties
| Name | Meaning |
|---|---|
| Request Title | The title of the Request. This is a required text field that describes the subject or summary of the request. |
| Request Body | The body of the Request. This is a required multi-line text field where you provide detailed information about the request. |
| Type Name or ID | Choose from a list of available request types, or specify a type ID using an expression. This determines the category or template for the request. |
| Affiliation | The affiliation of the Request. This is a required numeric field indicating which affiliation (e.g., client, department) the request is associated with. |
Output
The output will be a JSON object representing the newly created Request in Accelo. The structure typically includes fields such as:
{
"id": 123,
"title": "Example Request",
"body": "Details about the request...",
"type_id": 5,
"affiliation_id": 42,
// ...other fields returned by the Accelo API
}
The exact fields may vary depending on the Accelo API response.
Dependencies
- External Service: Requires access to the Accelo API.
- API Credentials: You must configure valid Accelo API credentials in n8n under the name
acceloApi. - n8n Configuration: No additional environment variables are required beyond standard credential setup.
Troubleshooting
- Missing Required Fields: If you do not provide all required properties (Title, Body, Type, Affiliation), the node will likely throw an error indicating missing parameters.
- Invalid Type or Affiliation: Providing an invalid Type ID or Affiliation ID may result in an error from the Accelo API, such as "Invalid type_id" or "Affiliation not found."
- Authentication Errors: If your API credentials are incorrect or expired, you may see errors like "401 Unauthorized" or "Invalid API key."
How to resolve:
- Double-check that all required fields are filled and valid.
- Ensure your Accelo API credentials are correctly configured in n8n.
- Use the "Type Name or ID" dropdown to select a valid type, or verify the ID if using an expression.