Sales leaders
Review pipeline by stage and owner every Monday without exporting from HubSpot.
Review contacts, deals, CRM activities and custom objects. Teammates or AI can propose property updates, new records, deal stage and ticket status changes, owner changes, links between records, notes, static list changes and archiving on contacts, companies, deals and tickets, and each one waits for owner approval.
Updated November 2026
| Name | Stage | |
|---|---|---|
| Avery Chen | avery@northwind.example | Lead |
| Jordan Blake | jordan@harbor.example | Proposal |
| Sam Okonkwo | sam@acme.example | Won |
Review pipeline by stage and owner every Monday without exporting from HubSpot.
Fix messy contact and company names without giving everyone admin access.
Show clients which campaigns turned into HubSpot deals.
Read existing CRM and marketing reports plus calls, meetings, notes, tasks, logged emails, custom-object schemas and records, record associations and association labels.
The owner reviews the exact values and approves every proposed change before it is applied to HubSpot.
New activity and relationship datasets show current accessible records; permissions and subscription determine availability.
Read current calls, meetings, notes, tasks and logged emails with their IDs and timestamps.
Limit: Task timestamps are due dates; these reports do not reconstruct historical activity counts.
Choose one record to inspect its associated records and relationship labels.
Limit: Read one custom object's selected properties as JSON using its account-specific schema.
Bring the current pipeline and won-deal report into the weekly review.
Limit: Use the same project for the contact details your team needs to check.
A teammate spots an outdated company name or description and proposes the replacement.
Limit: The owner reviews and approves that specific change.
See the problem in your report, then propose the fix in Datapipe instead of opening HubSpot, finding the record and retyping it.
Teammates and AI tools can suggest changes without getting edit access to HubSpot.
You see the current and proposed value side by side, and every change is logged.
TodayFind contacts entered as "jordan BLAKE" and retype them in HubSpot.
With DatapipeSort the contact report to find them. Propose the corrected names and approve each one.
TodayLook people up and paste titles in one record at a time.
With DatapipeA teammate proposes job titles for the contacts in your report, and you approve them.
Changes an existing contact's name or job title. HubSpot workflows and connected systems may react. Email, lifecycle stage, marketing consent and associations are unchanged.
Supported fields: First name, Last name, Job title.
TodayCopy text from each company's website into HubSpot.
With DatapipeChatGPT drafts a description per company, and you approve it before it's saved.
TodayRename companies like "acme inc" one at a time.
With DatapipeSort the company report by name, propose the proper name for each and approve. Domains and owners stay unchanged.
Changes an existing company name or description. HubSpot workflows and connected systems may react. Domain, ownership and associations are unchanged.
Supported fields: Company name, Company description.
TodayRename deals by hand so reports read "Company · Product · Quarter".
With DatapipePropose the new names from the pipeline report. Amounts, stages and owners stay unchanged.
TodayOpen deals called "New deal" and rename them one by one.
With DatapipeFind them in the pipeline report and propose a clear name. HubSpot changes only after you approve.
Renames an existing deal. HubSpot workflows and connected systems may react. Amount, pipeline, stage, close date, owner and associations are unchanged.
Supported fields: Deal name.
TodayOpen each contact after the call and pick the new lifecycle stage from the dropdown.
With DatapipeA teammate proposes the stage for each contact from the call list, and you approve each exact change.
TodayLook up where each contact came from and type it into a custom property.
With DatapipeChatGPT compares your ad report with the contact report and proposes the lead source. You see the old and new value before approving.
TodayReassign contacts one at a time when territories change.
With DatapipePropose the new contact owner from the territory sheet. Datapipe checks the owner is an active HubSpot user before you approve.
Changes the contact properties the owner selects, which can include custom properties, dropdowns, numbers, dates, checkboxes and the record owner. HubSpot property rules still apply, and workflows or connected apps may react. Marketing consent, subscription status and sensitive properties are not offered. A new owner must be an active HubSpot user and may get a HubSpot notification.
The owner selects supported writable fields for this action before teammates can propose changes.
TodayResearch each company and update its dropdowns and numbers by hand.
With DatapipeChatGPT reads the company report and proposes industry and size from the allowed values. You approve each company.
TodayTick a custom "Key account" box on each company before the quarterly review.
With DatapipeJordan proposes the checkbox for the companies on the account plan, and the owner approves each one.
Changes the company properties the owner selects, which can include custom properties, dropdowns, numbers, dates, checkboxes and the record owner. HubSpot property rules still apply, and workflows or connected apps may react. A new owner must be an active HubSpot user and may get a HubSpot notification.
The owner selects supported writable fields for this action before teammates can propose changes.
TodayOpen each deal and retype the amount and close date after the call.
With DatapipeA teammate proposes the new amount and close date from the call notes. You see the before and after values and approve.
TodayKeep renewal dates in a spreadsheet and copy them into a custom deal property.
With DatapipeIf the owner allows that date property, ChatGPT proposes renewal dates from the sheet and you approve each deal.
Changes the deal properties the owner selects, which can include custom properties, dropdowns, numbers, dates, checkboxes and the record owner. HubSpot property rules still apply, and workflows or connected apps may react. Pipeline and stage have their own action. A new owner must be an active HubSpot user and may get a HubSpot notification.
The owner selects supported writable fields for this action before teammates can propose changes.
TodayOpen each ticket and pick a priority after the morning triage.
With DatapipeA teammate proposes the priority for each ticket from the ticket report, and you approve each exact change.
TodayReassign tickets by hand when someone is out of office.
With DatapipePropose the new ticket owner for each ticket. Datapipe checks the owner exists in HubSpot before you approve.
Changes the ticket properties the owner selects, which can include custom properties, dropdowns, numbers, dates, checkboxes and the record owner. HubSpot property rules still apply, and workflows or connected apps may react. Pipeline and status have their own action. A new owner must be an active HubSpot user and may get a HubSpot notification.
The owner selects supported writable fields for this action before teammates can propose changes.
TodayType each attendee into HubSpot after the event.
With DatapipeChatGPT reads the sign-up sheet and proposes each new contact with the properties you allow. You approve each one before it is created.
TodayOpen HubSpot and fill in the contact form when a client adds someone to the project.
With DatapipeA teammate proposes the new contact with name, email and job title. HubSpot refuses duplicates by email.
Creates one new contact with the properties the owner selects. HubSpot property rules still apply, and workflows or connected apps may react. HubSpot refuses a second contact with the same email address. It is not linked to other records; use the link action for that. It can be archived later with the archive action or in HubSpot.
The owner selects supported writable fields for this action before teammates can propose changes.
TodayCreate each company in HubSpot from a list sent by sales.
With DatapipeChatGPT proposes each company with its name and domain from the list, and you approve each one.
TodayAsk an admin to add the partner company and its details.
With DatapipeA teammate proposes the company with the properties you allow, and it is created after your approval.
Creates one new company with the properties the owner selects. HubSpot property rules still apply, and workflows or connected apps may react. It is not linked to other records; use the link action for that. It can be archived later with the archive action or in HubSpot.
The owner selects supported writable fields for this action before teammates can propose changes.
TodayCreate renewal deals by hand from the contract sheet every quarter.
With DatapipeChatGPT proposes a deal per renewal with name, amount and pipeline stage. You approve each one before it appears in HubSpot.
TodayCopy the details from an email into a new deal form.
With DatapipeA teammate proposes the new deal with its stage and close date, and you review it before it is created.
Creates one new deal with the properties the owner selects. HubSpot property rules still apply, and workflows or connected apps may react. A new deal needs a name and a pipeline stage. It is not linked to other records; use the link action for that. It can be archived later with the archive action or in HubSpot.
The owner selects supported writable fields for this action before teammates can propose changes.
TodayCopy each request from email into a new HubSpot ticket.
With DatapipeA teammate proposes a ticket with subject, description and status from the request. You approve it before it is created.
TodayCheck the store report and create a support ticket for each failed order.
With DatapipeChatGPT proposes one ticket per failed order from your store report, and you approve each one.
Creates one new ticket with the properties the owner selects. HubSpot property rules still apply, and workflows or connected apps may react. A new ticket needs a subject and a pipeline status. It is not linked to other records; use the link action for that. It can be archived later with the archive action or in HubSpot.
The owner selects supported writable fields for this action before teammates can propose changes.
TodayDrag each deal to its new stage in HubSpot after the Monday meeting.
With DatapipeA teammate proposes the new stage for each deal discussed, and you approve each move.
TodayCheck payments, then mark each paid deal as closed won.
With DatapipeChatGPT compares your payment report with open deals and proposes closed won for paid ones. You approve each deal.
Moves one deal to a different pipeline or stage, including closed won or closed lost. HubSpot may update properties tied to the stage, such as the deal probability, and workflows may react. Amount, owner and other properties are unchanged.
The owner selects supported writable fields for this action before teammates can propose changes.
TodayOpen each ticket and set its status to closed after reading the thread.
With DatapipeA teammate proposes the closed status for resolved tickets, and you approve each one.
TodayFind tickets with new replies and move them back to open.
With DatapipePropose the new status from the ticket report. HubSpot changes only after your approval.
Moves one ticket to a different pipeline status, which can close or reopen it. Workflows your HubSpot admin set up may react, including ones that email the customer; Datapipe sends no email itself.
The owner selects supported writable fields for this action before teammates can propose changes.
TodayOpen each contact and add the company it belongs to.
With DatapipeChatGPT matches email domains in the contact report to companies and proposes each link. You approve each one.
TodaySearch for the deal from inside the ticket and associate it by hand.
With DatapipeA teammate proposes the link between the ticket and its deal, and you review both records before approving.
Adds HubSpot's standard link between one contact, company, deal or ticket and one record of another kind, so each appears on the other's record. Existing links and association labels are unchanged. Workflows that react to new associations may run.
Supported fields: Records to link, The other record's HubSpot ID.
TodayOpen the contact and remove the old company association.
With DatapipeA teammate proposes removing the link. You see both records before approving, and neither record is deleted.
TodayFind deals linked to the wrong person and remove the association.
With DatapipePropose removing the link from the deal report, and you approve each one.
Removes every link between two records, including labelled ones such as a primary company. Both records stay in HubSpot, and the link can be added again with the link action. Reports and workflows that follow the link stop seeing it.
Supported fields: Records to unlink, The other record's HubSpot ID.
TodayCopy notes from a call into the deal timeline by hand.
With DatapipeChatGPT drafts a short note from your call summary and proposes it on the deal. You approve the exact text.
TodayWrite a note on each contact before someone goes on leave.
With DatapipeA teammate proposes a note per contact, and it is added to the timeline after your approval.
Adds one plain-text note, timed now, to the timeline of an existing contact, company, deal or ticket. Datapipe sends no email; HubSpot notifications and workflows may react. The record's properties are unchanged.
Supported fields: Record type, Note.
TodayFind each attendee and add them to the event list in HubSpot.
With DatapipeA teammate proposes adding each attendee from the sign-up sheet to the static list. You approve each contact.
TodayAdd companies to a call list by hand before a campaign.
With DatapipeChatGPT proposes companies from the account report for the static list, and you approve each one.
Adds one contact, company or deal to a static HubSpot list. Active lists are refused because their filters decide membership. Workflows, ad audiences and marketing emails that use the list may start including this record.
Supported fields: Static list ID.
TodayCheck each contact and take them off the static list.
With DatapipeA teammate proposes removing each contact from the list, and you approve it. The contact record stays unchanged.
TodayRemove closed deals from a static follow-up list one at a time.
With DatapipePropose removing each closed deal from the list using the pipeline report. You approve each removal.
Removes one contact, company or deal from a static HubSpot list. Active lists are refused because their filters decide membership. Workflows, ad audiences and marketing emails that use the list stop including this record; the record itself is unchanged.
Supported fields: Static list ID.
TodayFind contacts created during testing and delete them by hand.
With DatapipeA teammate proposes archiving each test contact. It goes to the recycling bin and can be restored for 90 days.
TodayDelete leftover duplicate companies one by one.
With DatapipePropose archiving each duplicate from the company report. The owner turns this action on separately and approves each one.
Archives one contact, company, deal or ticket. HubSpot moves it to the recycling bin and removes it from lists, views and reports. A HubSpot user can restore it from the recycling bin for 90 days, after which it is gone for good.
Supported fields: Archive.
| Field | Current value | Proposed value |
|---|---|---|
| Job title | Mktg mgr | Marketing Manager |
Source changes use the separate Actions & approvals workflow in Datapipe. AI tools such as ChatGPT can propose changes but never approve them. Who can turn this on?
Provider permissions still apply, and automations in HubSpot may react to approved changes.
Only fields supported by an enabled action can be proposed; some actions also support individual owner-selected writable fields.
An API key or token from your HubSpot account.
Read access for reports. The 19 change actions need edit access in HubSpot and stay off until the owner turns them on.
These reports do not reconstruct past CRM state. Custom properties use an explicit selection and stay JSON; typed custom-property columns are not included.
Nine new reports add current activities, custom-object schemas and selected records, associations and labels. These reports do not reconstruct past CRM state. Custom properties use an explicit selection and stay JSON; typed custom-property columns are not included. Task activity timestamps are due dates and call duration is in milliseconds. Account read permissions and subscription apply. Optional contact, company and deal edits remain separate: the owner enables permitted actions and approves every proposed change.
17 reporting datasets, each with its own fields. Pick one in the app, then choose your columns.
Existing contacts reporting from the connected account. Choose supported fields in the app; record availability follows permissions and the report's date rules.
Existing companies reporting from the connected account. Choose supported fields in the app; record availability follows permissions and the report's date rules.
Existing deals reporting from the connected account. Choose supported fields in the app; record availability follows permissions and the report's date rules.
Existing tickets reporting from the connected account. Choose supported fields in the app; record availability follows permissions and the report's date rules.
Existing forms reporting from the connected account. Choose supported fields in the app; record availability follows permissions and the report's date rules.
Existing campaigns reporting from the connected account. Choose supported fields in the app; record availability follows permissions and the report's date rules.
Existing pipelines reporting from the connected account. Choose supported fields in the app; record availability follows permissions and the report's date rules.
Existing marketing-email statistics; provider counters and date-window semantics apply. Logged CRM emails are a separate report.
Current accessible, non-archived records in the connected HubSpot account, independent of report dates. Activity timestamps describe the logged activity (task timestamps are due dates); they do not turn this into a historical activity-count report. Provider permissions apply.
Current accessible, non-archived records in the connected HubSpot account, independent of report dates. Activity timestamps describe the logged activity (task timestamps are due dates); they do not turn this into a historical activity-count report. Provider permissions apply.
Current accessible, non-archived records in the connected HubSpot account, independent of report dates. Activity timestamps describe the logged activity (task timestamps are due dates); they do not turn this into a historical activity-count report. Provider permissions apply.
Current accessible, non-archived records in the connected HubSpot account, independent of report dates. Activity timestamps describe the logged activity (task timestamps are due dates); they do not turn this into a historical activity-count report. Provider permissions apply.
Current accessible, non-archived records in the connected HubSpot account, independent of report dates. Activity timestamps describe the logged activity (task timestamps are due dates); they do not turn this into a historical activity-count report. Provider permissions apply.
Current custom-object definitions in this account, including labels, property definitions and required/display properties. Collections stay JSON. A HubSpot subscription and schema-read permissions may be required. These private definitions appear in connected reports, not on this public page.
Current non-archived records of one custom object type from the connected account. Enter its 2-... type ID from Custom object schemas. Optionally choose up to 100 comma-separated property names; otherwise only the primary display property is requested. Selected native property values stay together as JSON, with absent values null. Schema and record permissions/subscription are required. Dates do not reconstruct past records.
Choose a source object type, source record ID and destination object type in the connected account. One row per destination record and association type, preserving direction, category, type ID and nullable label. This is the current relationship inventory, independent of report dates; it does not load the related records' private fields.
Current association label/type definitions for an explicitly selected pair of object types. Direction matters: reverse associations can have different type IDs. Unlabeled relationships retain a null label. Account permissions apply; no relationship or schema is modified.
113 report fields across 17 datasets.
Hover or tap a field to see what it means. Custom fields from your own account appear after you connect.
No fields match. Try another search or choose All.
Claude or ChatGPT can read the same numbers. You ask in a normal sentence, and the answer stays with your report.
AI tools can also propose a HubSpot change. Only the owner can approve it.
Which opportunities in HubSpot with values over $50k have had no activity for 14 days?
Four enterprise accounts totaling $240k in pipeline with stalled momentum and their assigned account executives.
Current accessible, non-archived records in the connected HubSpot account, independent of report dates.
Use this template →Current accessible, non-archived records in the connected HubSpot account, independent of report dates.
Use this template →Current accessible, non-archived records in the connected HubSpot account, independent of report dates.
Use this template →Current accessible, non-archived records in the connected HubSpot account, independent of report dates.
Use this template →Sign in with HubSpot.
Pick where it goes. This one sends the numbers to Claude.
You're done. It refreshes every day.
| Name | Stage | Deal | Amount | Closed | Sent | ||
|---|---|---|---|---|---|---|---|
| Avery Chen | avery@northwind.example | Lead | Northwind renewal | $80.00 | Oct 27 | avery@northwind.example | 860 |
| Jordan Blake | jordan@harbor.example | Proposal | Acme expansion | $125.50 | Oct 28 | jordan@harbor.example | 410 |
| Sam Okonkwo | sam@acme.example | Won | Harbor pilot | $42.00 | Oct 29 | sam@acme.example | 155 |
Sample numbers, so you can see the shape. Your report uses your accounts.
Add both to the same project. Each keeps its own report, so you can check them side by side or ask ChatGPT or Claude a question that needs both.
Free to start. Paid plans add more data sources and refresh faster.
Free and Starter refresh once a day. Pro refreshes every hour. Agency refreshes every 15 minutes on the first 50 data sources.
No. Name a project, add a data source, then choose a report and destination.
OAuth means you sign in with the service and grant access, without pasting an API key. Datapipe works with multiple partners to provide that sign-in. Some partners already provide it. Some integrations are API-only at present, so you paste a key or token. OAuth is coming soon for some. Some partners do not provide OAuth at all. The setup steps on each integration page say how that source connects. Signing in is only how the connection is made. It is not permission to change records. Where a source supports changes, those writes stay off until the workspace owner turns specific actions on and approves each one. We do not promise OAuth on every source, and we do not share dates.
Only the workspace owner. Writes start disabled. The owner enables permitted actions and eligible teammates: owner only, all project operators and managers, or selected teammates. The owner can change this at any time, and saving new settings cancels pending proposals.
No. Teammates propose in Datapipe, and approved changes are applied through the connected HubSpot account. Nobody else gets a HubSpot login from this.
They can propose a change through Datapipe, the same way a teammate can. They can never approve it. Only the owner approves, in Actions & approvals.
Datapipe sends each approved change once and logs the result. If it cannot confirm that HubSpot received it, the request is marked Uncertain and is never retried automatically, so you can check HubSpot first.
Yes. Datapipe reads the reports on this page and can make 19 kinds of change: update contact name or job title; update company name or description; update deal name; update any approved contact property; update any approved company property; update any approved deal property; update any approved ticket property; create a contact; create a company; create a deal; create a ticket; move a deal to another pipeline stage; change a ticket's status; link two records; remove the link between two records; add a note to a record; add a record to a static list; remove a record from a static list; archive a record to the recycling bin. Each one stays off until the owner turns it on, and every proposed change needs the owner's approval. Provider permissions still apply.
This page lists 113 report fields across 17 datasets. You pick the columns when you build the report.
Available rows depend on the connected account, selected report type, its date rules and provider limits. Current-inventory reports show current records rather than earlier historical states.
One for each HubSpot account you add to a project. Adding the same account to another project counts again. Reports and destinations do not use extra data sources.
Yes. The same numbers can go to a sheet, a chart, a warehouse, or an assistant.
Build the report first, then add HubSpot when you are ready.