HubSpot setup guide

Flow Relay reads your HubSpot deals and tickets and combines them with the activity of your other connected tools – code hosts, issue trackers, chat, monitoring – into handoffs, insights, digests and release notes. The integration is read-only: Flow Relay never creates, edits, assigns or closes anything in HubSpot.

What you get:

• Deal and ticket changes next to the engineering work that relates to them, so a handoff can say "Acme renewal moved to Contract sent, owned by Jane Doe" next to the pull request that unblocked it.
• Correlation insights that link a spike in tickets to the deploy that caused it.
• Pipeline, stage and owner ids resolved to their labels, so every artifact reads like a person wrote it.

• A Flow Relay account on any plan. Sign up at flowrelay.it.
• A HubSpot user with permission to install apps on the account. Sales Hub or Service Hub are not required: deals and tickets are part of every HubSpot CRM.

1. Sign in to Flow Relay and open Integrations.
2. Find the HubSpot card and click Connect.
3. HubSpot asks you to pick the account to connect. Choose it and click Choose account.

4. Review the requested scopes and click Connect app. Flow Relay requests three read-only scopes:

• crm.objects.deals.read – deal name, pipeline, stage, amount, close date, priority and owner id of your deals.
• crm.objects.tickets.read – ticket subject, pipeline, stage, priority and owner id of your tickets.
• crm.objects.owners.read – the name behind an owner id, so changes are attributed to a person instead of a number. HubSpot lists a fourth entry, the basic oauth scope every app carries: it lets Flow Relay read the portal id and domain that route webhook deliveries to your account.

5. You are redirected back to Integrations. The HubSpot card now shows the portal it reads, a green Connected status and a Sync now button for a manual refresh.

Behind the scenes Flow Relay stores an encrypted access token, pulls a baseline of your open deals and tickets and starts receiving deal and ticket changes through HubSpot webhooks.

HubSpot data reaches a project only when you bind it there. This keeps a sales pipeline out of a project that has nothing to do with it.

1. Open a project and scroll to the Integrations section.
2. Click Add Integration and pick HubSpot under Select integration source.
3. Under Select pipelines, click + next to each pipeline the project should follow. Each pipeline is added as soon as you click it, and only deals and tickets in the added pipelines reach the project.
4. Repeat for every project that should see HubSpot activity.

Optional, per generation: the filter panel of every artifact lets you narrow HubSpot to specific pipelines, priorities (deal and ticket priority alike) and deal or ticket event types. A handoff filtered to the high-priority tickets of the Support tickets pipeline covers only those tickets. See Filters.

Nothing to run by hand. Once a pipeline is bound to a project:

• Automatic capture. New deals and tickets, stage moves, amount and close date changes, priority changes and deletions arrive in real time through webhooks and show up in the Activity section of the project page as HubSpot: deal updated – Acme renewal, with pipeline, stage, owner and amount resolved to labels underneath. When the project follows more than one source, the picker in the section header narrows the list to HubSpot.

• Readable events. Click an event to expand it and see what changed: the stage move (for example Contract sent to Closed won), owner, amount, close date and priority of a deal, or the stage and priority of a ticket, as your team names them in HubSpot, never as internal ids.

• Periodic baseline. Every few hours Flow Relay refreshes the list of open deals and tickets per pipeline so an artifact always sees the current state, not only the changes.
• Generate artifacts. From the project page, click Generate on the handoff, correlation, onboarding, architecture, digest or release notes panel. The same generations are available through the REST API, the MCP server and the VS Code extension. Each artifact costs a flat number of credits from your plan – the HubSpot source does not change the price.

• Ask a question. The Ask this project box answers a plain-language question, such as "Which deals moved this week and what blocks them?", from the deals and tickets bound to the project plus your other connected tools. Every answer cites the events it comes from, and each question costs 2 credits.

1. Open Integrations and click Disconnect on the HubSpot card.
2. Choose what happens to the captured context:
   • Disconnect revokes the HubSpot grant and stops capturing new activity. Captured deals and tickets are kept for 30 days so reconnecting restores everything, then deleted automatically.
   • Disconnect & Delete (toggle Delete all captured context now) revokes the grant and deletes every HubSpot event Flow Relay stored, immediately. Events already cited by a generated handoff or insight are kept so the artifact stays readable.
   • Keep Connected closes the dialog without changing anything.

Nothing changes in HubSpot: your deals, tickets and owners are untouched, and the app is removed from the account's connected apps.

You can also remove Flow Relay from HubSpot's side. In HubSpot go to Settings, then Integrations, then Connected apps, find Flow Relay and click Uninstall – see the HubSpot knowledge base. Flow Relay stops receiving events at once; disconnect from the Integrations page as well to revoke the stored token and choose what happens to the captured context.

• Stored: deal and ticket properties listed under the scopes above, the resolved pipeline, stage and owner labels, and the portal id used to route webhook deliveries.
• Not stored: contacts, companies, emails, notes or any object outside deals and tickets.
• Tokens and every captured event are encrypted at rest, scoped per project and never shared across Flow Relay accounts.
• Full detail in the privacy policy.

Write to support@flowrelay.it with the portal shown on your HubSpot card and we will look at the connection. Other channels are listed on the support page.