Rvops icon

Rvops

Integração Rvops

Actions40

Overview

This node integrates with the Rvops platform to manage notes associated with various objects such as contacts or deals. Specifically, the "Create a Note" operation allows users to add a new note to an existing object (either a contact or a deal) within Rvops. The note can be of different types like email, call, meeting, WhatsApp, or general notes.

Common scenarios where this node is beneficial include:

  • Automatically logging communications or remarks related to a contact or deal during workflow automation.
  • Adding contextual information or updates to CRM records without manual entry.
  • Tracking interactions and activities for sales or support teams.

For example, after a customer call, a workflow could use this node to create a "call" type note on the relevant contact record summarizing the discussion.

Properties

Name Meaning
Autenticação Do Cliente Method of client authentication; currently supports "Access Token".
Nota Para O Objeto The object type to which the note will be attached; options: "Contato" (contact), "Negócio" (deal).
ID Do Objeto a Ser Criada a Nota Numeric ID of the object (contact or deal) where the note will be created.
Tipo De Nota Type of the note; options: "Email", "Geral" (general), "Ligação" (call), "Reunião" (meeting), "WhatsApp".
Descrição Text description/content of the note.
Proprietário Name or ID Owner of the note; selectable from a list or specified by expression.

Note: Other properties listed in the full property set relate to other resources or operations and are not relevant for the "Create a Note" operation.

Output

The output JSON contains the newly created note's data as returned by the Rvops API. It includes all properties of the note such as its ID, type, text content, owner, and timestamp.

Example structure of the output JSON:

{
  "id": "note_id",
  "properties": {
    "type": "email",
    "text": "Note content here",
    "owner": "owner_id",
    "timestamp": "2024-06-01T12:34:56.000Z"
  }
}

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Rvops API.
  • The node uses internal helper methods to make HTTP requests to the Rvops endpoints.
  • No additional external services beyond Rvops are required.

Troubleshooting

  • Invalid Object ID: If the provided object ID does not exist or is invalid, the API will return an error. Verify that the ID corresponds to an existing contact or deal.
  • Missing Required Fields: The note type, text, owner, and target object must be provided. Omitting these will cause errors.
  • Authentication Errors: Ensure the API token used is valid and has sufficient permissions to create notes.
  • Timestamp Handling: The node generates a UTC timestamp at execution time. System clock issues might affect this value.
  • API Rate Limits: Excessive calls may trigger rate limiting; implement retries or delays if needed.

Links and References

Discussion