dusk botopen the stripe invoice behind a billing question
answer the billing question with the actual bill in front of you. give the bot the customer and invoice context.
it lists or searches stripe invoices, finds the match and opens the bill. if several fit, it asks you to choose. you get invoice details in chat while billing records and payments stay untouched.
what it does
find the november bill before explaining the october one. one customer can have several invoices. a separate list or search finds the candidates; this action opens the one you choose. ask for the choices when the description fits more than one.
it can request linked details up to four levels deep. have it name what came back and leave missing details unknown.
when you would use it
- explain an unfamiliar bill. read its details before answering the customer.
- explain one invoice to a colleague. keep the findings in your chat.
- confirm which bill the client meant. compare their description with the actual invoice.
- prepare a billing answer. request supported linked customer details alongside the invoice.
try it
paste this into a chat with your bot
at noon each weekday, read emails from the last day that ask about an invoice. find the stripe invoice matching each sender and the bill they describe. ask me to choose if more than one fits.
read the matched invoice and report its status, amount and currency here. if a requested linked detail doesn't come back, say you don't know it. never send the invoice, contact the customer, edit billing records or take a payment.- when
- weekdays at noon
- needs
- gmail and stripe both read only; email reads and invoice lookup and retrieval allowed
what comes back looks like this (an example)
rosewater print asks about its november bill
- matched invoice: rw-204
- status: open
- amount: 240 usd
ready to use when you write the customer reply.set it up
- connect both sources for reading. gmail finds the question; stripe provides the bill.
- confirm a first match. describe the customer and billing context before opening the invoice.
- ask for the needed details. request related customer information too if it matters to the answer.
- compare the first answer with stripe. then schedule the daily review. use edit to narrow it if needed.
what it needs from you
| input | required | what it is |
|---|---|---|
invoice | yes | The unique identifier of the invoice to retrieve. |
expand | no | Specifies which fields in the response should be expanded. |
from composio's catalog for Stripe (action STRIPE_GET_INVOICES_INVOICE, read 12 november 20263). your bot fills these in from what you tell it.
how dusk bot handles it
dusk bot counts Retrieve Invoice as a read: it looks and changes nothing. a bot you allow only to read can use it.
the permissions Stripe asks for to run it: read_only.
where it stops
- retrieval opens one invoice. another lookup finds it first. an unclear customer name is not enough.
- linked reads stop at four levels. if a detail does not return, the bot should say it does not know.
- search can lag behind new bills. usually within a minute; outages can delay it up to an hour. try listing fresh invoices instead.
- local routines need an awake computer. a run under 12 hours late runs once on return. older runs skip; dusk cloud runs on time.
try it in 2 minutes
- pick one recent billing email
- ask the bot to find matching stripe invoices
- confirm the customer and bill
- ask for status, amount and currency, without sending
mistakes people make
picking the first bill for that customer
match the bill in the email. ask when several invoices fit.
inventing a missing linked detail
say it is unknown. request the needed detail separately if the connection supports it.
questions
can it find the invoice if i only know the customer?
it can find candidates. list or search finds the bills; retrieval opens the right one. have it ask when several fit.
will opening an invoice email it to the customer?
no. this only reads. sending an invoice is another action, outside this routine.
why is a newly created invoice missing from search?
search may not have caught up. try listing invoices, then confirm the match before opening the bill.
sources
read next
a stripe bot that reads billing before money movesbilling context before a money decision.
an invoice follow-up bot that leaves reminders for reviewthe invoice, the evidence, the reminder.
ai agents for founders and solopreneursa starter team, and the routines to copy.
claude connectors: connect the job you actually needpick a task before you connect an app.
an airtable assistant that learns the table before writingread the fields before filling the rows.
an asana assistant for the work between tasksfind the work holding up the handoff.
drafted with ai help from the dusk bot docs and the sources listed on this page, then checked against them. if something here is wrong or out of date, write to [email protected].