Actions71
- Settings Actions
- Subscribers Actions
- Create Subscriber
- Manage Subscriber Lists By Query
- Get Subscribers
- Delete Subscriber By List
- Get Subscriber By Id
- Update Subscriber By Id
- Delete Subscriber By Id
- Manage Subscriber Lists
- Manage Subscriber List By Id
- Manage Blocklist By Subscriber List
- Manage Blocklist Subscribers By Id
- Export Subscriber Data By ID
- Get Subscriber Bounces By Id
- Delete Subscriber Bounces By Id
- Subscriber Send Optin By Id
- Delete Subscriber By Query
- Blocklist Subscribers Query
- Bounces Actions
- Import Actions
- Campaigns Actions
- Update Preview Campaign By Id
- Get Campaigns
- Create Campaign
- Get Campaign By Id
- Update Campaign By Id
- Delete Campaign By Id
- Get Running Campaign Stats
- Get Campaign Analytics
- Preview Campaign By Id
- Preview Campaign Text By Id
- Update Campaign Status By Id
- Update Campaign Archive By Id
- Create Campaign Content By Id
- Test Campaign By Id
- Media Actions
- Templates Actions
- Public Actions
- Miscellaneous Actions
- Admin Actions
- Logs Actions
- Lists Actions
- Transactional Actions
- Maintenance Actions
Overview
This node operation "Transact With Subscriber" in the "Transactional" resource allows sending transactional messages to a subscriber using the Listmonk API. It supports specifying subscriber details such as email or ID, the template to use, sender email, message content, headers, messenger type, and content type. This operation is useful for automating personalized transactional communications like order confirmations, password resets, or notifications to individual subscribers.
Use Case Examples
- Sending a password reset email to a subscriber by specifying their email and a template ID.
- Sending a notification message to a subscriber identified by their subscriber ID with custom data and headers.
Properties
| Name | Meaning |
|---|---|
| Subscriber Email | The email address of the subscriber to whom the transactional message will be sent. |
| Subscriber Id | The unique identifier of the subscriber to whom the transactional message will be sent. |
| Template Id | The ID of the message template to use for the transactional message. |
| From Email | The email address from which the transactional message will be sent. |
| Data | JSON object containing dynamic data to be merged into the message template. |
| Headers | JSON object specifying additional HTTP headers to include in the request. |
| Messenger | The messenger platform or channel to use for sending the message. |
| Content Type | The content type of the message being sent. |
| Request Options | Additional request options such as batching, SSL certificate validation, proxy settings, and timeout configuration. |
Output
JSON
response- The JSON response from the Listmonk API after sending the transactional message.
Dependencies
- Requires an API key credential for authenticating with the Listmonk API.
Troubleshooting
- Ensure the subscriber email or subscriber ID is correctly provided; missing or incorrect subscriber identification will cause the request to fail.
- Verify that the template ID exists and is valid in the Listmonk system to avoid template not found errors.
- Check that the 'from_email' is a valid sender address authorized in the Listmonk account.
- If using custom headers or data, ensure they are correctly formatted JSON to prevent request errors.
- If SSL certificate validation errors occur, consider enabling the 'Ignore SSL Issues' option cautiously.
- Proxy settings must be correctly configured if used, including authentication details if required.
- Timeouts can occur if the server is slow to respond; adjust the timeout setting accordingly.
Links
- Listmonk Transactional API Documentation - Official documentation for the Listmonk transactional messaging API, detailing endpoints and usage.