Get a demo

Pipeline & CRM reporting

Keep your sales pipeline tracker up to date from HubSpot or Salesforce. Pull opportunities, filter by stage, and push a clean summary to Google Sheets every cycle.

Get a demo

The prompt

I want to keep our sales pipeline tracker up to date from HubSpot. Can you build me a flow that pulls open opportunities from HubSpot, filters to the relevant pipeline stages, calculates deal counts and total values by status, and pushes a clean summary to Google Sheets?

Just copy and paste the prompt into a new Parabola flow to get started.

What Parabola builds

A workflow with six steps you can edit:

1. Pull open opportunities. API connection to HubSpot or Salesforce. The flow ingests every open deal with its stage, owner, amount, expected close date, and any custom fields you care about.

2. Filter to the relevant stages. Drop disqualified, closed-lost, and closed-won. Or keep a sliding window (last 90 days closed) for the trend view. The filter is a row in the flow, not a hard-coded rule.

3. Standardize the stage and the owner. Stage names get mapped to your reporting categories. Owner records get joined to the rep master so the report rolls up by team.

4. Calculate the metrics. Deal count by stage, total pipeline value by stage, weighted pipeline by probability, average deal size, average sales cycle. Per team, per region, per product.

5. Compare against the prior week. Net new pipeline created, deals advanced, deals slipped, deals lost. The delta is the part RevOps reads first.

6. Push to Google Sheets. Clean summary in the tracker, detail tab for the dig, optional Slack alert when a major deal slips or a forecast bucket changes.

Why teams stop doing this manually

Pipeline data is in the CRM, but the report someone actually reads lives in a Google Sheet. The RevOps analyst exports a CSV out of HubSpot or Salesforce every Monday, opens it in a spreadsheet, runs the pivots, and pastes the summary into the tracker. The tracker has tabs for each region, each segment, each rep. Each one needs its own filter, its own roll-up, its own comparison.

The work is repetitive and high stakes. The CFO looks at the weighted pipeline number to make a hiring decision. The CRO looks at the deal slips to coach the team. The CEO looks at the new logo pipeline to decide on board commentary. Each of them is reading a number the analyst built by hand over the weekend.

The math is straightforward. The work is the plumbing. Pull, filter, roll up, compare, push. That is exactly the kind of work that lives in a flow. The tracker refreshes on schedule. The detail tab is current. The exec team is reading a number that ties back to the CRM, not last week's export.

How it works

Step 1. Paste the prompt.

Open Parabola, paste the prompt in section 2, and let it ask follow-up questions about your stage definitions, your forecast methodology, and the cuts your team reports against.

Step 2. Connect your data.

API connection to HubSpot or Salesforce. Plus the Google Sheets tracker and the rep master.

Step 3. Run it every cycle.

Monday morning is the default. Daily for high-volume teams. The flow refreshes the tracker and posts the alerts before the team comes in.

Related prompts

FAQ

Does this work with Salesforce as well as HubSpot?

Yes. The CRM is a source. Swap in Salesforce or run both side by side if the team uses both for different segments.

How does the flow handle stage definitions that change?

The stage mapping is a row in a table. Update the row when stages change. The flow picks up the new mapping on the next run. The report still ties to historical data through the mapping.

Can the flow calculate weighted pipeline using a custom probability model?

Yes. Weight by stage, by deal size, by historical conversion rate, or by a custom score. The weighting logic lives in the flow and the output reflects it.

What about pipeline created versus pipeline closed-won attribution?

Tag each deal with its create date and its close date. The report can split by either dimension. Common to show both: pipeline created this quarter, closed-won attributed to source quarter.

How is this different from a native CRM dashboard?

CRM dashboards read the CRM. This flow combines the CRM with the Google Sheet tracker the team actually works in, plus the rep master, plus any custom reporting cuts. The output goes where the team reads, not where the source data lives.
One pipeline tracker, refreshed before Monday.
Paste the prompt, point it at your CRM and tracker, and let the report run on its own.
Start for free