> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.platform.ly/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Automation Builder Explained

Here are a few concepts that can help users better understand how our automation builder works:

**TRIGGER**

A trigger is a procedure that initiates an action.

Examples of trigger:

* When a contact is added to a segment
* When a contact opened an email
* When an event has been fired
* When a purchase has been made

![](https://storage.crisp.chat/users/helpdesk/website/38fcf8f7d7ddec00/trigger_1bxfc70.png)

Once you have set up a trigger, you must choose an action, fork or integration...

**ACTION**

An action is executed when a trigger is fired.

Examples of actions:

* Send an email to a contact
* Add a tag to a contact
* Remove a contact from a segment
* Adjust the score of a contact

![](https://storage.crisp.chat/users/helpdesk/website/38fcf8f7d7ddec00/send-email_1jh740r.png)

For example:

Trigger: When a contact is added to a segment
Action: Send an email to the contact

Trigger: When a purchase has been made
Action: Adjust the score of the contact

**FORK**

A fork creates a condition:

* IF the condition is met, then...
* IF the condition is not met, then...

Examples of conditions:

* If a contact opened an email
* If a contact contains a tag
* If an event has been fired
* If a purchase has been made


![](https://storage.crisp.chat/users/helpdesk/website/38fcf8f7d7ddec00/purchase-made_1ekniz4.png)

For example:

Trigger: When a contact is added to a segment
Condition: If a purchase has been made

If YES:
Action: Send an email to a contact (Email A)

If NO:
Action: Send an email to a contact (Email B)

**STOPS**

Stops are temporary or permanent time actions.

Examples of stops:

* Stop an automation
* Period delay
* Date delay
* Day of the week is

![](https://storage.crisp.chat/users/helpdesk/website/38fcf8f7d7ddec00/period-delay_ds9pq2.png)

For example:

Trigger: When a contact is added to a segment
Condition: If a purchase has been made

If YES:
Action: Send an email to a contact (Email A)

If NO:
Stop: Period delay (e.g. 7 days)
Action: Send an email to a contact (Email B)

**INTEGRATIONS**

An integration is an action powered by a 3rd party service.

Examples of integrations:

* Ping a URL
* Send a text message
* Notify with text message
* Deadline Funnel

![](https://storage.crisp.chat/users/helpdesk/website/38fcf8f7d7ddec00/notify-sms_1i3erxi.png)

For example:

Trigger: When a purchase has been made
Action: Notify with text message

**AUTOMATION SETTINGS**

**RE-ENTER AUTOMATION**

This option, which can be found in automation settings, allows contacts to re-enter the automation. This setting is turned off by default, which means that contacts can enter the automation only once.

**EXISTING CONTACTS**

This option, which can be found in automation settings, allows existing contacts to enter the automation. This setting is only available when you activate the automation for the first time, after creating it.

![](https://storage.crisp.chat/users/helpdesk/website/38fcf8f7d7ddec00/automation-settings_gttd5l.png)

**GLOBAL CONDITIONS**

A global condition is a condition that is checked before every next step. Global conditions can be created in automation settings.

Examples of global conditions:

* If a contact opened an email
* If a contact is subscribed to a segment
* If an event has been fired
* If a purchase has been made

![](https://storage.crisp.chat/users/helpdesk/website/38fcf8f7d7ddec00/global-conditions_82hz1k.png)

For example, imagine your automation is made of a series of 10 emails... You could create a global condition to check if contacts are subscribed to a specific segment, e.g. "Subscribers".

If NO (the contact is still not subscribed to the "Subscribers" segment):
The automation continues. The contact will receive the next email.

If YES (the contact is subscribed to the "Subscribers" segment)
The automation stops. The contact will not receive the next email.

That way, you don't need to create a fork at every step.