Custom automations

Assembling your own rules from the actions included in your base and add-ons — with tests, versions and a stop button.

7 days, 20 answered calls, no card

The task it takes over

The journeys included in your base already cover the everyday situations of your industry. Then there is your own way: that client wants notice the evening before rather than the morning of, that request has to pass an approval, that kind of file has to reach one particular person after a delay.

This add-on lets you assemble those rules yourself. A trigger, conditions, delays, approvals, a version, a test, and a stop. You compose from the actions included in your base and add-ons; a rule that needs another action shows you the add-on that carries it.

It also links your own applications: you authorise one, give it limited access, and it receives the events from your files, each delivery confirmed. You assemble the rules yourself from the actions you already have, with no code to write.

Step by step

  1. Compose

    Blocks included in your base and add-ons

    The editor shows the actions included in your base and add-ons. When a rule needs another action, the editor names the add-on that carries it.

  2. Test

    A trial ahead of publishing

    A rule is tested before publication, and each publication creates a version. You know which one runs, since when, and what it did.

  3. Run

    One run, one log

    Every run is logged with the version that ran, and it is counted once. Its steps, waits and retries stay inside that same run.

  4. Stop

    The stop button belongs to the tool

    A rule can be paused. Stopped mid-run, it leaves no half job behind, and a retry does not repeat the same action twice.

What the add-on adds

Standard connections and journeys of an add-on stay included in that add-on. This one adds composing your rules, your authorised applications and event delivery.

A rule is assembled from Zenvox actions, with no code to run; your applications reach only the data you open to them. Where a journey uses a payment, an appointment, a document or a channel, the action comes from your base or from the add-on that carries it.

What this changes, in practice

Law & accounting firms

A missing document chased on a precise rhythm, a handover to the right person after a business-hours delay: those are firm rules, rather than universal settings.

Real estate

A maintenance report above a spending cap has to reach an approval. A rule makes that limit automatic rather than dependent on somebody staying alert.

Clinics & home care

Preparation to send according to appointment type, a document requested only in certain cases: one rule per situation, rather than one message for everybody.

Contractors & trades

Work declined by one crew moving to another, a warranty reminder on a calculated date: the logic of a business, written once.

What it receives

  • Events on your files: a request, an appointment, a payment, a message
  • The actions included in your base and add-ons
  • Conditions, delays and approval steps
  • Client applications you authorise, with limited access

What it produces

  • Published rules, versioned and tested
  • Traced runs, with readable diagnostics where something blocks
  • Events sent to your applications, each delivery confirmed
  • A retry, with no duplicate, when a delivery did not go through

You publish, you pause, you revoke an application. A rule uses only the actions included in your base and add-ons.

What is counted, and how

The add-on carries its own monthly volume, which you follow in your app: runs, delivered events and active automations.

  • A run counts once, however many steps it has
  • A rule that checks a condition and does nothing still counts once; a run that fails before it starts does not count
  • Deliveries count per event received, rather than per attempt
  • A number of active personal automations, independent of how many runs happen

A run is counted once, and the calls, messages and documents it produces are counted only once.

With your applications

Standard connections of your add-ons stay included in those add-ons, and every connection is authorised from your account.

  • HubSpotA rule writes into the HubSpot customer record with the authorisation you installed on your account.HubSpot
  • Your own applicationsAn application you authorise receives limited access and the events from your files, at the receiving address you give.My software is not in the list

Questions about this add-on

Which actions can I use in a rule?

Those included in your base and add-ons: the editor shows them, and when a rule needs another one, it names the add-on that carries it.

Do I need to write code?

No. You assemble your rules from Zenvox actions, with no code to write, and your own applications receive the events you open to them.

A rule goes wrong — how do I stop it?

The stop button belongs to the tool: a rule can be paused. Stopped mid-run, it leaves no half job behind, and a retry does not repeat the same action twice.

Does connecting another add-on require this one?

No. Standard connections and journeys of an add-on stay included in that add-on. This one adds composing your rules, your authorised applications and event delivery.

How is a run counted?

A run counts once, however many steps, waits or retries it has. A rule that checks a condition and does nothing still counts once, a run that fails before it starts does not count, and deliveries count per event received rather than per attempt.

Where to next

What exists already with no rule written, or the data feeding your answers.

Custom automations

Assembling your own rules from the actions included in your base and add-ons — with tests, versions and a stop button.

Start your free trial7 days, 20 answered calls, no card