No-code Automations

What are no-code automations? 🪄

In Jestor you can make a no-code automation and integration with just a few clicks, it's really fast and there's no technical knowledge required.

When → Do

Every automation follows the same structure:

When [condition/trigger] → Do [action]

Example: When a purchase is approved, send a Slack message to the person who created the request.

Conditions (triggers)

Conditions define when an automation starts. Once the conditions are true, the automation runs.

Examples:

• When status is [value]
• When a record matches specified conditions
• When a record is created

Actions

Actions define what Jestor does once the conditions are met.

Examples:

• Create a new record
• Update record to [value]
• Delete record
• Send Slack message

Practical example

A common automation scenario:

• Leads are created on a workflow with a name and intended plan
• The Plans table contains the plan name and billing amount
• When a lead reaches the "Won" stage, the automation:
  • Creates a new record in the Clients table
  • Populates the client's name from the lead
  • Links to the lead record and the negotiated plan
  • Sets the client status to Active
  • Pulls the plan's billing amount into the client record

---

Concatenating text

In action fields, you can combine record values with static text to create dynamic messages.

Example setup:

Adding a lead named Andrew would generate a record using the concatenated output. This is especially useful for Slack notifications and email reports.

---

Field value formats

Some field types require specific value formats in automations:

---

Saving changes

After editing an existing automation, changes may take up to 3 minutes to propagate. If the automation still runs the previous logic after saving, wait a few minutes before testing again.

---

Automations are always improving

New triggers and actions are added regularly. Check back periodically — something new may be exactly what your process needs.