HubSpot
Contacts, deals and where the pipeline moved. Reads, and writes you grant.
| Connects with | OAuth, or a private app token |
| Reads | 18 operations |
| Writes | 11 operations, each granted separately |
| Irreversible | 2 operations, granted separately |
| Personal data | Contacts, and the content of logged notes, calls, meetings and emails. |
| Data stays in | AWS Sydney (ap-southeast-2) |
What it reads
Section titled “What it reads”- CRM records of these types: contacts, companies, deals, tickets, leads, quotes, products, line items, users, goal targets and feedback submissions. For each: the records, their properties, their associations, and search by text (a contact by email, a company by domain, a deal by name).
- Engagements logged against those records: notes, calls, meetings, tasks, emails and communications. Reading emails needs the
sales-email-readscope, which is only requested if you tick an operation that uses it. - The property definitions for each object, including dropdown options.
- Owners and teams, so a record’s owner id resolves to a person and a team.
- Pipelines and their stages.
- Sales forecasts and forecast types.
- Marketing campaigns, with each campaign’s engagement, attributed revenue and budget.
- Forms.
- Conversation inboxes and threads.
- The membership of a list (a segment built in HubSpot).
What it does not read
Section titled “What it does not read”Workflows, sequences and the content of marketing emails. None has an operation in this connector.
What it writes
Section titled “What it writes”Each of these is a separate operation you grant or withhold.
- Create and update contacts, companies and deals.
- Log a meeting, a note or a task against a record, and update a task.
- Associate two records: a note to a deal, a contact to a company.
An update changes only the properties sent. A deal stage must be a stage of that deal’s pipeline. StoriBot is told to search for an existing record before creating one; HubSpot itself refuses a duplicate contact email.
Irreversible operations
Section titled “Irreversible operations”Granted separately, and only where StoriBot may act unattended.
- Remove every association between two records. Nothing records what they were.
- Archive a record. HubSpot moves it to the portal’s recycle bin, which only a person in HubSpot can restore, and only for ninety days.
How you connect it
Section titled “How you connect it”Connect with OAuth. From the Integrations page, choose Connect on HubSpot, tick the operations StoriBot may use, and approve at HubSpot signed in as yourself. HubSpot asks you which account to connect.
If you prefer, paste a private app access token instead. Create the private app under Settings, then Integrations, then Private apps, with the scopes for the operations you will grant.
What StoriBot will ask for
Section titled “What StoriBot will ask for”HubSpot’s consent screen lists the scopes the ticked operations need. Reads use the .read scopes for contacts, companies, deals, tickets, owners, forecasts, campaigns, forms, conversations, teams and lists. Writes use the matching .write scopes for contacts, companies and deals. No scope is requested for an operation you did not tick.
Changing the operations on an OAuth connection takes you back to HubSpot to approve the scopes the new list needs. A pasted private app token must already carry them.
Every operation
Section titled “Every operation”These are the names the Integrations page shows beside each tick box, in the order it lists them. Generated from the connector registry; do not edit by hand.
All 31 operations
| Operation | Kind | What it does |
|---|---|---|
list_objects |
Read | List CRM records of one object type. |
get_object |
Read | Retrieve one CRM record by its numeric id. |
list_properties |
Read | Describe an object type: every property with its internal name, label, type, field type, group and, for a dropdown, radio or checkbox, its full list of options. |
list_owners |
Read | List the users records can be assigned to, with their id, name and email. |
list_pipelines |
Read | List the pipelines for an object type, each with its stages inline. |
list_associations |
Read | List the records of one type associated with a record, the contacts on a deal, the deals on a company, the tickets on a contact. |
list_forecasts |
Read | List sales forecast submissions, what each rep committed to for each period, against the forecast types from list_forecast_types. |
list_forecast_types |
Read | List the forecast categories a portal uses, commit, best case and so on, each with its id and label. |
list_campaigns |
Read | List marketing campaigns with their guid, name, status and dates. |
get_campaign_metrics |
Read | One campaign’s engagement over a window: sessions, new contacts and influenced contacts. |
get_campaign_revenue |
Read | Revenue attributed to one campaign over a window, from the deals it influenced, marketing return in one call. |
get_campaign_budget |
Read | One campaign’s budget and spend totals, side by side. |
list_forms |
Read | List the forms that capture leads, each with its id, name, type and creation date. |
list_inboxes |
Read | List the conversation inboxes, the shared queues that chat, email and form messages land in. |
list_threads |
Read | List conversation threads with their status, inbox, assignee and latest message time. |
list_teams |
Read | List the teams users belong to, each with its id, name and member ids. |
list_list_memberships |
Read | List the record ids in one list, a segment the customer built in HubSpot. |
search_objects |
Read | Find records of one type by text: a contact by email or name, a company by name or domain, a deal by name. |
create_contact |
Write | Create a contact, a new attendee from a call, say. |
update_contact |
Write | Update a contact’s standard properties, a new title, phone or owner learned on a call. |
create_company |
Write | Create a company. |
update_company |
Write | Update a company’s standard properties. |
create_deal |
Write | Create a deal. |
update_deal |
Write | Update a deal after a call: move the stage, revise the amount or close date, record the next step, reassign. |
create_meeting |
Write | Log a meeting that took place, the call itself, with its summary as the body and its outcome. |
create_note |
Write | Log a note, a decision, a summary, context for the next call. |
create_task |
Write | Create a follow-up task with a due date, and an owner from list_owners so it lands in someone’s queue. |
update_task |
Write | Update a task: mark it COMPLETED, move its due date, reassign it. |
associate_records |
Write | Attach two records with HubSpot’s default association for the pair: a meeting, note or task to the contact, company or deal it is about; a contact to a compa… |
remove_association |
Irreversible | Remove every association between two records, labels included, and nothing records what they were. |
archive_object |
Irreversible | Archive a record: a duplicate contact, a note or task logged in error. |