Actions4
- List Actions
- Activity Actions
Overview
This node integrates with the SalesBlink API to retrieve activity data related to email sequences. Specifically, the "Get Replies" operation fetches replies received from recipients in email sequences managed within SalesBlink. This is useful for sales and marketing automation workflows where you want to track engagement by monitoring which contacts have replied to your outreach emails.
Practical examples include:
- Automatically logging replies into a CRM system.
- Triggering follow-up actions or notifications when a reply is detected.
- Analyzing response rates for specific email sequences or recipients.
Properties
| Name | Meaning |
|---|---|
| Filters | Collection of filters to narrow down the replies retrieved: |
| - Sequence ID | Filter replies by a specific email sequence identifier. |
| - Recipient Email | Filter replies by the recipient's email address. |
Output
The node outputs an array of JSON objects representing the replies fetched from SalesBlink. Each object corresponds to a single reply and contains details as provided by the SalesBlink API (such as reply content, sender info, timestamps, etc.). The exact structure depends on the API response but generally includes metadata about the reply event.
No binary data output is produced 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/repliesendpoint. - 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 or malformed email) may result in empty responses or errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Authentication errors typically indicate issues with the API key; verify and update credentials.
- API rate limits or server errors will be returned as error messages from the API; consider retry logic or checking API usage quotas.
- Parsing errors might occur if the API response format changes unexpectedly; ensure the node and API versions are compatible.
Links and References
- SalesBlink API Documentation (for detailed API endpoints and data structures)
- n8n HTTP Request Node Documentation (for understanding how API requests are made)