Since Notifuse 39, Notifuse works with Zapier, which connects it to thousands of other apps. A Zap can send one of your transactional emails when an order comes in, add the people who fill in a form to your newsletter, or tell your team in Slack when a contact enters a segment. You build it in Zapier's editor, without writing code.
The Zapier integration also changed how API keys work. Connecting it creates a key limited to what a Zap needs, and you can now scope any API key the same way. A webhook subscription can also be limited to the lists or segments it cares about.
Triggers and actions
There are six triggers. Notifuse pushes each event to Zapier the moment it happens, so Zapier doesn't have to poll for it:
New Contact and Updated Contact. A save that changes nothing doesn't fire Updated Contact.
New List Subscriber fires when a contact becomes an active subscriber of a list, whether by subscribing for the first time, confirming a double opt-in, or coming back after unsubscribing.
Contact Unsubscribed From List.
Contact Joined Segment and Contact Left Segment fire when a contact starts or stops matching a segment.
There are three actions:
Send Transactional Email sends one of your transactional notifications, with its template variables filled from the Zap.
Create or Update Contact creates the contact if the address is new, and updates it otherwise.
Subscribe Contact to List creates or updates the contact and subscribes it to the lists you pick, in one step.
All three match contacts on the email address, so running one twice updates the same contact instead of creating a duplicate. Your custom fields appear under the labels you gave them in Settings → Custom fields, and a field with no label is hidden.
Four Zaps
Order confirmations
Start the Zap on a new order in Shopify or a successful payment in Stripe, and add a Send Transactional Email action. Pick your order confirmation in the Notification list, map the customer's Email, and fill Template Data with one row per variable your template uses, such as {{ order_number }} and {{ total }}. The template, the sender and tracking stay in Notifuse, and the email goes out through your own provider.
When a step fails, Zapier retries it, and a retry runs the whole action again. Fill Message External ID with the order number to guard against that: if Notifuse has already seen the ID, sending again returns the original message and no second email goes out. The send also creates the contact if the address is new, and any contact field you map overwrites the stored value. If you only want to send, map nothing but the email address.
Newsletter sign-ups
Trigger on a new response in your form tool, such as Typeform or Google Forms, and use Subscribe Contact to List with your newsletter list. The step returns the status each subscription landed in, and it isn't always active. A contact who unsubscribed before comes back as pending and receives the list's confirmation email. An address that bounced or reported spam isn't resubscribed. A brand-new address lands active, even on a double opt-in list, because the request comes from an API key and not from a public subscription form, so only point a Zap at a list when the form asks for consent.
Segment alerts
Use Contact Joined Segment on a segment such as your VIP customers or your active trials, and post a message in a Slack channel or create a task in your CRM. The trigger gives the contact's email address and the segment's name. Contact Left Segment works the same way for contacts who leave.
Billing sync
When your billing tool records a new subscription or a plan change, a Create or Update Contact action can write the plan into a custom field. Your segments and automations in Notifuse then work from billing data, and there is no import to run.
A key for Zapier
The workspace owner connects Zapier from Settings → Integrations. Notifuse then creates an API key with a fixed set of permissions, so there is nothing to tick: Transactional, Webhook Subscriptions, Contacts and Lists in read and write, plus Segments in read. The token is shown once, next to the API URL you paste into Zapier.
Triggers rely on Webhook Subscriptions. Each Zap you switch on registers its own subscription, listed as Zapier's in Settings → Webhooks, and switching the Zap off removes it. Contacts and Lists cover the contact actions. Transactional write lets a Zap send, but it also allows editing transactional notifications and relaying through the SMTP bridge, so a leaked token could send mail through your provider.
The key can't read your message history, broadcasts, automations or templates, and it belongs to one workspace. Deleting the connection revokes it, and every Zap using it stops at once. To change what it can do, edit the key in Settings → Team & API keys: the change applies on its next request and the token stays the same. A connection made before 39.1, when sending arrived, needs Transactional read and write added this way. On a self-hosted instance without a licence key, that edit is refused, so connect Zapier again instead, paste the new token into Zapier, and delete the old connection.
Scoped API keys
The keys you create in Settings → Team & API keys → New key work the same way. Each area of the workspace has a read switch and a write switch, and you grant only what a key needs. If you leave the choice out, the key gets full access, as before. You can widen or narrow a key at any time without re-issuing its token.
Since Notifuse 40, a self-hosted instance needs a licence key to give a key, or a member, less than full access. Every Notifuse Cloud plan includes one. Without it, a new key can only get full access, but keys you narrowed before keep their permissions, and connecting Zapier still creates its scoped key.
A backend that sends password resets and receipts, for example, needs Transactional write and nothing else. Without Contacts write, a send still creates the recipient contact but stores only the address. Some switches reach further than their name suggests: Contacts write also deletes contacts, and Lists write can overwrite the record of any address it subscribes. The Admins & API Keys page lists what each one allows. When a release adds a new permission, existing keys receive it, so recheck the keys you narrowed after each upgrade. The exception is Audit Logs read, added in Notifuse 41, which no key holds until you grant it.
Filtered webhooks
Until Notifuse 39, a webhook subscription to list or segment events received them for every list and segment in the workspace, and the receiver had to throw away the ones it didn't want. A subscription can now name its lists and segments, and Notifuse doesn't send the other events:
{
"event_types": ["list.subscribed", "list.unsubscribed", "segment.joined"],
"list_ids": ["newsletter", "product_updates"],
"segment_ids": ["vip_customers"]
}list_ids applies to list events only, segment_ids to segment events only. Leave them out and the subscription receives everything. Zapier sets this up for you: each list or segment trigger asks which one it watches, and registers a subscription limited to it. On large lists each list event means one delivery per contact, so the filter removes a lot of deliveries.
Not yet
There is no search step. A Zap can't look a contact up in Notifuse without an action that writes.
Not every event is a trigger. Deleting a contact doesn't start a Zap, and neither do broadcast or automation events.
A send can't carry attachments or a custom body. It uses a notification you configured in Notifuse.
Template Data arrives as text, so a template that compares a value as a number, such as
{% if total > 100 %}, fails, and the email is not sent.Outside Zapier, webhook filters can only be set through the API, with
webhookSubscriptions.createorwebhookSubscriptions.update. The console's webhook screen has no control for them yet.Keys have no usage log. Since Notifuse 41, the audit log (an Enterprise feature) records which key changed a setting, or tried to and was refused, but not the emails it sent or the contacts it wrote. If a token leaks and you don't know which key it is, remove and replace them all. One key per integration keeps that cost small.
A self-hosted instance must be public. Zapier only reaches instances on the public internet, over HTTPS, with a certificate from a public certificate authority: Let's Encrypt works, a self-signed certificate doesn't.
Getting started
If you self-host, run Notifuse 39.1 or later.
Label your custom fields in Settings → Custom fields.
In Settings → Integrations, choose Zapier, give the connection a label and click Connect Zapier. Copy the token, because it is shown only once.
In Zapier, create a Zap with a Notifuse trigger or action, and paste the token when asked to connect an account. On Notifuse Cloud, leave the API URL as it is. If you self-host, paste the address the connect panel printed.
Test with an address you own, because Zapier's Test action sends a real email.
Review your other keys in Settings → Team & API keys, and give each integration its own key with only what it needs.
The Zapier documentation lists the permission each step needs and has a troubleshooting guide, and the webhooks page sits next to it.
