Dispatch preview
Dispatch preview asks the dispatcher what one HubSpot contact would get next from a campaign, and gets back exactly that: the row, the pool, the message, its position in the pool, the sender, the subject, the blocks, and for every row whether it matched the contact and why. It runs the same code a HubSpot workflow dispatch runs, on the contact's real properties, lists and progress.
Use it to confirm a campaign's pools with a test contact, from an AI assistant connected to mxAURA, from another app through the API, or from your own scripts.
A test changes nothing
A preview writes nothing. The contact does not move forward, no rotation moves, nothing is added to the dispatch log, no number on any page changes and nothing is written to HubSpot. Run it ten times and you get the same answer ten times. It only changes when the contact or the campaign does.
If you send the previewed email to yourself, its links and open pixel are marked as a test: opening or clicking it is not counted anywhere.
A campaign that is switched off still previews, so you can check it before go-live. The answer says it would not send yet, and why.
Reading the answer
- Status: message, no message (nothing left to send, or no row in its schedule window), filtered (every row in window failed its filter), or blocked (the message cannot be filled, with the reason).
- Rows evaluated: every row in order, matched or not, with the value it compared. For example: opportunity_type is equal to Partner (got "Client").
- Progress key: contact and pool. Progress belongs to the pool, so the same pool on two rows carries on where the contact left it, whichever row lets them in.
Real dispatches from another app
A real dispatch through the API (commit, or send) does everything a HubSpot dispatch does: the contact moves forward, rotations move, and the send counts in the dispatch log and every stat, marked with where it came from. It needs an API key or connection with dispatch write access, which you grant in Account, API. It sends no email itself: the other app sends the message it gets back, or asks mxAURA to write it to the HubSpot contact so a HubSpot email sent next carries it.
Through the AI connection the message's field text and HTML come back as lengths only; the API returns them in full.