Everything SeqBridge does, in order.
Written for someone using the app inside HubSpot — install, the two workflow actions, how the sender is resolved, quota, and what to check when something looks off.
What SeqBridge does
SeqBridge lets a HubSpot workflow enroll a contact into a sales sequence — automatically. HubSpot reserves workflow-based sequence enrollment for Sales Hub Enterprise; on a Professional seat you can build sequences and enroll contacts by hand, but not from a workflow. SeqBridge closes that one gap.
It works because the gap is only in the workflow editor, not the API. The Sequences API itself accepts enrollments on a Professional seat. SeqBridge ships a custom workflow action that, when it runs, calls this backend, which calls the Sequences API for your portal.
Everything on the Free plan is fully functional — install it, wire up a real workflow, and enroll a contact before you decide whether to pay for a higher limit.
Install & permissions
Install SeqBridge from the HubSpot marketplace and approve the requested scopes. Your portal lands on the Free plan automatically — there is no signup form and no account to create.
The scopes it asks for, and why each is needed:
| Scope | Why |
|---|---|
automation.sequences.enrollments.write | To enroll a contact into a sequence. |
automation.sequences.read | To list your sequences in the action’s dropdown. |
automation | To register and run the workflow action. |
crm.objects.contacts.read | To read the contact being enrolled. |
crm.objects.companies.read, crm.objects.deals.read, tickets | To walk from a company, deal or ticket to its associated contacts for the bulk action. |
crm.objects.owners.read | For the sender dropdowns, and to translate a sender’s email into the HubSpot user id the Sequences API requires. |
oauth | Standard OAuth handshake. |
SeqBridge never asks for access to your email content, and the sequences it enrolls into are the ones you already built in HubSpot.
Enroll Contact in Sequence
This is the main action. Add it to any contact-based workflow. When the workflow reaches it, the contact is enrolled into the sequence you picked.
Fields
| Field | What it does |
|---|---|
| Sequence | The sequence to enroll into, chosen from a dropdown of your portal’s sequences. Each is labelled with its owner, because two teams often name sequences the same thing. |
| Send as | Either a specific user or the contact’s owner. Choosing the contact’s owner hides the sender field and uses each contact’s own owner as the sender. |
| Sender | Shown only in “a specific user” mode: the user the sequence sends as. Sequences send through this person’s connected inbox. |
| From email | The connected from-address to send from. |
| Replace active sequence | If the contact is already in a sequence, whether to replace it or skip this contact. Default is skip. |
Outputs
The action returns a status, the enrollment id when it succeeded, and a readable failure reason when it did not — all visible on the workflow history for that step.
The action always completes the workflow. If an enrollment can’t proceed, it returns “fail and continue” with a reason rather than erroring — so the rest of your workflow still runs.
Enroll Associated Contacts
The bulk action. Add it to a company, deal, or ticket workflow, and it enrolls every contact associated with that record into the sequence.
It carries a maxContacts safety limit — default 50 — so an unexpectedly large association set can’t enroll thousands of contacts in one run. The run resolves the sender once and reuses it, so a 50-contact batch makes a single owners lookup rather than fifty.
Its outputs report how many contacts were enrolled, skipped, and failed for the run.
How the sender is resolved
HubSpot’s Sequences API is user-scoped: every call needs the sending user’s
HubSpot userId, not just their email. SeqBridge resolves that for you.
- In specific-user mode, it looks the id up from the email you picked.
- In contact’s-owner mode, it reads the id from each contact’s owner record.
This is also why the owners scope is required even though you’re enrolling contacts: the
owners endpoint is the bridge from an email address to a userId.
The enrollment status card
On any contact record, the Sequence enrollment card shows that contact’s recent enrollment attempts through SeqBridge — the sequence, the status, and the reason for anything that didn’t succeed. It reads the same audit trail the workflow history draws from, so the two always agree.
Account & plan page
SeqBridge adds an Account & plan settings page inside HubSpot showing your current plan, how many enrollments you’ve used this month, your limit, and the date the count resets. It’s the quickest way to see where you stand without leaving HubSpot.
Quota & how it resets
Three rules govern the enrollment limit, and they’re worth knowing precisely:
- Only successful enrollments count. A failed or skipped attempt uses no quota.
- The window is the UTC calendar month. Your limit resets on the 1st — not on a billing anniversary.
- Expiry is lazy. A paid plan that lapses reads as Free on the next request; your history is kept, so renewing restores where you were.
When you reach the limit, the action returns “fail and continue” with a reason naming the plan, your usage and where to upgrade. A bulk run checks the limit once for the batch and only attempts as many as remain, so you don’t get a wall of identical rejections.
Upgrading & billing
To move up a tier, submit an upgrade request with your portal ID, the plan and the billing period. We email you bank-transfer details; once the transfer clears, we set your plan and it runs from that day. There is no card checkout, and SeqBridge stores no card details.
Prices shown on the pricing page are read live from our own records — the number you see is the number you’ll be invoiced.
Known limits
- No unenroll. HubSpot’s public API has no unenroll endpoint, so SeqBridge can’t offer one. Unenroll manually in HubSpot.
- One active sequence per contact. HubSpot allows exactly one; “replace active sequence” chooses whether to skip or replace.
- Rate and send limits. HubSpot caps requests per account and Professional caps sends per user per day. SeqBridge retries rate-limited calls automatically; very high-volume portals should stagger their workflows.
- A connected inbox is required on the sending user — a seat alone won’t send.
Troubleshooting
| Symptom | Likely cause |
|---|---|
| The sequence or sender dropdown is empty | Missing owners scope, or the user has no sequences they own or can see. Reinstall to grant the scope, or pick a user who owns a sequence. |
| “Sales Subscription Status is not OK” | The sending user has no connected inbox. Connect one to that user in HubSpot. |
| A contact was skipped, not enrolled | They’re already in an active sequence, and “replace active sequence” is off. That’s a SKIPPED, not a failure. |
| “Monthly enrollment limit reached” | You’ve used this month’s quota. It resets on the 1st, or upgrade for a higher limit. |
Still stuck? The failure reason on the workflow history and the contact’s status card usually name the exact problem. If not, reach us from the support page with your portal ID.