Actions40
- Associação Actions
- Contato Actions
- Empresa Actions
- Negócio Actions
- Nota Actions
- Produto Actions
- Propriedade Actions
- Segmento Actions
- Tarefa Actions
- Usuário Actions
Overview
The node integrates with the Rvops platform, specifically enabling operations on various resources including contacts, deals, companies, products, users, notes, tasks, associations, properties, and segments. For the Segmento resource with the Create a Segment operation, this node allows users to create a new segment in Rvops by specifying its name, description, and optionally adding contacts to it based on provided contact IDs.
This node is beneficial when you want to programmatically organize contacts into segments for targeted marketing, reporting, or workflow automation within Rvops. For example, you can create a segment named "VIP Customers" and add specific contacts to it automatically from your workflow.
Properties
| Name | Meaning |
|---|---|
| Autenticação Do Cliente | Authentication method; currently supports "Access Token". |
| Nome | The name of the segment to be created. (Required) |
| Descricão | A description of the segment. |
| Adicionar Contatos Ao Segmento | Optionally add contacts to the segment by specifying their contact IDs. |
Details on "Adicionar Contatos Ao Segmento"
- This is a fixed collection allowing multiple values.
- Each entry requires an "ID Do Contato" (Contact ID), which must be a positive integer.
- These contact IDs will be added to the newly created segment.
Output
The output JSON contains the details of the created segment:
id: The unique identifier of the created segment.properties: An object containing the segment's properties such asnameanddescription.- If contacts were added, the response may also include information about those associations.
The output is structured as an array of items, each representing one execution input item processed, enriched with metadata for n8n workflow use.
Dependencies
- Requires an API key credential for authentication (referred generically as an API access token).
- Relies on the Rvops REST API endpoints for segments (
POST /segments). - No additional external dependencies are required beyond standard HTTP request capabilities.
Troubleshooting
- Authentication errors: Ensure the provided access token is valid and has permissions to create segments.
- Invalid contact IDs: Adding contacts requires valid numeric contact IDs; invalid or non-existent IDs may cause errors.
- Missing required fields: The segment name is mandatory; omitting it will result in an error.
- API rate limits or connectivity issues: Network problems or API throttling can cause failures; retry or check API status.
- Error messages: The node returns error details including message and status code in the output if
continueOnFailis enabled.
Links and References
- Rvops API Documentation (generic placeholder, replace with actual URL)
- n8n documentation on Creating Custom Nodes
- General REST API usage best practices
If you need further details on other operations or resources, feel free to ask!
