Actions19
- Negócio Actions
- Empresa Actions
- Pessoa Actions
- Tarefa Actions
- Produto Actions
- Usuário Actions
- Sistema Actions
Overview
This node integrates with the Agendor CRM platform, enabling automation workflows to manage various CRM entities. Specifically, for the Tarefa (Task) resource with the Criar (Create) operation, it allows users to create new tasks in Agendor by specifying a title and optional additional details.
Typical use cases include:
- Automatically creating follow-up tasks after a deal is updated.
- Scheduling reminders or action items based on triggers from other systems.
- Creating tasks programmatically as part of a sales or customer support workflow.
For example, you might use this node to create a task titled "Call client for feedback" with an optional description and contact information, which then appears in the Agendor task list.
Properties
| Name | Meaning |
|---|---|
| Título (title) | The title of the task to be created. This is a required string field. |
| Campos Adicionais (additionalFields) | A collection of optional fields to add more details to the task: - Descrição (description): Text description of the task. - Valor (value): Numeric value in Brazilian reais (used mainly for deals but available here). - E-mail (email): Email address related to the task. - Telefone (phone): Phone number related to the task. |
Output
The node outputs JSON data representing the newly created task as returned by the Agendor API. This typically includes all task properties such as its unique ID, title, description, and any other fields set during creation.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Agendor CRM API.
- Needs an API authentication credential configured in n8n to authorize requests.
- The node uses internal helper functions to make HTTP requests to Agendor endpoints.
Troubleshooting
Common issues:
- Missing or invalid API credentials will cause authentication errors.
- Providing incomplete or invalid input data (e.g., empty title) may result in API validation errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication failures usually indicate incorrect or missing API keys; verify your credential setup.
- Validation errors from the API will specify which fields are missing or malformed; ensure required fields like "Título" are provided.
- Rate limiting or server errors from Agendor should be retried later or handled with error workflows.
Links and References
- Agendor CRM Official Website
- Agendor API Documentation (for detailed API endpoint info)
- n8n documentation on Creating Custom Nodes