v39.1

• Feature: Zapier can send. A Zap can now send one of your transactional notifications — an order confirmation, a password reset, a shipping update — picking the notification from a list, choosing who receives it, and filling the template's variables from whatever triggered the Zap. The template, the sender and the tracking stay in Notifuse; the Zap only supplies the recipient and the data. Sending creates the contact if the address is new, and updates it with any contact fields the Zap fills in. Giving the step your own message identifier makes it idempotent: sending again with the same one returns the original message instead of a second email, which is what protects a password reset when Zapier retries a step.

  This is why an API key created by connecting Zapier is now granted Transactional read and write. That verb is wider than sending a notification you configured: it also permits creating, editing and deleting transactional notifications, testing templates and providers, and relaying through the SMTP bridge. A leaked Zapier token can therefore send mail through your provider. Connections made before this release keep the narrower grant — add Transactional to the key in Settings → Team, which takes effect on its next request and does not change the token, so no Zap needs reconnecting. Message history remains unreadable to the key either way.

• Improvement: transactional.send on a workspace with no email provider configured now answers 400 naming that, instead of a 500 whose body said only "Failed to send notification" with the cause left in the server log. Other send failures — a provider that was down, rate-limited or rejected the message — still answer 500, because those are worth retrying.

• Improvement: The metadata you attach to a transactional send is now visible. transactional.send has always accepted a metadata object and kept it with the message, but nothing ever showed it back to you. Logs gains a Metadata column — hide it from the column picker if you would rather not see it — and previewing a message shows a Metadata tab when that send carried any. Only transactional sends carry metadata; broadcasts and automations never set it, so the column reads empty for those. Filtering the log by metadata is not part of this.