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 create new activities or tasks within the CRM system. It is useful for automating the logging of various types of interactions and follow-ups related to sales, customer management, or internal task tracking. Typical scenarios include scheduling calls, sending emails, recording meetings, adding notes, or creating general tasks associated with deals, people, or organizations.
For example, a sales automation workflow could use this node to automatically create a "Call" activity reminding a salesperson to contact a client after a proposal is sent. Another use case might be to log an "Email" activity when a marketing campaign email is sent to a contact.
Properties
| Name | Meaning |
|---|---|
| Activity Type | The type of activity to create. Options: Call (phone call), Email, Meeting, Note, Task (general task). |
| Text | Description or text content of the activity. |
| Date and Time | Optional date and time when the activity is scheduled or occurred. |
| Additional Fields | A collection of optional fields to provide more context or link the activity to other entities: - Address (full address, shown for people and organizations) - CNPJ (organization tax ID number) - CPF (person tax ID number) - Deal ID (ID of related deal) - Description (additional details) - Organization ID (related organization) - Person ID (related person) - Phone (phone number) - User ID (user responsible for the activity) - Website (organization website URL) |
Output
The node outputs JSON data representing the created activity as returned by the Agendor API. This typically includes all properties of the newly created activity such as its unique ID, type, text, datetime, and any linked entities (deal, person, organization, user).
There is no binary output from this node.
Dependencies
- Requires an API authentication token credential for the Agendor CRM API.
- The node makes HTTP POST requests to
https://api.agendor.com.br/v3/activitiesendpoint. - Proper configuration of the API token in n8n credentials is necessary.
Troubleshooting
- Missing Required Fields: If required fields like "Activity Type" or "Text" are not provided, the API will reject the request. Ensure these are always set.
- Invalid IDs: Providing invalid or non-existent IDs for related entities (dealId, personId, organizationId, userId) may cause errors or unexpected behavior.
- Authentication Errors: If the API token is missing, expired, or incorrect, the node will fail with authorization errors. Verify the API key credential.
- Date Format Issues: The "Date and Time" field should be in a valid ISO 8601 format. Invalid dates may cause the API to reject the request.
- API Rate Limits: Excessive requests may trigger rate limiting on the Agendor API side; handle such errors by retrying after some delay.
Links and References
- Agendor API Documentation (official API docs)
- n8n Documentation (for general usage of nodes and credentials)