Connect Sequenzy, email marketing and transactional email for SaaS, to your Dify workflows, chatflows and agents. Add and update subscribers, tag them, trigger events that start automated sequences, send transactional email, and read your lists and campaign results.
Source repository: https://github.com/Sequenzy/dify-plugin
- Sign in to Sequenzy (or create a free account).
- Go to Settings > API Keys and create an API key. New keys start with
seq_live_; olderek_keys also work. - In Dify, install the Sequenzy plugin from the Marketplace.
- Open Tools > Sequenzy > Authorize, paste the API key and save.
When you save, Dify checks the key with one read-only request (GET /subscribers/me), which changes nothing in your account.
The plugin needs one credential: a Sequenzy API key, sent as Authorization: Bearer <key>.
A key created with Full access works for every tool. If you restrict a key, give it the permissions for the tools you use, for example subscribers:write to add subscribers and tags, events:write to trigger events, transactional:send to send email, lists:read to list lists, and campaigns:read to read campaigns. A missing permission returns a clear permission error.
- All requests go to the fixed endpoint
https://api.sequenzy.com/api/v1over HTTPS (port 443). No other host is contacted, and the base URL cannot be changed. - Requests time out after 30 seconds, do not follow redirects and ignore proxy environment variables.
- Error messages never include your API key.
- API reference: https://docs.sequenzy.com/api-reference (OpenAPI: https://docs.sequenzy.com/openapi.yaml)
Every tool returns a short text summary for the model and the full API response as JSON for later workflow nodes.
| Tool | Name | Inputs | API call |
|---|---|---|---|
| Add or Update Subscriber | upsert_subscriber |
email, optional first_name, last_name, tags (comma-separated), list_ids (comma-separated), custom_attributes (JSON object), update_mode |
POST /subscribers |
| Get Subscriber | get_subscriber |
email |
GET /subscribers/{email} |
| Add or Remove Tag | tag_subscriber |
email, tag, action (add or remove) |
POST /subscribers/tags or POST /subscribers/tags/remove |
| Trigger Event | trigger_event |
email, event, optional properties (JSON object) |
POST /subscribers/events |
| Send Transactional Email | send_email |
to (up to 50, comma-separated), then either template_slug or subject + body (HTML); optional variables (JSON object), idempotency_key |
POST /transactional/send |
| List Lists | list_lists |
none | GET /lists |
| List Campaigns | list_campaigns |
optional status, limit (1-100, default 20), offset |
GET /campaigns |
| Get Campaign Stats | get_campaign_stats |
campaign_id, optional period (1h, 24h, 7d, 30d, 90d) |
GET /campaigns/{campaignId}/stats |
Notes:
- Add or Update Subscriber: by default, the fields you provide replace existing values and fields you leave empty are kept. Set "If the subscriber exists" to "Only fill in empty fields" or "Leave the existing subscriber unchanged" for the other behaviors. Unsubscribed contacts are never resubscribed.
- Add or Remove Tag and Trigger Event create the subscriber if it does not exist yet, and can start sequences that use the tag or event as a trigger.
- Send Transactional Email confirms the email was queued, not delivered. Pass the same
idempotency_keywhen retrying so the recipient is not emailed twice.
- Sign-up workflow: after a form or sign-up step, call Add or Update Subscriber with the email and name, then Trigger Event with
signed_upto start your onboarding sequence. - Support agent: give an agent Get Subscriber to look up a customer's status, tags and recent email activity before answering.
- Order confirmation: call Send Transactional Email with
template_slug: order-confirmationandvariables: {"orderId": "1042"}. - Weekly report chatflow: call List Campaigns with
status: sent, then Get Campaign Stats for each campaign ID to summarize opens and clicks.
The plugin sends only the inputs you give each tool and your API key to the Sequenzy API. It stores nothing itself and collects no analytics. See PRIVACY.md and the Sequenzy privacy policy.
Questions or problems: email hello@sequenzy.com or open an issue at https://github.com/Sequenzy/dify-plugin/issues. Never post API keys in public issues.
MIT
python3.12 -m venv .venv && . .venv/bin/activate
pip install -r requirements.txt pyyaml
python -m unittest discover -s tests -t .
dify plugin package . -o sequenzy.difypkgTests mock all HTTP traffic and never call the Sequenzy API.