Actions34
- Activity Actions
- Deal Actions
- Funnel Actions
- Organization Actions
- Person Actions
- Product Actions
- Tag Actions
- User Actions
Overview
This node integrates with the Agendor CRM API to manage deals (business opportunities). Specifically, the "Get" operation for the "Deal" resource retrieves detailed information about a single deal by its numeric ID. This is useful when you want to fetch up-to-date data on a specific sales opportunity within your CRM system.
Common scenarios include:
- Fetching deal details to display in dashboards or reports.
- Using deal data as input for further automation workflows, such as sending notifications or updating related records.
- Integrating deal information into other systems like ERP or marketing platforms.
Example: You have a workflow that triggers when a deal ID is provided, and this node fetches all relevant details about that deal from Agendor CRM to use downstream.
Properties
| Name | Meaning |
|---|---|
| Deal ID | The numeric ID of the deal to retrieve. Example: "12345". This property is required. |
Output
The node outputs the JSON response from the Agendor API representing the deal's data. This typically includes fields such as the deal's title, value, associated person and organization IDs, status, creation and update timestamps, and any other metadata provided by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token credential for Agendor CRM.
- The node makes HTTP GET requests to the Agendor API endpoint
https://api.agendor.com.br/v3/deals/{dealId}. - Proper configuration of the API token in n8n credentials is necessary for successful requests.
Troubleshooting
Common issues:
- Invalid or missing Deal ID: The node requires a valid numeric deal ID; ensure it is provided and correctly formatted.
- Authentication errors: Verify that the API token credential is set up correctly and has sufficient permissions.
- Network or API downtime: Check connectivity and Agendor service status if requests fail.
Error messages:
- 404 Not Found: The specified deal ID does not exist. Confirm the ID is correct.
- 401 Unauthorized: Authentication failed. Recheck the API token credential.
- 400 Bad Request: Possibly due to malformed request parameters; verify the Deal ID format.
Resolving these usually involves verifying input parameters, credentials, and network access.
Links and References
- Agendor API Documentation (official API docs for reference)
- n8n Documentation (for general usage of HTTP and credential nodes)