Accelo

Overview

This node interacts with the Accelo API to retrieve contract information based on user-defined search terms and filters. It is particularly useful for workflows that need to fetch, filter, or process contract data from Accelo, such as generating reports, syncing contract details with other systems, or automating contract-related tasks.

Example scenarios:

• Searching for contracts by title.
• Filtering contracts by type or status.
• Retrieving a specific contract using its ID.

Properties

Output

The output will be a JSON object (or array of objects) representing the contract(s) matching the specified search and filter criteria. Each object typically contains contract details such as ID, title, type, status, and other relevant fields as provided by the Accelo API.

Note: If the Accelo API returns binary data for contracts (unlikely in this context), it would be included as a binary property.

Dependencies

• External Service: Requires access to the Accelo API.
• Credentials: An n8n credential named acceloApi must be configured with valid authentication details.
• Environment: No special environment variables are required beyond standard n8n setup.

Troubleshooting

Common issues:

• Invalid credentials: If the acceloApi credential is missing or incorrect, authentication errors will occur.
• No results found: If the search term or filters do not match any contracts, the output will be empty.
• Invalid filter values: Providing non-existent IDs or invalid options may result in API errors.

Error messages and resolutions:

• 401 Unauthorized: Check your Accelo API credentials in n8n.
• 400 Bad Request: Review your filter values for correctness (e.g., ensure IDs exist).
• Network/connection errors: Ensure n8n can reach the Accelo API endpoint.

Links and References

• Accelo API Documentation
• n8n Expressions Guide
• n8n Credentials Setup