What a rule can do

Åtgärder (i ordning) — a rule can do several things, and they run in the order you list them. Each one has a Åtgärdstyp.

The common ones are creating a task, sending an email, notifying a user, updating a field on the record that triggered the rule, and Skicka webhook — POST JSON till en extern URL (Slack, Zapier osv.). That last one is how you reach a system we do not integrate with; the Webhooks page in the sidebar is the Tripletex delivery log, not this action. See Webhooks.

Values can come from the trigger. Free-text fields in an action accept variables from the record that fired it, written in double braces — Värde eller {{variable}}. So a task created when a deal reaches a stage can be titled with that deal's own name rather than something generic, which is the difference between a useful task list and a wall of identical rows.

Link what you create. When a rule makes a task, connect it to the record that triggered it. Valfritt: koppla uppgiften till en affärsmöjlighet, kund eller kontakt; lägg till taggar; ändra status; tilldela medägare; eller sätt andra aktivitetskolumner. An automated task floating free of any customer is one nobody can act on without going looking, and most people will not.

Koppla uppgiften till CRM-poster, lägg till taggar eller sätt andra tillåtna fält. Fritext stöder {{variables}} från utlösaren. Tomma fält sätts inte på den nya uppgiften.

Write real email content. An automated email goes to a customer without anyone reading it first, so a template left at its default wording gets sent exactly as-is. Write the subject and body properly, and use variables so it reads as though a person wrote it.

Order matters when actions depend on each other. If one action creates something a later action refers to, it has to come first in the list.