Agendor icon

Agendor

Trabalhe com dados da API do Agendor CRM
Join our community

Actions34

Overview

This node integrates with the Agendor CRM API to update an existing activity record. It allows users to modify details such as the type of activity (call, email, meeting, note, or task), descriptive text, scheduled date and time, and various related entity IDs (deal, person, organization, user). This is useful for keeping activity records current in a sales or customer relationship management workflow.

Typical use cases include:

  • Updating the status or description of a scheduled call or meeting.
  • Changing the assigned user responsible for an activity.
  • Adding or modifying links between activities and deals, people, or organizations.
  • Adjusting the scheduled date/time of a task or note.

Example: A sales rep wants to update the notes and reschedule a follow-up call activity linked to a specific deal and contact person.

Properties

Name Meaning
Activity ID The unique identifier of the activity to update (required).
Activity Type The type/category of the activity. Options: Call, Email, Meeting, Note, Task (required).
Text The main text or description of the activity (required).
Date and Time Optional date and time when the activity is scheduled.
Additional Fields A collection of optional fields to provide more context or link the activity to other entities:
- Address (for people or organizations)
- CNPJ (organization tax ID)
- CPF (person tax ID)
- Deal ID (related deal)
- Description (additional details)
- Organization ID (related organization)
- Person ID (related person)
- Phone (contact number)
- User ID (user responsible for the activity)
- Website (organization website)

Output

The node outputs the updated activity data in JSON format. This typically includes all the fields of the activity after the update, reflecting the new values set by the user. The output can be used downstream in workflows to confirm changes or trigger further actions.

No binary data output is involved.

Dependencies

  • Requires an API authentication token credential for the Agendor CRM API.
  • The node makes HTTP PUT requests to the endpoint /activities/{activityId} on the Agendor API base URL.
  • Proper configuration of the API token in n8n credentials is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing Activity ID will cause the update to fail.
    • Providing invalid field values (e.g., wrong date format, invalid IDs) may result in API errors.
    • Insufficient permissions or expired API token can lead to authorization errors.

  • Error messages and resolutions:

    • 404 Not Found: The specified Activity ID does not exist. Verify the ID is correct.
    • 401 Unauthorized: API token is missing or invalid. Check credential setup.
    • 400 Bad Request: One or more fields have invalid values. Review input data for correctness.
    • 422 Unprocessable Entity: Required fields are missing or constraints violated. Ensure required properties like Activity Type and Text are provided.

Links and References

Discussion