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 to perform various operations on different resources such as deals, organizations, people, tasks, funnels, products, users, and system data. Specifically for the Pessoa (Person) resource and the Atualizações Recentes (stream) operation, it fetches records of people updated since a specified date.
This functionality is useful for workflows that need to synchronize or process recently changed contact information, trigger actions based on updates to person records, or keep external systems in sync with the latest CRM data.
Practical example:
A user can set this node to retrieve all people updated since yesterday and then use the data to update a mailing list or notify a sales team about recent changes.
Properties
| Name | Meaning |
|---|---|
| Data Inicial | The starting date/time from which to fetch people records updated since this timestamp. |
Output
The node outputs an array of JSON objects representing the people records retrieved from Agendor CRM that have been updated since the specified date. Each object contains the fields returned by the Agendor API for a person, including standard and optionally custom fields if requested.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Agendor CRM API.
- The node uses HTTP requests to Agendor's REST API endpoints.
- No additional environment variables are needed beyond the API authentication setup.
Troubleshooting
Common issues:
- Incorrect or missing API credentials will cause authentication failures.
- Providing an invalid or future date in "Data Inicial" may result in no data being returned.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
- Rate limiting or API quota exceeded errors require checking Agendor account limits.
- If the node returns empty results unexpectedly, confirm that the "Data Inicial" parameter is correctly set and that there are indeed updates after that date.
Links and References
- Agendor API Documentation (official API docs for reference on endpoints and data structures)
- n8n Documentation (for general guidance on using n8n nodes and credentials)