Actions4
- List Actions
- Activity Actions
Overview
This node integrates with the SalesBlink API to retrieve activity data related to email sequences. Specifically, the "Get Clicks" operation fetches information about link clicks within email sequences sent via SalesBlink. This is useful for tracking recipient engagement by identifying which recipients clicked on links in your campaigns.
Common scenarios include:
- Monitoring the effectiveness of email campaigns by analyzing click-through rates.
- Filtering click data by specific email sequences or recipient addresses.
- Automating follow-up actions based on recipient interactions.
For example, you could use this node to get all clicks from a particular sequence and then trigger personalized follow-ups to highly engaged contacts.
Properties
| Name | Meaning |
|---|---|
| Filters | Collection of filters to narrow down the click data: |
| - Sequence ID: Filter clicks by a specific email sequence ID. | |
| - Recipient Email: Filter clicks by a specific recipient's email address. |
Output
The output is an array of JSON objects representing individual click events retrieved from SalesBlink. Each object typically contains details such as the sequence ID, recipient email, timestamp, and possibly metadata about the clicked link.
The node does not output binary data; all returned data is structured JSON suitable for further processing or analysis within n8n workflows.
Dependencies
- Requires an API key credential for authenticating with the SalesBlink API.
- The node makes HTTP GET requests to the SalesBlink public API endpoint
https://run.salesblink.io/api/public/clicks. - Proper configuration of the API authentication credential in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect filter values (e.g., invalid sequence ID) may result in empty responses.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication errors typically indicate issues with the provided API key; verify and update credentials.
- If the node returns an error message about request failure, check network access and API availability.
- Parsing errors might occur if the API response format changes unexpectedly; ensure the API version is compatible.
Links and References
- SalesBlink API Documentation (for detailed API endpoints and parameters)
- n8n HTTP Request Node Documentation (for understanding underlying request mechanics)