Actions33
- Campaign Actions
- Contact Actions
- Field Actions
- Opt-In Actions
- Opt-in-Case Actions
- Sign in Form Actions
- Storage-Field Actions
- Tag Actions
Overview
The node integrates with the 4leads platform to manage contact data by setting values for specified global fields on contacts. It supports setting a single field or multiple fields at once on a contact record. This is useful in scenarios where you want to update contact information dynamically, such as updating user preferences, status flags, or custom attributes based on workflow logic.
Practical examples:
- Updating a contact's subscription status after a form submission.
- Setting multiple profile fields for a contact imported from another system.
- Triggering automated processes by changing specific contact field values.
Properties
Name | Meaning |
---|---|
Set Multiple Fields | Boolean option to enable setting multiple fields at once (true) or just a single field (false). |
Global Field | When setting a single field, select the global field to update. Can be chosen from a searchable list or entered by ID. |
Contact | Select the contact whose field(s) will be updated. Can be selected from a searchable list or specified by ID. |
Value | The value to set for the selected global field when setting a single field. |
Do Triggers | Whether to enable automatic triggers that listen to value changes for the field(s). When true, any workflows or automations tied to field changes will be activated. |
Overwrite | Whether to overwrite existing values in the field(s). If false, existing values will not be changed. |
Fields to Set | When setting multiple fields, this collection allows specifying up to 20 fields. Each entry includes: - Global Field: The field to update. - Value: The value to set. - Do Triggers: Enable triggers for this field. - Overwrite: Enable overwriting existing values. |
Output
The node outputs an array of JSON objects representing the results of the set value operations performed on the contact(s). Each object typically contains details about the updated contact fields and their new values.
If binary data were involved (not indicated here), it would represent attachments or files related to the contact, but this node focuses on JSON data updates only.
Dependencies
- Requires an API key credential for authenticating with the 4leads platform.
- Needs network access to the 4leads API endpoints.
- The node depends on internal handlers for contacts and global fields within the bundled code.
Troubleshooting
- Invalid Global Field ID: If the global field ID does not match the expected numeric format, the node will reject the input. Ensure IDs are numeric strings.
- Contact Not Found: Selecting a contact by ID that does not exist or is inaccessible will cause errors. Use the list mode to pick valid contacts.
- Overwrite Disabled: If overwrite is false and the field already has a value, the node will skip updating that field. Verify if overwriting is intended.
- Triggers Not Firing: If "Do Triggers" is disabled, downstream automations depending on field changes will not activate. Enable this option if needed.
- API Authentication Errors: Ensure the API key credential is correctly configured and has sufficient permissions.
Links and References
- 4leads Official Documentation (hypothetical link)
- n8n Documentation on Creating Custom Nodes
- General info on Global Fields in 4leads (hypothetical link)