DatapipeSales · USE CASE
Ask Claude to define the current-stage review, export HubSpot pipeline data to Sheets, and build a custom dashboard with clearly scoped deal counts and values.
Build a dashboard for our HubSpot pipeline review.
Confirm the intended portal and pipeline. Read current accessible deal counts and values by stage using the source’s stage definitions.
Illustrated use case. Save the actual report, dashboard and schedule settings in the indicated app.
MAKE THE TASK CONCRETE
Confirm the intended portal and pipeline. Read current accessible deal counts and values by stage using the source’s stage definitions.
Save the HubSpot report, authorize Sheets and build custom charts from the populated export. Reconcile the selected pipeline and stage labels before sharing.
Compare the dashboard with the current source and account for changed deals between reads. Avoid implying that a date filter reconstructs historical pipeline state.
KNOW WHERE EACH STEP HAPPENS
START WITH YOUR ASSISTANT
Copy these in order into the assistant connected to your Datapipe project.
Use only the intended Datapipe project. Discover the account, datasets and compatible fields first. Use actual returned dates and filters; preserve empty or missing results and never substitute sample data for a failed read. Build a HubSpot pipeline dashboard with Claude in Looker Studio. Current pipeline state is not stage history, conversion rate or guaranteed revenue. Validate pipeline and currency context.
Show which stages need a closer look. Plan stage-count and stage-value charts. Keep currencies separate and explain that this is current pipeline state, not historical stage conversion or a revenue forecast. Prepare the checklist without claiming completion. Save reports, destination authorization, schedules and recipients in Datapipe; build custom native charts in Looker Studio. The AI tools do not perform those setup steps.
Check the pipeline dashboard for the sales meeting. Compare the dashboard with the current source and account for changed deals between reads. Avoid implying that a date filter reconstructs historical pipeline state. Current pipeline state is not stage history, conversion rate or guaranteed revenue. Validate pipeline and currency context. Prepare the checklist without claiming completion. Save reports, destination authorization, schedules and recipients in Datapipe; build custom native charts in Looker Studio. The AI tools do not perform those setup steps.
A FEW USEFUL ANSWERS
No. This worked view uses current pipeline records. Historical transitions and conversion analysis require appropriate separate history and defined cohorts.
Prepare the checklist without claiming completion. Save reports, destination authorization, schedules and recipients in Datapipe; build custom native charts in Looker Studio. The AI tools do not perform those setup steps.
No. The conversation and output are labeled illustrations. Review the actual source account, permissions, fields and destination before doing the task. Current pipeline state is not stage history, conversion rate or guaranteed revenue. Validate pipeline and currency context.
YOUR NEXT STEP
Choose your source in Datapipe and review the setup before saving.