Actions68
- Email Actions
- File Actions
- Note Actions
- Product Category Actions
- Task Actions
- Address Actions
- Company Actions
- Custom Record Actions
- Deal Actions
- Deal Item Actions
- Person Actions
- Phone Actions
- Product Actions
Overview
The node integrates with Arivo CRM to manage various CRM data entities. Specifically, for the Email - Get operation, it retrieves detailed information about a specific email associated with a contact in Arivo CRM. This is useful when you want to fetch and use email details (such as subject, body, sender, recipients, timestamps) within an automated workflow.
Common scenarios include:
- Fetching an email record to display or process its content.
- Using email metadata to trigger further actions or updates in other systems.
- Auditing or logging email communications related to contacts.
Example: Given a Contact ID and Email ID, the node fetches the corresponding email's full details from Arivo CRM, enabling downstream nodes to utilize this data.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact to which the email belongs. |
| Email ID | The unique identifier of the email record to retrieve from Arivo CRM. |
Output
The output is a JSON object representing the retrieved email record. It typically includes fields such as:
- Email metadata (e.g., subject, sender, recipients, date/time).
- Email content/body.
- Associated contact information.
- Any additional custom fields defined in Arivo CRM for emails.
The exact structure depends on the Arivo CRM API response but generally provides comprehensive email details.
This node does not output binary data.
Dependencies
- Requires an active connection to Arivo CRM via an API key credential configured in n8n.
- The node depends on the Arivo CRM API being accessible and the provided Contact ID and Email ID being valid.
- No additional external dependencies beyond the configured API authentication.
Troubleshooting
- Invalid Contact ID or Email ID: If either ID is incorrect or does not exist, the node will likely throw an error indicating the resource was not found. Verify IDs before running.
- Authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions to read email records.
- API rate limits or connectivity issues: Network problems or API throttling may cause failures; retry or check API status.
- Continue On Fail: If enabled, the node will return error messages in the output JSON instead of stopping execution, allowing workflows to handle errors gracefully.
Links and References
- Arivo CRM Official Documentation (replace with actual URL if known)
- n8n Documentation on Creating Custom Nodes
- General info on CRM Email Management