Appearance

Automations

The right signal. The right next step.

Respond to what happens on your website. Connect events, conditions and actions in a clear process that helps customers and keeps your team organised.

Explore the product in a demo tailored to your business.

Meetlead visual automation editor with a trigger, conditions and a sequence of actions.
From website behaviour to a meaningful action.
Capabilities

Less repetition. More relevant responses.

Someone spends time on pricing, returns to your website or asks for a call. Decide when to help and what should happen next, while the moment still matters.

Events and conditions

Start with behavior that matters.

A page visit, elapsed time, click or chat opening can start a scenario. Conditions define which situations your response fits.

Website and contact signals
Consider a return visit, scroll depth, a message or a tag change.
Conditions evaluated together
All configured conditions must match, such as page URL, language and device.
Rule editor with trigger, conditions and actions. Example data.
Rule editor with trigger, conditions and actions. Example data.
Proactive help

A good message fits a specific moment.

A visitor is comparing an offer for a while? Offer a short prompt to help them choose. Copy, conditions and chat behavior form one scenario you can refine before publishing.

A contextual message
Refer to the offer being viewed and suggest one clear next step.
The right contact behavior
Choose a proactive message, chat opening or popup to match the rule’s goal.
Message settings within an automation sequence.
Message settings within an automation sequence.
Action sequences

Arrange the steps your team would take manually.

After a message, add a tag, wait or pass information onward. Actions follow the defined order, giving every rule a clear sequence.

Organized contacts
Add and remove tags to keep interest context available to later rules.
An intentional delay
Space actions out when an immediate response is unnecessary.
The example sequence combines a message with a tag action.
The example sequence combines a message with a tag action.
The team’s next step

An on-page event can prompt work beyond it.

Not every scenario ends with a popup. Notify the right person about a relevant event or connect the flow to your own system through a webhook.

Email a team member
Notifications go to an active workspace member. This is not a customer email campaign.
Webhooks according to plan
Send an event to a public endpoint when your plan includes webhooks and the integration is ready.
The conversation stays in the shared inbox when the next step needs the team.
The conversation stays in the shared inbox when the next step needs the team.
Publishing and review

Launch the scenario. Review what follows.

Save a draft, publish and review execution history. Compare the rule’s results with funnels and goals to assess whether visitors take the next step.

Execution outcome
History distinguishes successful and failed actions. A rule running does not mean a customer goal was achieved.
The option to pause
Pause a rule while changing an offer or reviewing results. Previous actions remain part of history.
A funnel helps assess the journey after introducing an automation.
A funnel helps assess the journey after introducing an automation.

For your team

See how the product fits everyday work.

Help choosing a plan

Offer a conversation after a defined time on the pricing page. A URL condition keeps the scenario focused on the relevant page.

Returning visitors

Combine a return visit with an existing tag and show a message about that interest. Offer one clear next step.

A notification for the team

After a relevant event, notify an active workspace member or send data to your system through a webhook supported by your plan.

Automations

Capabilities

Events that matter

Trigger rules from a page visit, click, time on site, scrolling, a message, a tag change or a callback request.

Conditions that add context

Use the page, referral source, UTM, language, device, time of day and visit history. A rule runs when all its conditions are met.

Actions in a clear order

Show a message or popup, open chat, add a tag, wait or call a webhook. Email notifications can reach a member of your team.

Visibility into every run

Start from a template, save a draft, publish or pause a rule. Run history and results show what worked and where an error occurred.

A message that fits the visit

Combine time on a pricing page with its URL and the visitor’s language. Offer help at a specific point in the journey instead of using the same message for every visit.

Start with a template

Choose an engagement, support, return-visit or internal-work template. Adjust its conditions and copy before publishing rather than after the first delivery.

How it works

From event to action. Step by step.

  1. Choose the moment

    Start with an event, such as an extended visit to your pricing page.

  2. Add context

    Limit the rule to the right page, visitors or working hours.

  3. Build the sequence

    Choose actions, their order and any delay. Check message copy and notification recipients before the rule goes live.

  4. Launch and observe

    Arrange your actions, publish the rule and review its run history.

Availability

Enable Automations as an App for your website. Active rule limits and webhook access depend on your plan. Compare the current options and choose what fits your workflow.

See pricing
FAQ

Good to know

Can I start with a ready-made scenario?

Yes. Templates cover engagement, lead capture, support, returning customers and internal work. Adapt their conditions and actions to your website.

Can automations send customer email campaigns?

The email action notifies an active member of your workspace. It is not a tool for sending marketing campaigns to visitors.

How does a rule run?

An event starts the process, all configured conditions must be met, and actions execute in sequence. You can pause a rule and review its results.

Can a rule consider language and campaign?

Yes. Conditions include language, device, page URL, referrer and UTM parameters. The relevant data must be available in that visit; missing campaign identification is not proof of non-campaign traffic.

Can I stop a published scenario?

Yes. Pause the rule and review its execution history. Pausing does not undo messages or other actions that have already happened.

Can a webhook connect my system?

Yes, if webhooks are included in your plan. Prepare a public HTTP(S) endpoint and verify event handling. Your system’s integration and downstream logic require their own setup.

Turn the right moment into action.

Tell us about your team. We will show you the product and help you choose capabilities for the way you work.

Explore the product in a demo tailored to your business.