Skip to content

Reference: Automation events, conditions and actions ​

This article is the full reference for the three blocks of an automation. For the step by step, see Creating an automation.


Events (When it runs) ​

The event is what calls the automation. When you pick one, its configuration fields show up right below.

Pipeline group ​

EventWhen it firesFields
Deal createdThe opportunity did not exist and was createdPipeline (specific or all) · Stage (specific or any)
Opportunity entered a stageThe opportunity already existed and entered the stagePipeline · Into stage (empty = any) · Only once per deal
Opportunity stuck in a stage for N daysThe opportunity has been sitting in the stage for N daysPipeline · Stage (empty = any) · Stuck for (days) · Only once per deal
Deal wonThe opportunity was marked/dragged as WonPipeline (specific or any) · Only once per deal
Deal lostThe opportunity was marked/dragged as LostPipeline (specific or any) · Only once per deal

About Only once per deal: with it on, a card that comes back to the same stage does not fire again; off, every pass through the stage fires.

About stuck in a stage for N days:

  • The count starts when the opportunity enters the stage (a card created in it counts from its creation);
  • The check runs every hour — it fires on the first check after the period;
  • Each card fires once per pass through the stage: if it leaves and comes back, it can fire again (unless Only once per deal is on).

Contact group ​

EventWhen it firesFields
Contact createdA new contact was created—
Tag added to contactThe chosen tag was appliedTag · Only once per deal
Tag removed from contactThe chosen tag was removedTag · Only once per deal

Conversation group ​

EventWhen it firesFields
New conversationA conversation was createdChannel (empty = all)
Conversation assignedA conversation was assigned to someoneChannel · Sector
Conversation closedA conversation was closedChannel (optional)
Conversation reopenedA closed conversation was reopenedChannel (optional)
AI handed off to a humanThe AI agent transferred the conversation to a humanChannel (optional)

Conditions (Only if) ​

With no conditions, the automation runs every time it is called. With conditions, pick the mode:

  • All conditions — AND connector: all of them must be true;
  • Any of them — OR connector: one being true is enough.

Example: tag has "active customer" + sector is "General" → in All conditions, it only runs when both are true; in Any of them, it runs when either is.

Available fields ​

GroupFields
ContactTag · Source · Type · Sector · Email · Company
DealPipeline · Stage · Deal value (greater than, equal to or less than X) · Owner · Title
ConversationChannel · Sector · Assignee · AI active · Status
TriggerPrevious stage — the stage the opportunity came from
Custom fieldsEvery contact and opportunity custom field in your account

💡 Custom fields vary from account to account — the list you see reflects the fields your operation created (Instagram data, city, category, whatever it is).


Actions (What it does) ​

Actions run in order, one after another. Full catalog:

Assignment ​

  • Set owner — sets the opportunity owner;
  • Transfer to sector — moves it to a specific sector.

Contact ​

  • Add tag — accepts several tags at once;
  • Remove tag — same, several at once;
  • Change field — changes a contact field (system or custom), setting the new value;
  • Add note — records a note on the contact;
  • Add to list — adds the contact to one of your sending lists;
  • Remove from list — removes the contact from a list.

Deal ​

  • Create deal;
  • Move to stage — moves the opportunity to the chosen stage;
  • Set opportunity field — system or custom;
  • Mark as won;
  • Mark as lost;
  • Add comment — on the opportunity;
  • Start playbook — starts a playbook on the opportunity, creating the process tasks automatically.

Conversation ​

  • Send message — you choose where the message goes and can send files;
  • Private note — adds an internal note to the conversation;
  • Turn AI on or off — activates or pauses the AI agent in that conversation;
  • Close conversation.

Tasks and team ​

  • Create task — creates a specific task;
  • Notify — sends a notification about the task.

Timing ​

  • Wait — pauses the sequence for as many minutes as you set, before running the next action.

Integrations ​

  • HTTP Request — calls an external API from the automation. It is the only action with its own editor; it is detailed in the section below.

The HTTP Request action ​

Calls an external API in the middle of the automation — to notify a system, create a record on the other side, or fetch a piece of data and use it in the following actions.

Method and URL ​

Pick the method and enter the URL. The URL accepts variables, for example /contacts/{{contato.email}}.

Body (JSON) ​

There are two modes, and choosing between them is the most important decision in this action.

GetRaze data ​

GetRaze builds the body for you. There are 124 fields in nine blocks, and four rules explain the behavior:

📖 Field by field: this section is a summary. The full reference — every field with its type and caveats, plus the entire example JSON — is in HTTP Request body.

RuleWhat it means
Fixed formatThe body is the same for every trigger. What changes is the trigger block and what comes empty — the receiver does not need per-event handling
No messagesThe conversation history is never sent. What goes is the channel, status, assignee, sector, counts, date and direction of the last message, its preview and the AI summary
Missing is nullA block with no data becomes null, it never disappears. An empty list becomes []. A contact trigger, with no opportunity, sends "opportunity": null
Unchecking removesA block unchecked on screen leaves the JSON — the key does not even show up. That is different from coming as null, and it lightens the body when the API on the other side does not need everything

The nine blocks, each with its own checkbox:

BlockJSON keyWhat it carries
TriggertriggerThe event type and its scope — pipeline, stage, tag, channel, depending on the case. It is the only block whose format changes
ContactcontactThe person: name, email, phone, job title, type, source, owner, sector, tags, custom fields, channels and the link to the contact
CompanycompanyThe registered company: domain, website, industry, size, headquarters, ICP fit and tier
DealopportunityThe deal: title, value, currency, probability, pipeline, stage, owner, products, tags, custom fields and won/lost dates
Other dealsother_opportunitiesThe contact's other deals, in any pipeline, in a reduced version. Capped at 20
Conversation (summary)conversationChannel, status, who is handling it, counts, the last message preview and the AI summary
TaskstasksCounts, not a list: how many are open, how many are overdue and which one is next
PlaybooksroadmapsThe playbook runs of the deal or the contact, newest first. Capped at 10
CalendarcalendarOnly the next confirmed meeting. Past or canceled events are not included

⚠️ The Playbooks block key is still roadmaps in the JSON. The screen was renamed, but the body kept the old name so existing integrations do not break.

Five keys are always sent, in any mode, and have no checkbox on screen: event, sent_at, test, automation and account. test comes as true when the call came from the Test request button rather than from a real run — useful for the other side to ignore tests.

Write my own ​

You build the JSON by hand, in the format the API on the other side expects, and GetRaze replaces the variables before sending.

  • Where variables work: in the body, the URL, the headers and the URL parameters — the same ones in all four places;
  • How they are replaced: always as text. A missing or null value becomes an empty string, never the word null;
  • If the JSON is not valid after the replacement, the body is sent as plain text instead of an object. Check the quotes around each variable.

The available variables (the names are fixed and stay in Portuguese):

VariableWhere it comes from
{{contato.nome}}The contact's full name
{{contato.primeiro_nome}}First name; if missing, the first word of the name
{{contato.email}}The contact's email
{{contato.telefone}}Phone, in international format with +
{{contato.empresa}}The contact's "company" field, as text
{{contato.cargo}}The contact's job title
{{oportunidade.titulo}}Title of the run's deal
{{oportunidade.valor}}Value, with no symbol or thousands separator
{{etapa.nome}}The trigger's stage
{{pipeline.nome}}The trigger's pipeline
{{usuario.nome}}Who triggered it, when there was someone
{{resposta.nome_do_campo}}A field kept from the response of an earlier HTTP Request in the same automation

⚠️ There are 11 variables, against the 124 fields of the ready-made body. If you need company, tags, products, custom fields or conversation data, you cannot build that by hand — in those cases, use GetRaze data and handle the body on the other side.

Authentication ​

Four options: None, Bearer token, Basic (user and password) and API Key header.

Headers and URL parameters ​

Add as many as you need. Both accept the same variables as the body.

Keep from the response ​

Enter the path in the response and the variable name. Each kept field becomes available to the automation's following actions, as {{resposta.rd_uuid}}.

💡 After using Test request, the platform lists the response fields — click one to keep it, instead of typing the path by hand.

Timeout ​

How many seconds to wait for the response before giving up.

If it fails ​

What to do when the call does not succeed:

OptionWhen to use it
Retry up to 5 timesOnly when the API accepts the same call twice without duplicating anything
Move on to the next actionWhen the call is a notification and the automation should continue anyway
Stop the automationWhen the following actions depend on this one's result

⚠️ Be careful with Retry: besides requiring an API that accepts the repetition, actions that use the response wait for the attempts to finish.

Secret (optional) ​

Signs the body with HMAC-SHA256 in the X-Getraze-Signature header. It lets whoever receives a generic body confirm the request really came from your account.

Test request ​

Calls the API for real, right away, and shows the response — unlike the Dry run, which simulates everything but does not send the request.


Next steps ​

  • Build your first automation with the Creating an automation guide;
  • Test everything in simulation with the Dry run before activating it;
  • Follow each run in the Runs tab.

GetRaze - AI-Powered Lead Generation