Deals
Deal name, amount, stage, close date, and pipeline are read for a suggested RunwayCal deal.
HubSpot + RunwayCal
Read supported HubSpot contacts, companies, and deals, review suggested matches, and approve the opportunities that belong in RunwayCal. CRM pipeline remains expected commercial context, not cash received.
What connects
The connection is a user-triggered CRM import workflow. It reads HubSpot objects, proposes deal mappings, and waits for approval before creating or linking RunwayCal deals.
Contacts and companies
Supported contact and company fields help identify the opportunity; they are not separate RunwayCal customer records.
Stage context
HubSpot stage informs the suggested lifecycle status. The connection does not convert pipeline into realized cash.
User control
Users can refresh, preview, approve, link, create, skip, dismiss, and disconnect.
Without HubSpot connected vs with HubSpot connected
Without HubSpot connected
- Export CRM opportunities before financial review
- Re-enter supported opportunity details
- Track the CRM source outside RunwayCal
With HubSpot connected
- Read HubSpot objects through OAuth
- Review match confidence and suggested actions
- Approve only the deals that belong in RunwayCal
- Keep expected pipeline separate from received cash
Who uses this connection
Finance and revenue reviews
Bring selected opportunity amounts and dates into one controlled planning workflow.
Founders checking commercial assumptions
Review which opportunities belong in the model before making a spend decision.
Teams cleaning duplicate entry
Link an opportunity to an existing RunwayCal deal when the records describe the same commercial commitment.
Connection boundary
The HubSpot connection requests read scopes for contacts, deals, and companies. It does not write to HubSpot, create CRM activity, or make pipeline cash. The user owns every RunwayCal deal approval.
OAuth connection · explicit approval
Bring selected CRM opportunities into the financial conversation.
HubSpot describes sales work. RunwayCal needs only the supported opportunity context that a user chooses to bring into the operating plan.
A user-triggered refresh reads contacts, companies, and deals. RunwayCal compares each deal with existing records and proposes a link or new deal without writing to HubSpot.
The approved RunwayCal deal retains the HubSpot deal ID and supported stage context. Expected close dates and amounts remain planning inputs; they are not evidence that money has landed.
OAuth access tokens refresh when required. Disconnecting revokes the stored refresh token on a best-effort basis, clears local credentials and cache, and removes HubSpot links from RunwayCal deals.
Use HubSpot to manage the pipeline. Use RunwayCal to review the financial meaning of selected opportunities without treating them as collected cash.
Review HubSpot data in RunwayCal
Connect the supported account, inspect available data, and approve what enters RunwayCal.