Actions4
- List Actions
- Activity Actions
Overview
This node integrates with the SalesBlink API to add one or more contacts to a specified list within SalesBlink. It is useful for automating contact management workflows, such as importing leads collected from various sources into targeted email lists for marketing campaigns or sales outreach.
Typical use cases include:
- Automatically adding new leads captured from web forms or CRM systems into SalesBlink lists.
- Bulk importing multiple contacts with detailed information and custom fields.
- Ensuring no duplicate contacts are added by optionally removing duplicates during import.
For example, a marketing automation workflow could collect contact details from a landing page and then use this node to add those contacts to a specific SalesBlink list for follow-up email sequences.
Properties
Name | Meaning |
---|---|
List ID | The unique identifier of the SalesBlink list where contacts will be added. |
Contacts | One or more contacts to add, each with optional fields: City, Company Name, Country, Department, Email (required), First Name, Job Title, Last Name, Office Phone, Phone, State, Street, Website. |
Custom Fields | Additional custom contact fields defined by name and value pairs to extend contact data. |
Remove Duplicates | Boolean flag indicating whether to remove duplicate contacts when adding them to the list. |
Output
The node outputs an array of JSON objects representing the response from the SalesBlink API after attempting to add the contacts. Each object corresponds to a contact addition result or error message if applicable.
The output json
field contains the parsed API response, which typically includes details about the added contacts or any errors encountered.
This node does not output binary data.
Dependencies
- Requires an active connection to the SalesBlink API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The base URL used for API calls is
https://run.salesblink.io/api/public
.
Troubleshooting
Common issues:
- Invalid or missing List ID can cause the API to reject the request.
- Missing required contact email addresses will prevent contacts from being added.
- Network or authentication failures may occur if the API key credential is invalid or expired.
Error messages:
- Errors returned from the API will be included in the output JSON under an
error
property if "Continue On Fail" is enabled. - Typical errors include validation errors for missing required fields or duplicate entries if removal is disabled.
- Errors returned from the API will be included in the output JSON under an
Resolutions:
- Verify that the List ID is correct and exists in your SalesBlink account.
- Ensure all contacts have valid email addresses.
- Check that the API authentication token is correctly set up and has necessary permissions.
- Enable "Remove Duplicates" to avoid conflicts with existing contacts.
Links and References
- SalesBlink API Documentation (for detailed API endpoints and data formats)
- n8n Documentation (for general usage of nodes and credentials setup)