What this helps you do
Some editions are written by a system you run: a weather digest, a daily puzzle, a report your team generates. BlastsFlow can accept them through a signed ingest. Each item lands in your review queue exactly as it would go out. A person reviews it and presses Publish; that one action sends it now to the item's audience, by email and on Blasts. Nothing filed this way ever sends on its own.
When to use it
Use it when the words come from a system rather than a person. When a person is writing, Compose and Content Series are the right tools.
How to do it
- Ask BlastsHub staff to register a producer for your organization. Producer credentials are issued by staff, not self-serve, and the signing secret is shown exactly once.
- Your system signs each item and posts it to the ingest. A repeated post of the same item is recognized, not duplicated.
- Open Review queue in your Hub (owners and administrators; it appears once a producer is registered). Each item shows the exact rendering readers would receive and the audience it goes to.
- Publish sends it now to that audience. Approve only records a decision and sends nothing. Reject sets it aside.
Example
A publisher's puzzle system files tomorrow's puzzle at 5 p.m. At 5:30 the editor opens the review queue, checks it, and presses Publish; the puzzle's readers receive it by email and on Blasts.
Good to know
- Publishing is always a person's action, and it sends immediately. A time a producer asks for is not scheduled: publish at the moment you want it to go out, or copy it into Compose and schedule it there.
- Publishing from the queue does not ask for a passkey, even when the item goes to All Subscribers. Check the audience shown on the Publish button before you press it.
- Every item keeps its source and its status: review, approved, rejected, published or publish failed.
- Published items are normal Blasts: they cost credits and take the email leg like any other send.
- Staff can disable a producer at any time.