What this helps you do
Flow is the Hub's door for content produced outside it: an alert engine, a publishing system, an analysis pipeline. A registered producer signs each item with its own secret and posts it to the ingest endpoint. The item lands in your Hub's review queue exactly as it would go out, with its text, links and any chart images. Approve or reject it, then Publish: that one human action turns it into a real Blast, with the Blasts fanout and the email leg. Ingest can never send on its own.
When to use it
Use Flow when the words are written by a system rather than a person: market alerts, scheduled reports, automated notices. If a person is writing the message, Send and Campaigns are the right tools.
How to do it
- Ask BlastsHub staff to register a producer for your organization. Producer credentials are issued by staff today, not self-serve; the signing secret is shown exactly once at issue time.
- Your producer signs each request (sha256 HMAC over a timestamp and the raw body, with a five-minute window) and posts the item.
- Open Automated content in your Hub. Each item shows a preview identical to the send.
- Approve or reject. Approval alone sends nothing.
- Click Publish on an approved item. The Hub reports how many Blasts and emails went out and how many attachments were uploaded.
Example
A publisher's analysis engine files a morning alert with a chart at 8:05. The editor opens Automated content, sees the exact rendering, approves it, and publishes at 8:20. Subscribers receive it on Blasts, the email-only readers get the same rendering in their inbox, and the chart travels as an attachment.
Good to know
- Only owners and admins see the review queue and can publish.
- Every item keeps its status and reason: review, approved, rejected, published, or publish failed.
- Producer secrets are stored encrypted at rest and can be disabled by staff at any time.
- Published Flow items are normal Blasts: they cost credits and take the email leg like any other send.