The record
One occurrence of the object: a given customer, a given order. This is what your users create and edit every day.
Three notions are enough to build an application on Slamflow: objects that describe your data, flows that make it live, and formulas that compute whatever needs computing. This page covers all three, in that order.
An object is a data type you define: a customer, an order, a ticket. It acts as table, form and screen at once — you describe its fields, the rest follows.
One occurrence of the object: a given customer, a given order. This is what your users create and edit every day.
A piece of information carried by the object. Its type decides input, display and checks — a date is not a piece of text.
A field pointing to another object: an order belongs to a customer. Both sides are kept in step.
The type does more than store: it decides what users can enter, what is displayed and what gets checked.
Worth knowing. A Formula field computes itself and is never typed in. An AutoNumber field assigns a number on creation, following the pattern you give it. Those two remove most manual entry.
A flow is a sequence of tasks run in order. It sends an email, creates a record, calls an external service or shows a screen — without a line of code.
manual | A button, on a record page or in a list. |
object_after_upsert | After a record is created or changed. |
object_before_upsert | Before the record is saved — where you complete or reject it. |
scheduled | At a fixed time, on a schedule. |
webhook | An incoming call from another piece of software. |
received_mail | An email arriving in a watched mailbox. |
Each task does one thing only. Here are the most common ones; the platform ships about thirty.
Worth knowing. A task publishes its result under its own name: a get task called theCustomer is then read as theCustomer.company_name in later tasks. That is what lets you chain tasks without copying anything.
Each example gives the trigger, the sequence of tasks and the exact formulas. They can be copied as they are, replacing the field names with your own.
As soon as a request is saved, the customer receives a personal confirmation carrying its reference.
getLoad the customer the request belongs to.id == context.new.client[0]emailSend them the confirmation.leClient.emailA request above ten thousand euros goes to approval: the manager is notified, the others trigger nothing.
decisionOnly carry on when the amount is above the threshold.context.new.montant > 10000getLoad the manager named on the request.id == context.new.responsable[0]emailSend them the alert.leResponsable.emailEvery morning, sent quotes whose validity has passed are chased, one by one.
getFind quotes that were sent and have expired.statut == 'Envoyé' && date_validite < $System.currentDateloopWalk through the resulting list.lesDevis ?? []emailChase the contact on the current quote.leDevis.contact_emailFrom a button on the record, the summary is built as a PDF then sent to the customer with the document attached.
getReload the full order.id == context.commande.idgenerate_pdfBuild the PDF from the template.emailSend it to the customer, as an attachment.laCommande.client_emailThe email content is HTML in which you place formulas between double braces. Each one is evaluated when the email is sent.
<p>Bonjour {{ leClient.prenom }},</p>
<p>Nous avons bien reçu votre demande
{{ context.new.reference }} du
{{ context.new.date_creation }}.</p>
<p>Montant estimé : {{ context.new.montant }} €</p>Everything available in a formula is available here: the record's fields, the result of earlier tasks, the system variables.
A formula is an expression returning a value: a computation, a condition, a composed piece of text. It is the only place in the platform where you write something resembling code — and it stays one line, not a program.
The usual operators work: the four operations, comparisons, and logical and/or. A field is referred to by its technical name. ?? provides a fallback when the first value is empty.
prix_ht * 1.2 quantite > 0 && statut == 'Validé' prenom + ' ' + nom date_fin ?? $System.currentDate
Eight functions are available, with no prefix and in upper case.
| Function | What it does |
|---|---|
NOW() | The current instant, for timestamping. |
ISBLANK(texte) | True when the text is empty or missing. |
ADD(a, b) | Adds two integers. |
MROUND(valeur, multiple) | Rounds to the nearest multiple — to the quarter hour, to the ten. |
ROUNDUP(valeur, multiple) | Rounds to the multiple above, never below. |
ROUND_HALFUP(valeur, décimales) | Rounds to a number of decimals, half upwards. |
GETOBJECT('type', identifiant) | Loads a record by its identifier and returns its fields. |
DEBUG(valeur) | Writes a value to the logs, while you work out a computation. |
This list will grow: further functions — text, dates, totals across records — are planned, and we add more as the need arises. In the meantime, concatenate with + and have a flow write a running total.
Besides the record's own fields, three variables are always there:
Inside a flow, the input data is read under context, followed by the name you gave the variable. In a flow triggered by a record, context.new is the record that has just been written.
context.demande.montant
context.new.email
GETOBJECT('client', context.demande.client[0]).raison_socialeEven when it points to a single record. Write context.request.customer[0], never context.request.customer on its own.
Use the typographic apostrophe ’ or escape it with \'. Two straight apostrophes in a row make the expression ambiguous and it fails.
In a manual flow, the input record is only reachable under context. Dropping the prefix returns an empty value, with no error message.
Concatenating an empty field yields an empty result. Guard with (my_field ?? ') as soon as a field may be left blank.
Slamflow exposes an MCP server: an assistant like Claude can read and configure your organization — create objects, write flows, search records. Two paths lead there. The simplest one uses your account, with no secret to handle; the other uses a key, for the tools that cannot open a browser yet.
The tool sends you to a Slamflow sign-in page, you grant access, and it receives a token that renews itself. Nothing to copy or keep, and access is revoked application by application from your profile. The server address to paste is your instance's, followed by /mcp; your profile shows it, with a button to copy it.
Claude (desktop app or claude.ai)
Settings → Connectors → Add custom connector
Any name, the server address, then Connect: you sign in with your Slamflow account and grant access. All that is left is enabling the connector in the conversation. Requires a Claude Pro, Max, Team or Enterprise subscription.
ChatGPT
Settings → Connectors (developer mode)
Create a connector with the same address and choose OAuth authentication. Developer mode requires a paid plan, and depending on the plan the connector may stay read-only.
Le Chat (Mistral AI)
Connectors → Add custom MCP connector
Same address, OAuth authentication, then sign in with your Slamflow account. Adding a connector belongs to the account administrator; on an individual plan, that is you.
Claude Code, Cursor and VS Code connect with a key — Claude Code can also sign in through a browser, and your profile offers that first. The key belongs to one user and covers all of their applications at once.
Open your profile in the application, “Connect an AI application” block. An administrator can also do it from a user's page in the administration.
Click Generate a key.
Copy the key shown. It starts with sk- and is displayed only once.
Pick your tool: the screen then shows the exact configuration and the file to paste it into. Restart the tool.
The key is shown only once. No screen can show it again. If it is lost, regenerate it — the previous one is invalidated immediately, and every application using it is disconnected.
You have nothing to write or adapt: the screen that generates the key asks which tool you use, and shows the matching configuration — your instance URL included — with a button to copy it. All that is left is pasting it into the file it names.
{
"mcpServers": {
"slamflow-mon-organisation": {
"type": "http",
"url": "https://<votre-instance>/mcp",
"headers": { "x-api-key": "sk-…" }
}
}
}Pick yours on the generation screen: the configuration then takes the shape it expects, and the file to paste it into is named right above.
Claude Code
.mcp.json
It can also sign in through a browser: two commands, and no key at all. The screen gives you both forms.
Cursor
~/.cursor/mcp.json
VS Code (Copilot)
.vscode/mcp.json
The root of the file is called servers, not mcpServers: the screen does it for you.
Once the client is connected, describe what you want in plain words. There is nothing else to learn:
In my Slamflow organization, build a field-service app: customers, sites, jobs with a date, a technician, a status and time spent; a list of jobs to schedule and a dashboard per technician.
The assistant creates the object types, the fields, the lists and the screens, then hands back. You open your application and fix whatever does not suit you, by asking.
Get in touch, or start your free trial today.
Slamflow© 2026 · About us · slamflow.com