.json. There is no Excel export, and no scheduled or emailed report — anything beyond
those comes out of the REST API.
Exports are not gated by your plan. What you can export depends on your role and permissions
— see Roles and permissions.
Contacts
Your contact list as
salesbot-contacts.csv.Products
Your product catalogue as
salesbot-products.csv.Export your contacts
The contacts export gives you every contact in the workspace — not just the ones who have messaged on the channel you’re currently viewing. Contacts belong to the workspace, not to a channel. The file issalesbot-contacts.csv with these columns:
The
country_code column is always empty, on every row. It exists so the export matches the
layout the contacts importer expects — the country code is already part of phone. Don’t
build anything that reads it.Export your products
The products export is the whole catalogue, every time — it has no filters and ignores whatever you’re looking at on screen. Products come out in the order they’re sorted in the catalogue. The file issalesbot-products.csv and covers name, sku, price, cost_price,
currency, tax_rate, tax_inclusive, track_stock, stock_quantity,
low_stock_threshold, category, active and description.
Services and Plans do not export. Only products do.
What doesn’t export
The dashboard numbers
The dashboard numbers
Overview has no export. The KPI cards, the Message volume chart,
the Broadcast funnel, Flow outcomes and Contact sources are on-screen only. If
you need those numbers in a spreadsheet, read the underlying records through the API and do
your own totals.
Appointments, payments and conversations
Appointments, payments and conversations
None of these have a download button in the app. Pull the records through the API instead.
Invoices are the exception: an individual invoice downloads as a PDF from Finance →
Invoices → the row’s dropdown → Download PDF. There is no bulk invoice export.
CSAT scores
CSAT scores
Survey answers are used to route the conversation — each score sends the contact down its own
branch of your flow — but they are never stored as a score you can total up or export. If you
need CSAT reporting, have the flow write the outcome somewhere you can query, such as a tag
or a custom field. See CSAT.
Anything on a schedule
Anything on a schedule
DMLY doesn’t email you a report or drop a file anywhere on a timer. Every export is something
you download yourself, when you ask for it.
Get the rest through the API
For anything without an export, the REST API is the route. It returns JSON, so it suits a spreadsheet tool that can import from a URL, a reporting tool, or an automation platform like n8n.1
Create an API key
Keys are minted per workspace and carry the workspace with them, so no workspace ID appears
in any URL. See Authentication.
2
Call the endpoint you need
Browse the API reference for contacts, appointments,
invoices, payments and the rest. Lists paginate, so page through them for a full extract.
3
Or get pushed to instead of pulling
If you want a running record rather than a snapshot, subscribe to
webhooks and have each event land in your own system as it
happens.

