Automation · Collections and receivables

Leave ready the CFDI invoice draft a customer asks for on WhatsApp, with gigstack

An AI agent takes the customer's tax data on WhatsApp, registers them in gigstack and leaves their CFDI invoice draft ready to stamp.

Show me this with my own operation See every automation

How do I get a customer's invoice ready when they ask on WhatsApp, without typing their data into gigstack?

When a customer asks you for an invoice on WhatsApp, a Met connected to gigstack asks for their tax data, checks whether they are already registered and, if not, adds them. It takes from your catalog the service or product they bought and, if it lacks the SAT key, looks it up in the official catalog. With that it prepares the invoice as a draft and reviews it before telling your team. Nothing reaches the SAT yet: stamping starts switched off, so your team reviews the draft and stamps it in gigstack, or the admin turns stamping on if they prefer the Met to do it.

Where it applies: México. Written for businesses in Mexico that issue CFDI with gigstack; the keys come from the SAT catalogs.

What starts it

When the customer writes

It starts when a customer writes on WhatsApp that they need an invoice for a purchase. There is no trigger to configure: the Met assigned to the line runs the procedure inside that conversation.

Nothing to set up. The Met assigned to that channel picks up the conversation and runs the procedure inside it.

Who runs it

Invoicing Met that prepares drafts in gigstack

Finance and operations team

This is not a named, seeded Met. It is the Met that already answers the business's WhatsApp, with gigstack connected. Its work ends when the draft is ready to stamp, or when it is missing a tax detail the customer did not provide.

Run by the quotes and receivables Met

Channels: WhatsApp

What you need connected

gigstack Collect and manage

6 steps · 6 tools

The procedure, step by step

Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.

1
Check whether the customer is registered

The Met asks the customer for their RFC and business name, and checks your gigstack customers to see whether they already exist. That way it does not register them twice or invoice with old data without saying so.
- list_clients gigstack
2
Register them if they are new

If they do not show up, the Met registers the customer with the tax data the person gave in the conversation. If something is missing, such as the tax regime or postal code, it asks instead of making it up.
- create_client gigstack
3
Take the service from the catalog

The Met finds in your gigstack catalog the product or service the customer bought, with the price you loaded, so the invoice matches what you sell and not an improvised description.
- list_services gigstack
4
Look up the SAT key if missing

If the product has no product or unit key, the Met searches the SAT catalogs by description and suggests to your team the one that applies.
- search_sat_catalog gigstack
5
Prepare the draft

The Met prepares the invoice as a draft with the customer and the service. A draft does not exist for the SAT, so it can be corrected as many times as needed.
- create_invoice_draft gigstack
6
Review it and notify

The Met opens the draft to check it has the right customer, item and amount, tells the customer their invoice is in progress and lets your team know there is a draft to stamp.
- get_invoice_draft gigstack

Before you start

What you need ready

The Met solves none of these for you. If one is missing, the automation stops there.

gigstack with your service catalog

Your team loads in gigstack the products or services it invoices. Whatever is not in the catalog, the Met does not add in this procedure.
gigstack connected in Met

In Met, open Connections → gigstack → Connect and enter your Team ID and API key on the authorization screen. The six actions in this procedure start switched on.
A WhatsApp line with the Met assigned

The business connects its WhatsApp Business API line and assigns the Met that answers customers. Tax data is requested inside that conversation.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

It does not stamp the invoice: stamping the draft starts switched off. Your team stamps it in gigstack, or the admin turns stamping on if they want the Met to do it.
It does not send the CFDI to the customer: until it is stamped there is no invoice to send.
It does not validate tax data against the SAT: if the customer gives a wrong RFC or regime, the error shows up when stamping.
It does not ask for confirmation in the chat before registering the customer or creating the draft: if the actions are on, it does it. A draft has no tax effect.