What a rule can do

Handlinger (i rekkefølge): a rule can do several things, and they run in the order you list them. Each one has a Handlingstype.

The common ones are creating a task, sending an email, notifying a user, updating a field on the record that triggered the rule, and Send webhook: POST JSON til en ekstern 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: Verdi 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. Valgfritt: koble oppgaven til en mulighet, kunde eller kontakt; legg til tagger; endre status; tildel medeier; eller sett andre aktivitetskolonner. An automated task floating free of any customer is one nobody can act on without going looking, and most people will not.

Koble oppgaven til CRM-poster, legg til tagger eller sett andre tillatte felt. Fritekst støtter {{variables}} fra utløseren. Tomme felt settes ikke på den nye oppgaven.

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.

Choose who the email is from. Send fra on an email step has three choices. Arbeidsområdets adresse sends from your workspace's address: set Avsendernavn to the name recipients should see, and once your own sending domain is verified Postkassenavn picks the address on it, such as kurs@ your domain. Until the domain is verified the email goes from noreply@dealjourneycrm.com with your chosen name. Postkassen til eieren av posten sends from the connected Outlook or Gmail account of whoever owns the record, so replies land in their inbox. En bestemt postkasse lets you pick one connected mailbox, including a shared one; only mailboxes you are allowed to send as are listed, and recipients see the name set on that mailbox in Outlook or Gmail. You cannot type any other address: mail sent as an address we cannot prove is yours ends up in spam or is refused. If the chosen mailbox is disconnected, or the owner has none, the email still goes out from the workspace address and the run history says why.

Send to several people at once. Type more than one address in the recipient field, separated by a comma or a semicolon. Each person gets their own copy, so nobody sees who else received it, and anyone who has unsubscribed is skipped while the others still get theirs. Variables such as the contact's email work in the list too. Leave the field empty to send to the contact, lead or customer on the record.

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.

A step can wait before it runs. Kjøringsforsinkelse on a step holds that one step back. Pick 1 time, 1 dag or another ready-made choice, or pick Egendefinert and set your own number in minutter, timer, dager or uker. The rest of the rule carries on immediately. Only the delayed step waits, and it runs on its own once the wait is up, which is how a follow-up email three days after a deal is won can live in the same rule as everything that happens the moment it is won.

A step can also wait for a date rather than a length of time. Some things are not "two days later", they are "the 20th" or "ten days after the quarter closes", and a routine built out of relative waits drifts away from the calendar month by month. Two extra choices in Kjøringsforsinkelse handle these. På en bestemt dag i måneden pins the step to a day number and how often that day comes round: every month, or every second, third, sixth or twelfth. A day no month has, such as the 31st in February, moves back to the last day of that month. Etter at en periode er slutt counts a number of days from the end of a måned, kvartal, halvår or år, which is how a VAT or annual-accounts mail is actually described. Both take a time of day, read in your own time zone, and both can Flytt til neste virkedag so nothing lands on a Saturday or a public holiday.

The rest of the rule still runs immediately, which is the point: the task is created the moment the rule fires and only the email waits for its date. If a rule fires after the chosen moment has already passed this month, the step goes to the next one round rather than sending straight away.

An activity a rule creates can arrive with its checklist on it. Pick a checklist on the Create activity step and its steps are added to the new activity the moment it is made, ready to tick off. Without this, whoever picks the activity up has to know which checklist belongs to it and apply it by hand, which is the part of the routine the rule was meant to remove. Checklists are managed under Templates; a rule can only use one that already exists there.

Dates can be a rule, not a number. A date field in an action is built from three parts: how far from the moment the rule fires, in what unit, and which day to land on. The last part is where the useful ones live. As well as the first or last day of the week, month, quarter or year, you can pin a set day of the month, so a monthly routine lands on the 10th every time instead of being spelled as "the 1st, then nine days later". A day no month has, such as the 31st in February, moves back to the last day of that month rather than spilling into the next one. The line under the field shows the date the rule would produce if it fired today, so you can check it before you save.

A later action can use what an earlier one wrote. Open Variabler: on any free-text field and the values earlier steps in the same rule will have filled in are listed alongside the trigger's own. So a rule that creates a task with a deadline can then send an email that names that exact deadline, instead of repeating the date in two places and letting them drift apart. Values from the step immediately before are offered first; a step further back is offered too, and stays pinned to that step even if there is a Yes/No branch in between.

Pause the whole journey. Add Vent på when later steps must wait too. It can wait for conditions on the current record, an event on a related record, or a period of time. For an event, choose the record type and event, then use Knytt til samme to match the same customer, opportunity, contact or activity. The event must happen after the wait starts. For example, send an onboarding form, wait for its submission on the same customer, then create the onboarding tasks.

Set Avslutt ventingen etter (dager) and Hvis ingenting skjer. Continuing after an expired wait makes Den forrige ventetiden utløp available to a following condition: use that branch for a reminder and the other branch for normal onboarding. Stopping ends that customer's journey. Waiting conditions are checked by the scheduled processor, normally every five minutes; an event marks the matching journey ready for its next check. This is separate from an individual action's delay described above.

Ask a person before continuing. Add Be om godkjenning, choose the record owner or a specific teammate, and fill in Innhold som skal godkjennes. The reviewer is notified and can open Forløp og godkjenninger from the workflow run history to Godkjenn or Avslå. Only the assigned reviewer can decide. A refusal or an expired approval stops the journey. Later steps remain paused until approval.

For an AI-written email, first use the AI action with Generer tekst til senere steg (ingen sideeffekt). Put its generated text in the approval step, then use the approved-content variable as the body of a later email action. That variable contains the exact text the reviewer saw. Choosing the AI action's email-sending output would send immediately, before the later approval step.

Distribute ownership. Fordel ansvar assigns a lead, customer, contact, opportunity or activity to one of the selected active teammates. Choose Bytt på mellom de valgte personene to take turns, or Personen med færrest åpne oppgaver to use current open task counts. The latter measures task workload; it does not check calendar availability. Later steps can notify or create work for the newly assigned owner.

Existing journeys keep the version they started with. Editing the workflow changes future entries. Turning it off cancels waiting journeys when the processor next checks them. You can also use Avbryt forløp for one waiting journey. If processing is interrupted during an action, the run stops for review rather than automatically repeating a message that may already have been sent.