Rvops icon

Rvops

Integração Rvops

Actions40

Overview

This node integrates with the Rvops platform to manage various CRM-related resources such as contacts, deals, companies, products, tasks, notes, users, associations, properties, and segments. Specifically, for the "Segmento" resource and the "Add One Contact to Segment" operation, the node allows you to add a single contact to a specified segment by their IDs.

This operation is useful in scenarios where you want to programmatically organize or categorize contacts into segments for targeted marketing campaigns, reporting, or workflow automation. For example, after qualifying a lead, you might add that contact to a "Qualified Leads" segment automatically.

Properties

Name Meaning
Autenticação Do Cliente Authentication method; currently supports "Access Token".
ID Do Segmento The unique numeric ID of the segment to which the contact will be added (required).
ID Do Contato The unique numeric ID of the contact to be added to the segment (required).

Note: The other properties listed in the provided JSON are related to sorting lists, creating properties, and other operations not relevant to the "Add One Contact to Segment" operation.

Output

The output of this operation is a JSON object representing the result of adding the contact to the segment. It typically includes confirmation details returned from the API about the updated segment or contact association.

The output is wrapped in n8n's standard execution metadata format, allowing it to be used seamlessly in subsequent workflow nodes.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authentication (referred generically as an API access token).
  • Depends on the Rvops API endpoint to perform the segment-contact association.
  • No additional environment variables or external services are explicitly required beyond the API access token.

Troubleshooting

  • Common Issues:

    • Providing invalid or non-existent segment or contact IDs will likely cause API errors.
    • Missing or incorrect authentication token will result in authorization failures.
    • Network connectivity issues can prevent successful API calls.

  • Error Messages:

    • Errors returned from the API include HTTP status codes and messages indicating the problem (e.g., 404 Not Found if the segment or contact does not exist).
    • If the node is set to continue on failure, error details are included in the output JSON under an error field with message and status.

  • Resolution Tips:

    • Verify that the segment ID and contact ID are correct and exist in the system.
    • Ensure the API access token is valid and has sufficient permissions.
    • Check network connectivity and API endpoint availability.

Links and References

Discussion