Actions4
- List Actions
- Activity Actions
Overview
This node integrates with the SalesBlink API to retrieve email activity data related to sequences in a sales campaign. Specifically, for the Activity resource and Get Opens operation, it fetches information about email opens by recipients. This is useful for tracking engagement metrics in email outreach campaigns, allowing users to see which contacts have opened their emails.
Practical scenarios include:
- Monitoring the effectiveness of email sequences by analyzing open rates.
- Filtering open events by specific sequence IDs or recipient email addresses to focus on particular campaigns or contacts.
- Automating follow-up actions based on whether an email was opened.
Properties
| Name | Meaning |
|---|---|
| Filters | Collection of optional filters to narrow down the results: |
| - Sequence ID: Filter opens by a specific sequence identifier. | |
| - Recipient Email: Filter opens by a specific recipient's email address. |
Output
The output is a JSON array where each item represents an email open event retrieved from SalesBlink. Each object contains details about the open event, such as timestamps, associated sequence IDs, and recipient information (exact fields depend on the API response).
No binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the SalesBlink API.
- The node makes HTTP requests to
https://run.salesblink.io/api/public/opensendpoint. - Proper configuration of the API authentication credential in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing incorrect filter values (e.g., invalid sequence ID) may result in empty responses.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Errors returned from the API are caught and can be output as error messages if "Continue On Fail" is enabled.
- Typical errors include authentication errors ("Unauthorized"), bad request errors due to invalid parameters, or server errors.
Resolutions:
- Verify that the API key credential is correctly set up and has sufficient permissions.
- Double-check filter inputs for correctness.
- Ensure network access to the SalesBlink API endpoint.
Links and References
- SalesBlink API Documentation (for detailed API endpoints and data structures)
- n8n documentation on HTTP Request Node (conceptual similarity for API calls)