Connect your app to HubSpot

HubSpot brings contacts, companies, deals, and support tickets into one CRM. Connect your account to Mythos to build a tailored interface for those records or let an app update your CRM when someone submits a form or completes a workflow.

The saved connection can be used in the project chat while building and in the app you publish. It uses a service key or private app token for your HubSpot account. App visitors do not each connect their own HubSpot account through it.

With HubSpot, you can:

Read and search contacts, companies, deals, and tickets.
Create and update CRM records and their associations.
Use pipelines, lists, and properties to organize a custom workflow.
Build dashboards from the CRM data the key can access.
Work with marketing email drafts and transactional email where your HubSpot account and scopes support them.

Examples to build

These prompts describe custom apps Mythos can create. The connection supplies CRM access; the form, dashboard, access rules, and automation are part of the app you ask it to build.

App idea	Prompt to try	What it adds
Lead capture	Build a demo request form that creates or updates a HubSpot contact using the submitted email, company, and product interest.	New enquiries reach the CRM with the fields your sales team needs.
Pipeline dashboard	Show open HubSpot deals by stage, with filters for owner and expected close date.	A focused view of your sales pipeline using existing deal records.
Contact workspace	Build an internal contact search with editable phone number, job title, and next-step fields.	A simpler CRM interface for a specific team’s daily work.
Support queue	Display open HubSpot tickets and let authorized agents update priority and status.	A support view with the controls you choose.
Record enrichment	Let staff review new company details and apply approved changes to the associated HubSpot contact.	A review step before information is written into the CRM. Provide the source of those details.
Client portal	Build a login-protected portal where each customer sees only their company’s deals and tickets.	A customer-facing view with explicit account-to-record access rules.
Won-deal handoff	Build a won-deal review queue and add a button that posts a handoff summary to our Slack channel.	A deliberate handoff from CRM records to team communication. This also needs a Slack connection.

Connect HubSpot to Mythos

You need permission to create connections in your Mythos workspace and a HubSpot credential with access to the intended data. If a suitable connection is already shared with you, select it and link it to your project.

HubSpot controls API quotas and feature access under your subscription. A working connection does not unlock a paid HubSpot feature or bypass a missing scope.

1. Prepare a service key or private app token

Mythos checks the connection by reading a contact, so include crm.objects.contacts.read, even if the app will mainly work with deals or another object.

Add the read scope for every other object you want to use, and the matching write scope for changes. For example:

What the app needs	Scopes to consider
View contacts	`crm.objects.contacts.read`
Add or edit contacts	`crm.objects.contacts.read` and `crm.objects.contacts.write`
View deals	`crm.objects.deals.read`, plus the contact read scope required for setup
Add or change deals	`crm.objects.deals.read` and `crm.objects.deals.write`, plus contact read access

Lists, other CRM objects, and marketing or transactional email have their own permissions. Choose them according to the features you want to build.

To create a service key in HubSpot:

Open Development → Keys → Service keys.
Select Create service key and give it a name such as Mythos CRM.
Choose Add new scope, select the scopes you need, and click Update.
Review the permissions, click Create, and confirm.
Open the new key, choose Show, and copy it.

HubSpot service keys are in public beta and require a super admin or a user with Developer tools access. See HubSpot’s service key guide. If you already use a private app token, Mythos accepts that credential too, with the same requirement for the scopes your app needs.

2. Save the connection in Mythos

From the Dashboard, open Connectors and select HubSpot. If no saved connection is available, the setup form opens.
Enter a Display name, such as Sales CRM.
Paste the credential into Service key or private app token. Do not put it in a chat message.
Under Sharing, keep Private or select Share with others. Choose specific workspace members or Share with workspace.
Click Connect HubSpot. Mythos checks the credential and contact read access before saving it.

In your project, open Chat actions (+) → Project connectors, select the saved connection, and choose Use in this project. Then ask Mythos to build the CRM feature you need. Sharing access with people and linking a project are separate actions; see Connections in Mythos.

Limits and missing access

This connection works with your HubSpot account’s permitted API actions. It does not install HubSpot UI extensions or subscribe your app to HubSpot webhooks. For a dashboard that should stay current, describe when it should refresh its CRM data.

If setup fails, first check that the credential is valid and includes crm.objects.contacts.read. If the connection saves but a particular action fails, check that object’s scope and the relevant HubSpot feature access. Contacts being readable does not prove deals, tickets, lists, or email actions are also available.

For a client portal, tell Mythos how each signed-in customer maps to a HubSpot record and which fields they may see. The shared credential’s broad CRM access is not a substitute for your app’s customer access rules.

Manage the connection

Open Connectors → HubSpot, then the saved connection. Linked projects → Unlink projects removes selected project links. Disconnect stops Mythos from using the connection while leaving your CRM records in HubSpot.

If you rotate or revoke the credential in HubSpot, disconnect the old connection and connect HubSpot again with a working credential. Link it to the intended projects, ask Mythos to set up the affected features again, and publish the update. Features using the disconnected connection stop working until they are set up again.