A click-by-click walkthrough — from the HubSpot Marketplace button to your first blocked contact in the decision log. If you get stuck on any step, email support@flowchester.com and we'll fix it with you.
Head to our HubSpot Marketplace listing and click Install app. You can also start the install from this site — both buttons land you in the same HubSpot OAuth screen.
Why not link to HubSpot directly? Our install URL passes through the Flowchester backend first so we can generate a CSRF token that HubSpot echoes back. It's the only way to prevent OAuth state attacks. The next page you see is HubSpot's.
HubSpot will ask which portal to install on. Pick one portal per subscription — if you manage several portals (agencies, multiple brands), install separately on each and subscribe independently. Flowchester never crosses portal boundaries.
HubSpot shows the exact scopes we request. All four are required for the app to work; we do not ask for anything else.
| Scope | What we do with it |
|---|---|
| crm.objects.contacts.read | Reads contacts immediately after HubSpot creates them so we can evaluate your rules. |
| crm.objects.contacts.write | Deletes a contact when a block rule matches, and restores it when you click un-block. |
| conversations.read | Looks at the conversation that triggered a contact creation — lets us tell a true sender from a CC-only recipient. |
| oauth | Required by HubSpot for any OAuth app; lets us refresh our access token without asking you again. |
Click Connect app. HubSpot will redirect you to Flowchester.
You'll land on the Flowchester billing page at app.flowchester.com. Pick a plan:
Click Choose and you'll be redirected to a Stripe-hosted checkout page. Enter your card, email, and (if required for tax) billing country, then click Subscribe. Stripe charges immediately; your subscription activates on our side within a couple of seconds.
After Stripe redirects you back to the dashboard, you land on the decision log. At first it's empty — blocks only happen when HubSpot creates new contacts. Two ways to confirm the pipeline is live:
noreply@anywhere.com into a conversation your portal is watching. Within a few seconds the decision log shows the block with rule name, matched pattern, and source.If no blocks appear after an hour of HubSpot receiving noreply-style emails, skip to Troubleshooting below.
The default rules handle about 80% of garbage. The remaining 20% is portal-specific — your vendor auto-responders, your internal tools, the specific domains your team always ends up CC'd on.
@typeform.com), local part (e.g. accounts-noreply@*), or full pattern.Tip: before writing a rule from memory, open the decision log filter for “passed through” (nothing matched, contact created) — it shows you what recently slipped through that you might want to block.
Two things to do, in either order. Both must happen for a full removal.
No data stays with HubSpot from our side — we never write anything to contact records except the deletion itself.
Include your HubSpot portal ID (top-right of your HubSpot dashboard), what you were trying to do, and what you saw instead. That's usually enough for us to reproduce and fix it on the spot.