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 Deal - Create operation allows users to create a new deal record in their Agendor account. This is useful for automating sales pipelines by programmatically adding new business opportunities as they arise, such as when a lead expresses interest or a quote is sent.
Practical examples include:
- Automatically creating a deal when a form is submitted on a website.
- Adding deals from other sales tools or marketing platforms into Agendor.
- Creating deals based on triggers from email campaigns or customer interactions.
Properties
| Name | Meaning |
|---|---|
| Title | The title or name of the deal (e.g., "Venda de Software - Empresa ABC"). Required. |
| Value | The monetary value of the deal in centavos (e.g., 1000 = R$ 10,00). |
| Additional Fields | A collection of optional fields to provide more details about the deal. These include: |
| - Address | Full address (only shown for people and organizations resources). |
| - CNPJ | Organization's CNPJ number (Brazilian company tax ID, numbers only). |
| - CPF | Person's CPF number (Brazilian individual tax ID, numbers only). |
| - Deal ID | Related deal ID for activities resource. |
| - Description | Detailed description of the deal. |
| - Organization ID | ID of the related organization (shown for people and deals resources). |
| - Person ID | ID of the person responsible for the deal. |
| - Phone | Phone number (for people and organizations). |
| - User ID | ID of the user responsible for the activity (only for activities resource). |
| - Website | URL of the organization's website (only for organizations resource). |
Note: Some additional fields are conditionally shown depending on the resource context but are available for inclusion in the deal creation request body.
Output
The node outputs the JSON response returned by the Agendor API after creating the deal. This typically includes:
- The newly created deal's unique identifier.
- All submitted fields and their values.
- Metadata such as creation timestamps and related entity IDs.
No binary data output is involved.
Dependencies
- Requires an API token credential for authenticating requests to the Agendor CRM API.
- The base URL used is
https://api.agendor.com.br/v3. - Proper configuration of the API token in n8n credentials is necessary.
Troubleshooting
- Missing required fields: The "Title" field is mandatory. Omitting it will cause the API to reject the request.
- Invalid numeric values: The "Value" must be a non-negative number representing centavos; negative or invalid numbers may cause errors.
- Authentication errors: Ensure the API token credential is correctly set up and has sufficient permissions.
- Field validation: Some fields like CNPJ and CPF expect only numbers; including letters or special characters may cause validation failures.
- API rate limits: Excessive requests might trigger rate limiting; handle retries accordingly.