Revenue Tracking: Zapier Setup
Last updated: July 22, 2026
This article walks you through setting up Revenue Tracking with Zapier. Unlike HubSpot and GHL (which use a stage trigger in Charlie’s settings), Zapier Revenue Tracking works entirely through a Zapier Action — there is no configuration in the Charlie dashboard.
This method is ideal if you want to send revenue data from a payment processor, invoicing tool, or any other system that connects to Zapier.
Prerequisites
A Zapier account with the Charlie AI app added
Your Charlie AI account connected via Zapier
At least one AI Setter configured in Charlie
A trigger source in Zapier (CRM, payment processor, spreadsheet, etc.) that fires when a deal closes or payment is received
Zapier Revenue Tracking configuration
With HubSpot and GHL, you configure Revenue Tracking inside Charlie’s dashboard by selecting a stage trigger and mapping properties. Charlie then listens for stage changes.
With Zapier, the approach is different:
No stage trigger — Revenue fires whenever the Zap triggers
No settings page in Charlie — Everything is configured within Zapier
Revenue values are sent directly — You pass the dollar amounts as fields in the Zap Action, rather than mapping to CRM properties
Works with any system — Any tool that connects to Zapier can send revenue data to Charlie
Step 1 — Create a New Zap
Log in to your Zapier account
Click Create Zap (or + Create → Zap)
You’ll see the Zap editor with a Trigger and Action step
Step 2 — Set Up the Trigger
The trigger determines when the revenue event fires. Choose the system that knows when a deal is closed or a payment is made.
Select your trigger app
Choose the appropriate trigger event
Connect your account and configure any filters (e.g., only trigger for “Closed Won” deals)
Test the trigger to make sure it pulls in sample data
Step 3 — Add the Charlie AI Action
For the Action step, search for and select Charlie AI
Select the Revenue Event action (this is a new action added to the Charlie Zapier App)
Connect your Charlie AI account if not already connected
Step 4 — Map the Required Fields
Lead Identifier (Required)
Provide the lead’s phone number or email address. Charlie uses this to match the revenue event to an existing lead in the system.
Map this to the phone or email field from your trigger step
At least one identifier is required
If the identifier doesn’t match any existing Charlie lead, the revenue event will not be recorded
Cash Collected
A dynamic number field. Enter the actual payment amount received.
Map this to the payment/amount field from your trigger step
Example: 10000 for $10,000
Contract Value Closed
A dynamic number field. Enter the total committed contract value.
Map this to the deal value/contract amount field from your trigger step
Example: 120000 for $120,000
Step 5 — Test and Publish
Click Test Action to send a test revenue event to Charlie
Verify the test data appears correctly
Click Publish to turn the Zap on
Once published, every time your trigger fires, the revenue data will be sent to Charlie and appear on your Performance Page.
Common triggers
Trigger App | Trigger Event | When It Fires |
|---|---|---|
Stripe | New Payment | When a payment is processed |
QuickBooks | New Payment | When a payment is received |
Any CRM | Deal/Opportunity Updated | When a deal reaches a specific stage or marked as won |
How Attribution Works with Zapier
Like HubSpot and GHL, Zapier revenue events are attributed to the Use Case (AI Setter) that most recently triggered CTA for the matched lead.
The flow:
Charlie matches the phone number or email from the Zap to an existing lead
Charlie checks if that lead has reached CTA
If yes, the revenue event is created and attributed to the most recent CTA-triggering Use Case
The metrics appear on your Performance Page
If the lead has not reached CTA through Charlie, the revenue event will not be attributed.
Multiple Revenue Events
Zapier can send multiple revenue events for the same lead. For example:
A client pays monthly — each payment fires a new Zap with the Cash Collected amount
Charlie sums up all revenue events for the same lead
This is useful for tracking cumulative cash flow over time, especially for subscription or installment-based billing.
Example Zap Configurations
Stripe → Charlie (Cash Collected on each payment)
Trigger: Stripe → New Successful Payment
Action: Charlie AI → Revenue Event
Lead Identifier: Customer email from Stripe
Cash Collected: Payment amount from Stripe
Contract Value Closed: (leave empty)
CRMs → Charlie (Contract closed)
Trigger: → Deal Status Changed to Won
Action: Charlie AI → Revenue Event
Lead Identifier: Lead phone number from Close
Cash Collected: (leave empty or map to initial payment)
Contract Value Closed: Deal value from Close
FAQ
Q: Is there a Revenue Tracking settings page in Charlie for Zapier?
No. Unlike HubSpot and GHL, Zapier Revenue Tracking has no configuration page in the Charlie dashboard. Everything is managed within Zapier.
Q: Can I send both Cash Collected and Contract Value Closed in the same Zap?
Yes. Both fields are available in the action. Fill in whichever values you have — both, or just one.
Q: What if the lead’s phone number or email doesn’t match any Charlie lead?
The revenue event will not be recorded. The identifier must match an existing lead in Charlie.
Q: Does this update the version of the Charlie Zapier App?
Yes. The Revenue Event action was added as a new action, which increases the version of the Charlie Zapier App. You may need to update the app connection if you’re on an older version.