Datapipe
Start free

Finance · USE CASE

Review unpaid invoices alongside open support tickets.

Use Stripe to find the remaining invoice balance and Zendesk to understand the customer’s open questions. Give finance and support one coordinated follow-up list.

Data sources
Assistant
Destination
Try it with your data Free with up to 3 data sources · No credit card
A WORKED EXAMPLE

Which unpaid invoices need a support check?

InvoiceRemaining · USDTickets
Cedar · in_1042$120.002
Maple · in_1048$450.001

Invoices created Aug 13–Nov 10, 2026 UTC · Current state Nov 10, 12:00 UTC

Review Cedar’s payment-link question before the next recorded retry. Two unpaid invoices total $570; group the three support tickets with their invoices before agreeing the next contact.

WHERE THE RESULT GOES

Google Sheets

Export each data source report to Google Sheets, then add your analysis or checklist to the review Sheet.

Example use case

Ask. Follow up.
Take the next step.

✦ AI assistantSample use case
StripeZendesk
YOU

  1. 01
    in_1042 · Tickets 3814 and 3816Coordinate before retry

    Next

  2. 02
    in_1048 · Ticket 3820Review with finance

    Next

Invoices created Aug 13–Nov 10, 2026 UTC · Current state Nov 10, 12:00 UTC

01 · CONNECT YOUR DATA

Your tools. One place to ask.

2 of 3 Free data sources
No credit card · Daily refresh

DatapipeYour project
Your AI assistantor a report in Sheets / Data Studio
  1. Create your free workspace

    Sign up with your company email. Your first project opens on Data sources.

  2. Add the data sources

    Choose the accounts for this use case. Authorize access and select the property or site.

  3. Bring your question

    Connect your project to a supported AI assistant, or build your source reports.

Create a free account →
Setup steps & what you need

Email/password signups confirm their email first. Use Google signup with a company account if you prefer.

  • Stripe: Authorize the intended Stripe account using its supported sign-in or dedicated read-key setup. Setup guide ↗
  • Zendesk: Enter your Zendesk subdomain and authorize the intended account using its supported setup. Setup guide ↗

Free includes 3 data sources across the workspace. One account/property added to one project counts as one. Extra properties or the same account in another project use another slot.

02 · ASK A USEFUL QUESTION

Start with a prompt.
Follow the evidence.

Copy these in order into your connected assistant.
Each builds on the answer before it.

01

Find the invoice follow-ups worth reviewing

Read the full prompt
Use only this Datapipe project’s authorized data. Discover the connected accounts, datasets and compatible fields first. Confirm dates, timezones, currencies and data coverage. Keep missing or unmatched rows visible; never substitute sample data. Compare the sources explicitly and explain every match. Do not change source records or send messages.

From the connected Stripe account, read the invoice resource only. Use a 90-day creation window ending today in UTC and show its actual boundaries. Return invoice.id, invoice.customer, invoice.customer_name, invoice.created, invoice.status, invoice.amount_remaining, invoice.currency, invoice.collection_method, invoice.attempted, invoice.attempt_count and invoice.next_payment_attempt. Keep open invoices with positive remaining amounts. Preserve raw currency amounts and explain the display conversion. Keep currencies separate. This is a creation-window shortlist, not a complete aged-receivables report; ask whether older invoices must be included. An attempt count alone does not identify the latest failure reason.
02

Add the matched Zendesk customer questions

Read the full prompt
Read Zendesk Users with users.id and users.external_id, and Expanded current tickets with tickets_expanded.id, requester_id, subject and status. Confirm with me whether users.external_id contains the Stripe customer ID before joining; if that convention is not established, ask for a verified mapping and keep the customers unmatched. Match tickets to users by requester_id, then to invoice.customer by that verified external ID. Keep new/open/pending/hold tickets as unresolved. Show ticket IDs, current subjects/statuses, read time, coverage gaps and ambiguous matches. These are current records, not ticket status as of invoice creation. Do not infer a payment-failure cause from a ticket subject.
03

Prepare a coordinated finance and support review

Read the full prompt
Produce one row per invoice with its remaining amount/currency, collection method, attempt count, next-payment timestamp if present, matched unresolved ticket IDs and subjects, mapping evidence, next review and the person or team to involve. Aggregate tickets before matching to invoices so invoice balances are counted once. Summarize distinct-invoice amounts by currency; never add different currencies. In this conversation, draft the question finance and support should resolve before another reminder. Mark missing ownership, ambiguous identity, older-invoice coverage and unknown retry settings for review. Re-read current records before the team acts. Do not charge a customer, retry a payment, change an invoice, send a reminder or update a ticket.
Need to connect your assistant?Claude guide ↗ChatGPT guide ↗

03 · USE WHAT YOU FIND

Agree one next step for each invoice.

  1. 01

    Read the unpaid invoice evidence from Stripe.

  2. 02

    Match each customer to the actual support conversation.

  3. 03

    Agree one next step for each invoice.

Check the result at your next review.

At the next review, re-read each invoice’s status and remaining amount and the matched tickets’ current statuses. Track which reviews were completed and whether the balance remains outstanding. A later payment does not establish that the coordinated follow-up caused it.

Implementation tips for this use case

Stripe supplies the balance and collection context; Zendesk supplies the unresolved customer question. Group the ticket evidence by customer, then retain one review row per invoice. New, open, pending and hold tickets are unresolved; solved and closed tickets stay outside that group. Ask finance and the support owner to review the next contact, then copy the agreed list to the team’s Sheet. Recheck the invoice and ticket immediately before acting.

WHEN YOU NEED MORE CONTEXT

Go a little deeper.

The method and reporting checks
behind this example.

How to combine unpaid invoice evidence with current support context

  1. Read the unpaid invoice evidence from Stripe.

    Add the intended Stripe account and Zendesk account to the same project. Discover Stripe’s invoice fields, then read invoice ID, customer ID, customer name, created timestamp, status, remaining amount, currency, collection method, attempted flag, attempt count and next-payment timestamp. The selected dates filter invoice creation, not when a payment failed. Keep open invoices with a positive remaining amount and widen the creation window when older invoices matter.

  2. Match each customer to the actual support conversation.

    Read Zendesk Users and Expanded current tickets as separate reports. Link requester_id to the user’s ID. Use external_id as the Stripe customer ID only after confirming that your team stores that identifier there; the example uses this verified convention. Otherwise, agree a reliable mapping first. Keep ambiguous, missing and unmatched customers visible. Zendesk returns current accessible records, independently of the Stripe creation window; archived tickets or restricted records can be absent.

  3. Agree one next step for each invoice.

    Stripe supplies the balance and collection context; Zendesk supplies the unresolved customer question. Group the ticket evidence by customer, then retain one review row per invoice. New, open, pending and hold tickets are unresolved; solved and closed tickets stay outside that group. Ask finance and the support owner to review the next contact, then copy the agreed list to the team’s Sheet. Recheck the invoice and ticket immediately before acting.

See the complete example report
EXAMPLE REPORTFictional sample data

Which unpaid invoices need a support check?

Invoices created Aug 13–Nov 10, 2026 UTC · Current state Nov 10, 12:00 UTC

Which unpaid invoices need a support check? · fictional sample data
InvoiceRemaining · USDTickets
Cedar · in_1042$120.002
Maple · in_1048$450.001
WHAT TO LOOK ATReview Cedar’s payment-link question before the next recorded retry. Two unpaid invoices total $570; group the three support tickets with their invoices before agreeing the next contact.

Agree one next step for each invoice.

Stripe shows an open invoice with $120 remaining, two recorded payment attempts and a next attempt on Nov 11 at 09:00 UTC. The matched Zendesk requester has an open payment-link question and a pending billing-contact conversation. Stripe shows an open invoice with $450 remaining and one recorded attempt. The matched requester has a pending question about the company name. No next-payment timestamp is returned in this example.

Try the example with sample CSVs

Fictional rows matching the example above. Attach these files to your assistant for a sample analysis.

Data method, reporting checks & sources

Add the intended Stripe account and Zendesk account to the same project. Discover Stripe’s invoice fields, then read invoice ID, customer ID, customer name, created timestamp, status, remaining amount, currency, collection method, attempted flag, attempt count and next-payment timestamp. The selected dates filter invoice creation, not when a payment failed. Keep open invoices with a positive remaining amount and widen the creation window when older invoices matter. Read Zendesk Users and Expanded current tickets as separate reports. Link requester_id to the user’s ID. Use external_id as the Stripe customer ID only after confirming that your team stores that identifier there; the example uses this verified convention. Otherwise, agree a reliable mapping first. Keep ambiguous, missing and unmatched customers visible. Zendesk returns current accessible records, independently of the Stripe creation window; archived tickets or restricted records can be absent. Stripe supplies the balance and collection context; Zendesk supplies the unresolved customer question. Group the ticket evidence by customer, then retain one review row per invoice. New, open, pending and hold tickets are unresolved; solved and closed tickets stay outside that group. Ask finance and the support owner to review the next contact, then copy the agreed list to the team’s Sheet. Recheck the invoice and ticket immediately before acting.

Each balance is counted once per invoice, even when a customer has several tickets or several invoices. The Stripe creation-date window and current Zendesk capture are explicit; older invoices and archived tickets can fall outside coverage. The requester-to-user match and the external-ID convention are verified; an absent match is not evidence of no support conversation. USD cents are divided by 100 in this example. Other currencies follow their own minor-unit rules and remain separate.

  • Each balance is counted once per invoice, even when a customer has several tickets or several invoices.
  • The Stripe creation-date window and current Zendesk capture are explicit; older invoices and archived tickets can fall outside coverage.
  • The requester-to-user match and the external-ID convention are verified; an absent match is not evidence of no support conversation.
  • USD cents are divided by 100 in this example. Other currencies follow their own minor-unit rules and remain separate.
  • Access to the intended Stripe account or property.
  • Access to the intended Zendesk account or property.
  • Each balance is counted once per invoice, even when a customer has several tickets or several invoices.

For blended reports, align dates, normalized URLs, and reporting grain. Query-level search rows must not duplicate page-level sessions.

Stripe invoice fields ↗Stripe invoice listing and creation-date filters ↗Stripe currency minor units ↗Zendesk requester IDs and ticket status ↗Zendesk user IDs and external IDs ↗Report starting points ↗

A FEW USEFUL ANSWERS

Before you start.

Why do I need both Stripe and Zendesk?

Stripe provides the invoice balance, currency and collection context. Zendesk provides the customer’s unresolved questions. The combined list helps finance and support agree the next contact instead of working from separate queues.

Can I match a Zendesk user to Stripe automatically?

Only with an established identity rule. In this example, Zendesk external_id already contains the Stripe customer ID. Confirm that convention for your account. Display names, similar email addresses and ticket wording are not a reliable substitute.

Does an open invoice with previous attempts prove the latest payment failed?

No. It is a reason to review the current payment state and collection settings. The invoice fields shown here do not supply a verified latest failure reason, and a missing next-payment timestamp is not a promise that no retry will occur.

Will this find every outstanding invoice?

The invoice report selects records by creation date, so older outstanding invoices need a wider creation window. Zendesk visibility and archive limits also affect coverage. Keep those gaps on the review list.

YOUR NEXT STEP

Try it with your own data.

Start free with up to 3 data sources. No credit card.

Start free →