Resources · Claude connector

Claude Qonto connectorWhat Claude can do in your Qonto account.

The Claude Qonto connector exposes 52 tools. 26 read your accounts, invoices, cards and requests, 25 change something in Qonto, and 1 is documented nowhere. Below: what Claude reads, what it can do, and where Qonto keeps the last word.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes once Claude can reach your Qonto account

Qonto is a business account, and its connector gives Claude a curated set of tools on it: read your transactions and statements, bill clients, manage cards and handle expense requests. Every call runs with your own Qonto role, so Claude cannot do more than you can. The money-moving steps, approving a transfer or a sensitive card, stay in the Qonto apps.

Read your books without exporting them. list_transactions, list_client_invoices and list_supplier_invoices let Claude answer which clients are late or what is still due this month.

Bill from the conversation. create_client_invoice drafts an invoice, send_client_invoice sends it by email or e-invoice, and mark_client_invoice_as_paid closes it when the money arrives.

Keep cards under control. create_card, update_card and change_card_status issue, adjust or lock cards, within your role.

What the connector does not do: Qonto says it does not cover SEPA transfers to a beneficiary, international transfers, webhooks, terminals or onboarding. It prepares a multi-transfer batch but never approves it; approval happens in the Qonto web app, and sensitive actions need strong authentication in the mobile app. Nothing runs on its own either. For hands-off bookkeeping flows, an automation tool does that job, covered on our Qonto Make integration page.

Vocabulary

Five words before you connect

The vocabulary Claude uses around this connector, in one minute.

Connector
A link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
Tool
One named thing the connector lets Claude do. Claude chooses the tools it needs by itself, and the directory lists them by name.
Authorization
The Qonto sign-in screen where you hand Claude the access it will use. Given once per person, and it can be taken back.
Approval
The confirmation Claude waits for before it does something that changes your account, shown in the chat at the right moment.
MCP
The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Qonto.
Connect

Connect Qonto to Claude in three steps

  1. 01

    Find Qonto in Claude

    Open Claude's settings, go to Customize then Connectors, and look for Qonto in the list. On a Team or Enterprise workspace, an Owner or Primary Owner enables the connector first; each member then signs in on their own.

  2. 02

    Start the connection

    Click Connect on the Qonto row, then sign in to Qonto in the window the service opens itself, not inside Claude. If the link breaks later, use Disconnect and connect again.

  3. 03

    Read the authorization screen

    Check what the screen lists before you accept. It belongs to Qonto, not to Claude, and it sets what the access covers. You can also withdraw that access later from your Qonto account.

Tools

The 52 tools, split by what they do

Qonto gives Claude 52 tools: 26 that read your account, 25 that change something in it, and 1 no official source describes.

Three groups: what Claude reads, what it changes, and what no official source describes. Tool names stay as Claude shows them.

  • 26 read
  • 25 write
  • 1 not documented

What Claude can read in Qonto

26 tools

26 tools that read accounts, invoices, cards, members and requests. Several return short-lived links that act as credentials.

approve_request

Returns a link to the approval page of a pending request in the Qonto web app. It does not approve anything itself: the approver confirms there, where any strong authentication happens.

When it helps
a manager wants the pending card requests from the design team in one click.

Sourcedocs.qonto.com · September 30, 2026 ↗

get_attachment

Fetches one receipt or document attached in Qonto, with a short-lived download link and, when it exists, the probative PAdES version.

When it helps
your accountant asks for the invoice behind one card payment.
Watch out
the link is a temporary credential; do not paste it anywhere public.

Sourcedocs.qonto.com · September 30, 2026 ↗

get_authenticated_membership

Returns your own membership, the Qonto user behind the connection, so Claude knows which role it is acting with.

When it helps
a request is refused and you want to check which role you connected with.
Watch out
role names follow Qonto's vocabulary: owner, admin, accountant, manager, employee or reporting.

Sourcedocs.qonto.com · September 30, 2026 ↗

get_card_iframe_url

Returns a short-lived link that displays a card's full number, expiry date and security code inside a secure frame.

When it helps
you need a virtual card's details to pay a supplier online right now.
Watch out
Qonto says to treat that link like a password.

Sourcedocs.qonto.com · September 30, 2026 ↗

get_client

Opens one client record in full, found by its identifier.

When it helps
before preparing a quote, you check the client's VAT number is on file.
Watch out
you only see the clients your Qonto role gives you access to.

Sourcedocs.qonto.com · September 30, 2026 ↗

get_client_invoice

Fetches one client invoice with the heavier details the list leaves out, such as regulatory blocks and electronic invoicing events.

When it helps
a client says they never received an e-invoice and you want its delivery status.
Watch out
a finalized invoice can no longer be edited or deleted, only canceled.

Sourcedocs.qonto.com · September 30, 2026 ↗

get_credit_note

Opens one credit note in full, the document that refunds part or all of a client invoice.

When it helps
you want the exact amount and lines of the refund you issued last month.
Watch out
a credit note always ties back to one existing client invoice.

Sourcedocs.qonto.com · September 30, 2026 ↗

get_organization

Returns your organization and its bank accounts, with IBAN, BIC, currency, balance and status for each.

When it helps
a partner asks for your main account IBAN and you want it without opening the app.
Watch out
one connection covers one organization; another company needs its own authorization.

Sourcedocs.qonto.com · September 30, 2026 ↗

get_quote

Fetches a single quote together with its public link, the page your client sees.

When it helps
the client lost the quote email and you want to resend the link by hand.
Watch out
a new quote sits in pending approval at first.

Sourcedocs.qonto.com · September 30, 2026 ↗

get_statement

Fetches one monthly account statement with its download link, for the month you name.

When it helps
your bank-loan file needs the March statement today.
Watch out
the file link is a credential; Qonto says to treat it like a password.

Sourcedocs.qonto.com · September 30, 2026 ↗

get_supplier_invoice

Opens one supplier invoice with its status, supplier, amounts, taxes, IBAN, matched transactions, approval workflow and available actions.

When it helps
a supplier chases payment and you want to see where the invoice is stuck.
Watch out
rejecting an invoice is irreversible, so read this record before asking for it.

Sourcedocs.qonto.com · September 30, 2026 ↗

get_transaction

Fetches one transaction in detail, in the same shape as the transaction list.

When it helps
an unknown debit appears and you want its counterparty, amount and date in one answer.
Watch out
asking for many transactions one by one can hit the API's rate limits.

Sourcedocs.qonto.com · September 30, 2026 ↗

list_cards

Lists the organization's cards, debit, credit, virtual, flash or advertising, page by page.

When it helps
you want to see which cards are still active after a teammate left.
Watch out
full card numbers never show here; they need a separate short-lived secure link.

Sourcedocs.qonto.com · September 30, 2026 ↗

list_client_invoices

Lists the invoices you issued to clients, filterable by draft, unpaid, paid or canceled, so Claude can see who owes what.

When it helps
you ask which clients have not paid in the last sixty days.
Watch out
a draft in this list has not reached your client yet.

Sourcedocs.qonto.com · September 30, 2026 ↗

list_clients

Lists your clients, with filters on tax number, VAT number, email and name.

When it helps
you want to know whether a company is already on file under another spelling.
Watch out
your role decides which clients appear in the answer.

Sourcedocs.qonto.com · September 30, 2026 ↗

list_credit_notes

Lists the credit notes linked to your client invoices, partial or full refunds.

When it helps
closing the quarter, you want every refund issued to one customer.
Watch out
each credit note is tied to one client invoice, never floating on its own.

Sourcedocs.qonto.com · September 30, 2026 ↗

list_labels

Lists the labels your team uses to tag transactions, including the one level of nesting Qonto allows.

When it helps
you want spending grouped by the labels your finance team already uses.
Watch out
the tool for reading a single label, get_label, is not documented by Qonto.

Sourcedocs.qonto.com · September 30, 2026 ↗

list_memberships

Lists the members of your organization with their role, team, country, birthdate and nationality.

When it helps
you check who holds an admin role before an audit.
Watch out
the list carries personal data, so keep answers inside the team.

Sourcedocs.qonto.com · September 30, 2026 ↗

list_products

Lists your catalog of goods and services, the items you reuse as lines on invoices, quotes and credit notes.

When it helps
you want the right product lines before Claude drafts an invoice.
Watch out
each product carries the VAT rate it was given at creation.

Sourcedocs.qonto.com · September 30, 2026 ↗

list_quotes

Lists your client quotes, the commercial offers issued before invoicing, with where each one stands.

When it helps
on Monday you review which quotes are still waiting for an answer.
Watch out
the list follows what your Qonto role is allowed to see.

Sourcedocs.qonto.com · September 30, 2026 ↗

list_requests

Lists expense requests, flash or virtual cards, transfers and multi-transfers. What you see follows your role: employees their own, managers their team's, admins and owners everything.

When it helps
an approver wants the queue before a Friday cut-off.
Watch out
Claude cannot approve from here; it can only hand you the approval link.

Sourcedocs.qonto.com · September 30, 2026 ↗

list_statements

Lists your monthly account statements with their period, bank account and file, so Claude can point to the right month.

When it helps
your accountant wants the last six statements in one go.
Watch out
each file link is a short-lived credential.

Sourcedocs.qonto.com · September 30, 2026 ↗

list_supplier_invoices

Lists supplier invoices page by page, with a filter that narrows the list to one status at a time.

When it helps
you want everything still outstanding before the monthly payment run.
Watch out
since the filter takes one status, seeing everything still due can take more than one request.

Sourcedocs.qonto.com · September 30, 2026 ↗

list_teams

Lists your organization's teams with their names.

When it helps
you want spending or requests broken down by team and need the team list first.
Watch out
it returns each team's identifier and name, and nothing about what that team spends.

Sourcedocs.qonto.com · September 30, 2026 ↗

list_transaction_attachments

Lists the attachments tied to one transaction, each with a short-lived link.

When it helps
you check whether a restaurant payment already has its receipt.
Watch out
Qonto says those links are short-lived credentials, so keep them out of shared channels.

Sourcedocs.qonto.com · September 30, 2026 ↗

list_transactions

Lists the transactions on one bank account, page by page. Qonto returns completed, declined and reversed ones only.

When it helps
you ask for last week's card payments on the main account.
Watch out
pending operations are not in the list.

Sourcedocs.qonto.com · September 30, 2026 ↗

What Claude can change in Qonto

25 tools

25 tools that create, send, change or delete. Qonto's own approval logic and strong authentication still apply.

change_card_status

Approval: see the rule

Changes a card's state: lock, unlock, report lost or stolen, or discard. Only locking can be undone, and only owners and admins can unlock.

What Claude asks for
Qonto documents no prompt specific to this tool; Claude shows its usual permission request the first time the tool runs in a session, and the general rule below applies.
When it helps
a card went missing on a trip and you want it locked at once.
Watch out
lost, stolen and discard are irreversible.

Sourcedocs.qonto.com · September 30, 2026 ↗

change_client_invoice_status

Approval: see the rule

Moves a client invoice through its life: finalize a draft, which locks it against edits, or cancel an unpaid one for good.

What Claude asks for
per Qonto's guide, a permission prompt appears the first time this tool is used in a session, with Allow once or Allow always; Qonto's own approval logic for writes then applies.
When it helps
the draft is checked and ready to become a real invoice.
Watch out
cancelling is irreversible.

Sourcedocs.qonto.com · September 30, 2026 ↗

change_supplier_invoice_status

Approval: see the rule

Changes a supplier invoice's status: reject it, which cannot be undone, or mark and unmark it as paid.

What Claude asks for
the one documented pause is the prompt Qonto describes at each tool's first use in a session; after that, the general rule below and your Qonto role apply.
When it helps
an invoice was paid outside Qonto and should stop appearing as due.

Sourcedocs.qonto.com · September 30, 2026 ↗

create_card

Approval: see the rule

Creates one card, with a card level that selects which variant you get.

What Claude asks for
Qonto describes a prompt at the first use of each tool in a session, where you pick Allow once or Allow always; the approvals section covers the rest.
When it helps
your ad spend needs its own card, separate from the team's everyday ones.
Watch out
physical cards trigger strong authentication in the Qonto mobile app.

Sourcedocs.qonto.com · September 30, 2026 ↗

create_card_request

Approval: see the rule

Files a request for a flash or virtual card for yourself, which then waits for approval before any card is issued.

What Claude asks for
Qonto documents no prompt specific to this tool; Claude shows its usual permission request the first time the tool runs in a session, and the general rule below applies.
When it helps
you need a card for a conference and your role cannot create one directly.

Sourcedocs.qonto.com · September 30, 2026 ↗

create_client

Approval: see the rule

Adds a client to Qonto, as an individual, a freelancer or a company, with the identity fields each kind needs.

What Claude asks for
per Qonto's guide, a permission prompt appears the first time this tool is used in a session, with Allow once or Allow always; Qonto's own approval logic for writes then applies.
When it helps
you signed a new customer and want them ready for the first invoice.

Sourcedocs.qonto.com · September 30, 2026 ↗

create_client_invoice

Approval: see the rule

Creates a client invoice, which starts as a draft unless you ask otherwise, so you can check it before it goes anywhere.

What Claude asks for
the one documented pause is the prompt Qonto describes at each tool's first use in a session; after that, the general rule below and your Qonto role apply.
When it helps
the job is done and you dictate the lines to Claude.

Sourcedocs.qonto.com · September 30, 2026 ↗

create_credit_note

Approval: see the rule

Issues a credit note against an existing invoice, in the same currency and never above the invoice total.

What Claude asks for
Qonto describes a prompt at the first use of each tool in a session, where you pick Allow once or Allow always; the approvals section covers the rest.
When it helps
a client returned part of an order and you owe a partial refund.

Sourcedocs.qonto.com · September 30, 2026 ↗

create_membership

Approval: see the rule

Invites a new member as an employee or a reporting user and sends the activation email.

What Claude asks for
Qonto documents no prompt specific to this tool; Claude shows its usual permission request the first time the tool runs in a session, and the general rule below applies.
When it helps
a new hire starts Monday and needs access.

Sourcedocs.qonto.com · September 30, 2026 ↗

create_multi_transfer_request

Approval: see the rule

Bundles between 1 and 400 SEPA transfers into one request, which an approver later signs with strong authentication in the Qonto web app.

What Claude asks for
per Qonto's guide, a permission prompt appears the first time this tool is used in a session, with Allow once or Allow always; Qonto's own approval logic for writes then applies.
When it helps
month-end supplier payments go in one batch for the finance lead.
Watch out
Claude prepares the batch; the money only moves once an approver signs.

Sourcedocs.qonto.com · September 30, 2026 ↗

create_product

Approval: see the rule

Adds a product or service to your catalog, with a title, a type, a unit price and a VAT rate.

What Claude asks for
the one documented pause is the prompt Qonto describes at each tool's first use in a session; after that, the general rule below and your Qonto role apply.
When it helps
you launch a new service and want it available as an invoice line.
Watch out
the title is capped at 120 characters.

Sourcedocs.qonto.com · September 30, 2026 ↗

create_quote

Approval: see the rule

Drafts a new quote for a client, which starts in a pending approval state.

What Claude asks for
Qonto describes a prompt at the first use of each tool in a session, where you pick Allow once or Allow always; the approvals section covers the rest.
When it helps
a prospect wants a price by tonight.
Watch out
creating the quote does not send it; emailing it is a separate tool, send_quote.

Sourcedocs.qonto.com · September 30, 2026 ↗

create_team

Approval: see the rule

Creates a new team in your Qonto organization.

What Claude asks for
Qonto documents no prompt specific to this tool; Claude shows its usual permission request the first time the tool runs in a session, and the general rule below applies.
When it helps
you open a sales team and want its members and cards grouped from day one.

Sourcedocs.qonto.com · September 30, 2026 ↗

decline_request

Approval: see the rule

Declines a pending request: it moves to declined and the underlying action, card or transfer, never runs.

What Claude asks for
per Qonto's guide, a permission prompt appears the first time this tool is used in a session, with Allow once or Allow always; Qonto's own approval logic for writes then applies.
When it helps
a duplicate card request slipped into the queue.

Sourcedocs.qonto.com · September 30, 2026 ↗

delete_client

Approval: see the rule

Permanently deletes a client. Recurring invoices on that client are canceled, while issued invoices keep showing its details.

What Claude asks for
the one documented pause is the prompt Qonto describes at each tool's first use in a session; after that, the general rule below and your Qonto role apply.
When it helps
a test client created by mistake clutters your list.
Watch out
there is no undo.

Sourcedocs.qonto.com · September 30, 2026 ↗

delete_client_invoice

Approval: see the rule

Deletes a client invoice, but only while it is still a draft.

What Claude asks for
Qonto describes a prompt at the first use of each tool in a session, where you pick Allow once or Allow always; the approvals section covers the rest.
When it helps
you started an invoice for the wrong client.
Watch out
a finalized invoice has to be canceled through its status instead.

Sourcedocs.qonto.com · September 30, 2026 ↗

delete_quote

Approval: see the rule

Removes a quote from Qonto for good.

What Claude asks for
Qonto documents no prompt specific to this tool; Claude shows its usual permission request the first time the tool runs in a session, and the general rule below applies.
When it helps
a quote went out with the wrong prices and you are replacing it.
Watch out
the deletion cannot be undone.

Sourcedocs.qonto.com · September 30, 2026 ↗

mark_client_invoice_as_paid

Approval: see the rule

Marks an unpaid client invoice as paid and stamps the payment date, today by default.

What Claude asks for
per Qonto's guide, a permission prompt appears the first time this tool is used in a session, with Allow once or Allow always; Qonto's own approval logic for writes then applies.
When it helps
a client paid by cheque and the invoice still shows as due.

Sourcedocs.qonto.com · September 30, 2026 ↗

remove_transaction_attachment

Approval: see the rule

Detaches a file from a transaction. The file itself stays in Qonto, and other transactions using it are unaffected.

What Claude asks for
the one documented pause is the prompt Qonto describes at each tool's first use in a session; after that, the general rule below and your Qonto role apply.
When it helps
the wrong receipt was matched to a payment.

Sourcedocs.qonto.com · September 30, 2026 ↗

send_client_invoice

Approval: see the rule

Sends a client invoice either by email or through the electronic invoicing network. Neither channel changes the invoice status.

What Claude asks for
Qonto describes a prompt at the first use of each tool in a session, where you pick Allow once or Allow always; the approvals section covers the rest.
When it helps
the invoice is final and the client expects it today.
Watch out
an electronic submission cannot be recalled.

Sourcedocs.qonto.com · September 30, 2026 ↗

send_quote

Approval: see the rule

Emails a quote to one or more recipients.

What Claude asks for
Qonto documents no prompt specific to this tool; Claude shows its usual permission request the first time the tool runs in a session, and the general rule below applies.
When it helps
the buyer and their finance contact both need the offer.
Watch out
check the recipients: an email, once sent, stays sent.

Sourcedocs.qonto.com · September 30, 2026 ↗

update_card

Approval: see the rule

Changes one of two things on a card: its nickname, or its options.

What Claude asks for
per Qonto's guide, a permission prompt appears the first time this tool is used in a session, with Allow once or Allow always; Qonto's own approval logic for writes then applies.
When it helps
a card's nickname no longer says who uses it.
Watch out
physical cards reject contactless changes.

Sourcedocs.qonto.com · September 30, 2026 ↗

update_client

Approval: see the rule

Edits an existing client record, found by its identifier.

What Claude asks for
the one documented pause is the prompt Qonto describes at each tool's first use in a session; after that, the general rule below and your Qonto role apply.
When it helps
a client moved offices and the billing address must follow.

Sourcedocs.qonto.com · September 30, 2026 ↗

update_client_invoice

Approval: see the rule

Edits a draft invoice. Finalized, canceled or paid invoices refuse any update.

What Claude asks for
Qonto describes a prompt at the first use of each tool in a session, where you pick Allow once or Allow always; the approvals section covers the rest.
When it helps
the client asks for a purchase order number on the draft.

Sourcedocs.qonto.com · September 30, 2026 ↗

update_quote

Approval: see the rule

Changes a client quote already saved in Qonto, found by its identifier.

What Claude asks for
Qonto documents no prompt specific to this tool; Claude shows its usual permission request the first time the tool runs in a session, and the general rule below applies.
When it helps
after a negotiation call, one line needs a new price.
Watch out
the public link your client already has will show the change.

Sourcedocs.qonto.com · September 30, 2026 ↗

Not documented

1 tool

One name the directory publishes that Qonto's tool reference never mentions.

get_label

No official source describes this tool: the directory publishes its name and nothing else. We do not read a purpose into the name, however clear it may look, and this note stops there.

Watch out
the general approval rule described below still covers it.
Approvals

What Claude checks with you first

By default, Claude stops and asks before each action it takes on an account for someone. Qonto adds that Claude asks permission the first time each tool runs in a session.

On Team and Enterprise workspaces, owners decide whether a member may let some actions through without being asked each time. They can also limit what a connector may do for the whole organization, for example leaving reads open and closing writes. Nobody overrides that from a personal account. Claude also works with the rights of the person who connected, nothing more: Qonto says the server cannot exceed your role.

Plans

Which plans include it

None of the 819 sheets in the official directory shows plan availability. The answer per connector is published nowhere.

The published rule is general: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organization before members can each connect. For the live state of this one, check the Qonto sheet in the official directory. Qonto's own guide names specific plans; the limits section below sets both texts side by side.

Limits

Where this connector stops

A connector is not an automation. Claude calls these tools while it answers you, so nothing starts when a payment lands or an invoice falls due.

Everything here comes from Qonto's developer documentation and the directory sheet: no Claude help page covers this connector. The badge in the directory is not a security audit, and Anthropic says on each sheet that it neither picks a publisher's tools nor guarantees their behavior. Qonto also warns that connecting shares your account data with the AI provider and lifts professional secrecy in that respect. Other finance apps are in our Integrations hub.

Two official sources disagree

Which Claude plans can use the Qonto connector?

What this page followsNeither text is outdated. Anthropic's rule covers every connector; Qonto's line is narrower, but it is the publisher speaking, not Anthropic. Check the directory sheet on your own account before relying on either.

Need help

Need help connecting Qonto to Claude?

A person reads every message.

FAQ

Questions about the Claude Qonto connector

01What can Claude do with the Qonto connector?
Claude can read your Qonto business account and act on part of it from a conversation. The 26 read tools cover transactions, statements, attachments, clients, invoices, quotes, credit notes, supplier invoices, cards, members, teams, labels and requests. The 25 write tools create and send client invoices and quotes, manage clients and products, create and adjust cards, invite members and file or decline requests. One further tool is listed by name only.
02Can Claude send invoices or move money in Qonto?
It can send invoices and quotes, but it does not move money on its own. Claude can draft, finalize, send and mark client invoices as paid, and it can prepare a batch of up to 400 SEPA transfers as a request. That batch only goes out once an approver signs it with strong authentication in the Qonto web app. Transfers to a beneficiary and international transfers are not covered at all.
03Does Claude ask before it acts in Qonto?
Yes, at several levels. Claude's default rule is to ask before an action it takes on an account for someone, and Qonto's guide adds that Claude shows a permission prompt the first time each tool is used in a session, with Allow once or Allow always. Beyond Claude, Qonto's own approval logic applies to writes, and sensitive actions need strong authentication in the mobile app, which the connector cannot bypass.
04Which plans is it available on?
No official source publishes plan availability connector by connector, and none of the 819 directory sheets shows it. Anthropic's general rule is that remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, with an Owner or Primary Owner enabling them first on Team and Enterprise. Qonto's guide names a narrower list, quoted in the limits section. The directory sheet shows the live state for your account.
05Does Claude see everything in our Qonto organization?
Claude sees what your Qonto role sees, and nothing more: every call is authenticated as you. An employee sees their own requests, a manager their team's, owners and admins everything. On Qonto's side, managers and employees can only connect once an owner or admin enables access. To cut it, revoke the app from the connected apps section of your Qonto account, or remove the connector in Claude's settings; either way, access stops.
06Why can't Claude use Qonto after connecting?
Most likely because your Qonto role is not enabled yet. Qonto lets owners, admins and accountants connect by default; managers and employees can connect only once an owner or an admin enables Qonto MCP for the organization. If you connected as a reporting user, reads work but every write tool refuses with an authorization error. Also check the organization you authorized: each authorization covers one, and the server never goes beyond your role.
07Claude or an automation tool for Qonto?
They do different jobs, so it depends on the use. Claude is for questions and one-off actions you steer: which clients have not paid, draft this invoice, lock that card. It never starts by itself. If you want every new transaction copied to a spreadsheet, or receipts pushed to your accountant each week without anyone asking, that is a scheduled flow, which an automation platform runs and a conversation does not.