Settings: Integrations and automations

Recipes

Your own automations. Each has a trigger, conditions and steps, and runs in shadow before you set it live.

Read as Markdown

A recipe waits for something to happen, checks its conditions, then does its steps in order. It might wait for a call outcome, a payment, an application or a new tag. Its steps can tag the person, open an inbox task, set a CRM status, send a Discord or Slack notification, post to a webhook, or enroll a buyer as a student.

PYLO never messages a lead from a recipe. To message someone, a recipe adds them to your CRM's workflow, and the CRM sends it.

Who can open it

Owners and admins, under Settings, Integrations and automations.

Where recipes come from

Every starter template brings recipes with it, and your agent can add more. A new recipe always arrives off.

Off, shadow and live

• Off does nothing.
• Shadow logs what the recipe would have done on each matching event and changes nothing. Read those runs under Recent runs.
• Live does the steps for real. PYLO asks you to confirm before a recipe goes live.

Your agent can move a recipe from off to shadow. Only a person can set it live, here.

Tags

Tags lists every tag on a person in this workspace and how many people carry it. Tags come from recipes.