Browse the manual

Connect events to the next action

Create rules from work events or schedules, add a wait, send follow-up messages after a person approves them or trusts the rule, and check each run.

On this page

For: owners and staff who want an event or a schedule to start the next piece of work. What you need: Automations access, permission to manage your rules and access to each source and destination.

Open Work > Automations to connect an event to a task, project or reviewed action. Saving leaves the rule inactive. Activate it after checking its steps.

Every run uses its creator's current permissions. Issuing, sending and webhooks each wait for a person to approve the exact action. A follow-up message or request also waits, unless you trust the rule (see Trust a rule).

An automation connects a work event to conditions and actions, with the selected step open for editing.

Check access and hosting

Permission What it allows
Read own rules and runs Open your rules and their permitted run history
Manage own rules and endpoints Create, change, activate and stop your rules; manage your webhook endpoints

Management also needs read access. Guests cannot use Automations. An administrator does not gain access to another person's private rules or runs.

Source apps must be available. You need their ordinary action permissions and current access to each selected record. An automation grants no extra access.

Your operator must configure the hosting scheduler. It processes automation work every minute. No AI account, connected client or separate queue worker is required.

Create a follow-up rule

This example creates a follow-up task after someone completes a task whose title contains review.

  1. Choose New rule.
  2. Enter a Rule name.
  3. Choose Add trigger.
  4. Select When a task is completed, then choose Add step.
  5. Choose Add condition.
  6. Select Source title, then choose Add step.
  7. Set Comparison to Contains and Value to review.
  8. Choose Add action.
  9. Select Create a task, then choose Add step.
  10. Enter Confirm the next step under Title.
  11. For Project · Value source, choose Project of the source task.
  12. Open the trigger and set Next step to the condition.
  13. Open the condition and set If yes to Create a task.
  14. Keep If no set to End this path.
  15. Choose Save rule.
  16. Review the saved rule, then choose Activate rule and confirm.

Use List for the same fields and connections without canvas gestures. On a phone, List opens first. Flow lets you select, move and connect steps on the canvas.

Each ordinary step has one Next step. A condition has separate If yes and If no paths. An empty connection ends that path.

Rules accept 2–32 steps, including exactly 1 trigger, and up to 64 connections. Every step must connect to the trigger. Loops and merging paths are refused.

The complete encoded rule graph must fit 131,072 bytes. Rule names accept 120 characters; optional descriptions accept 2,000 characters.

Remove step also removes its connections. You cannot remove the trigger through that control. Select another trigger in its fields when needed.

Choose values from records

Use Fixed value to enter a value. Where offered, choose a source value or a Result from an earlier connected action.

Only compatible values appear. A project field can use the source task's project. A later record field can use a compatible earlier action's result.

Current access still applies when the step runs. Selecting a record now does not reserve future permission to use it.

Choose an event or schedule

Trigger When it starts work
When a task is created A permitted task is created
When a task is completed A permitted task is completed
When a deal is won A permitted deal becomes Won
When a document is issued A permitted financial document is issued
When a calendar event is created A permitted calendar event is created
When a Doc edition is approved A permitted Doc receives an approved frozen edition
When a form is submitted A permitted form receives a submission
When an invoice is paid A permitted invoice becomes fully paid. It fires once per invoice; a partial payment does not fire
When a quote is accepted A permitted quote is accepted
When a customer is added A permitted customer is created
When a project is closed A permitted project is closed
When a lead is created A permitted lead enters Sales
On a schedule The selected local date and time becomes due

The choices follow available apps and your access. Activation starts from new events; it does not run old event history.

Add a condition

A condition compares one field of the trigger's record. The comparisons follow the field type:

Field type Comparisons Example fields
Text Is, Is not, Contains Source title, Document number, Currency, Name, Lead source, Email address
Whole number Is, Is greater than, Is less than Source priority (1 Urgent, 2 High, 3 Normal, 4 Low)
Amount Is, Is greater than, Is less than Total of a paid invoice or an accepted quote
Record Is Customer, Project

Enter an amount as the record shows it, for example 1250.00. Pepper compares amounts exactly, to the cent. 1250.00 is 1250.000; it is not 1250.01. A record comparison uses the record you pick.

Only the fields of the selected trigger appear. Rules saved before this release keep their Source title and Source priority conditions.

Set a schedule

  1. Choose On a schedule as the trigger.
  2. Set Start date, Local time and Time zone.
  3. Choose Daily, Weekly or Monthly under Cadence.
  4. Set Every from 1 to 365 periods.
  5. Add a Last date when the schedule must end.
  6. Save the rule, review it and activate it.

Weekly schedules keep the start date's weekday. The last date includes an occurrence on that date.

Monthly schedules keep their original day. A schedule on 30 January uses 28 February in a non-leap year, then 30 March. A month-end start stays at month end.

A skipped daylight-saving time uses the first valid instant after the gap. A repeated time uses the earlier instant. A wholly skipped local date creates no occurrence.

Later occurrences keep the original cadence. A delayed scheduler catches up one due occurrence per rule per pass. Check the dates before activating an old start date.

Add a wait

Choose Add wait to pause the run before the next step. Set Wait for and Unit:

Unit Range When the run goes on
Days 1 to 90 At 09:00 in your business time zone, on the chosen day after the wait began
Hours 1 to 72 Exactly that many hours later

The step shows the sentence, for example Resumes at 09:00 business time on day 2. Run history shows Waiting until the date and time.

When the wait ends, Pepper reads the source record again. A condition after a wait checks the record as it is then, not as it was. If the record is gone or you can no longer read it, the run ends as Skipped and sends nothing.

Stop rule, Deactivate rule and saving a change cancel waiting runs with the rest.

Choose the action

Action What to set and check
Create a task Title, optional project, dates and priority. Check the created task in the run result
Open a project from a won deal Select a permitted won deal. Pepper uses the ordinary project-opening action
Issue a document Select the draft financial document. Review its exact number, figures and current version before approving
Send an issued document Select the issued document, email template, subject, message and permitted recipients. Review the exact send before approving
Send a signed webhook Select your endpoint and enter the exact JSON object. Review its destination, body and retry policy before approving
Send a follow-up message Choose one of the three follow-up templates. Pepper derives the recipient from the record that started the run. Review the recipient and the rendered message before approving, or trust the rule
Ask for a testimonial, feedback or answers Choose the widget. Pepper derives the customer from the record that started the run; a feedback request from a closed project names the project. Review before approving, or trust the rule

Issuing sends no email. Sending follows the normal document outbox and its delivery result. A Doc approval triggers work; it never becomes financial-document issuance by itself.

Financial calculations stay in Pepper's ordinary actions. EUR, USD and other supported currencies keep their exact figures and separate balances.

Choose document recipients

For Send an issued document, choose Billing recipient to use the current eligible primary recipient. If none is primary, Pepper uses the first offered recipient.

For a fixed document, choose Choose recipients to select permitted names and email addresses. Add copy recipients when needed.

When the document comes from a source binding, use Billing recipient. Pepper resolves that document's recipient when it prepares the action.

Check the exact addresses in the approval. A changed recipient after preparation requires a new review. The rule grants no permission to send without that confirmation.

Follow-ups

A follow-up is a message about an event between you and one person: an invoice paid, a quote accepted, a customer added, a project closed, a lead created. It needs no marketing consent. It needs an honest sender, a way to stop and respect for bounces, and Pepper gives it all three. A message sent because of who someone is, such as an inactive customer, a season or an offer, is a campaign. Campaigns and newsletters are not included yet.

Start from a sentence

Choose New rule. Pick the sentence that says what you want:

Starting point What Pepper fills in
When an invoice is paid, wait two days, send Thank you Trigger When an invoice is paid, a 2-day wait, Send a follow-up message with Thank you after payment
A week after a project closes, ask for a review Trigger When a project is closed, a 7-day wait, Ask for a testimonial, feedback or answers. When you have exactly one testimonials widget, it is preselected
When a quote is accepted, create a task to start the work Trigger When a quote is accepted, Create a task
When a customer is added, send Welcome Trigger When a customer is added, Send a follow-up message with Welcome
Two weeks after a project closes, send Check-in Trigger When a project is closed, a 14-day wait, Send a follow-up message with Check-in after a project
When a lead comes in, follow up within a day Trigger When a lead is created, a 24-hour wait, Create a task

Change any step, then save. Start empty opens an empty rule.

Who receives a follow-up message

Pepper derives the recipient; you never type an address in a rule:

Record that started the run Recipient
Invoice or quote The customer's primary billing contact with an email address, else the customer's address
Customer The same rule on that customer
Project The same rule on the project's customer
Lead The lead's address

When no address exists, the step ends as Skipped with Skipped: no one has an email address for this message, and the run goes on.

Edit the three templates

Open Settings > Email templates and choose the language. The follow-up templates are Thank you after payment, Check-in after a project and Welcome. They use the ordinary template variables, plus {first_name} (the first word of the recipient's name) and {project_title} (the closed project's title, empty for other records). Document variables are empty when the record is not an invoice or quote.

A message renders in the customer's document language, else your company language, with the sender identity of Settings > Email. It has an HTML part and a plain-text part with the same words. Pepper loads no remote image and tracks no opens or clicks.

Every message can be stopped

Every follow-up carries a visible Stop automatic messages link and the one-click unsubscribe headers that mail programs show. The recipient opens a page with one sentence and one button, or their mail program sends the one-click request. Pepper then blocks automatic messages to that address and says so beside the run. The link is signed and expires after 90 days; a changed or expired link shows a plain refusal and reveals nothing.

Blocked addresses are listed under Settings > Email > Blocked addresses. Read Blocked addresses for the two scopes and how to lift a block.

Save, activate and stop

Control Result
Save rule Save the rule inactive. Changing an existing rule cancels its unfinished runs
Activate rule Admit new events and due scheduled occurrences for the saved version
Deactivate rule Turn off the rule and cancel unfinished runs
Stop rule Turn off the rule, cancel unfinished runs and block activation
Clear stop Remove the stop. The rule remains inactive until you activate it

Review the confirmation before changing operation. Completed effects stay recorded. Stopping cannot recall a request already accepted by an outside receiver.

Trust a rule

By default every Send a follow-up message and Ask for a testimonial, feedback or answers step pauses in the approval inbox. You review the recipient and the rendered message, then approve that one message.

An owner or administrator who manages the rule can trust it instead:

  1. Open the rule and check its steps.
  2. Choose Activate rule, select Run follow-ups without asking each time (trusted), then confirm. On an active rule, choose Trust this rule instead.
  3. The rule shows Trusted, with who trusted it and when.

A trusted rule sends its follow-up messages and requests without a per-send approval. Every such step still records an approval, marked Decided by a trusted rule, so the inbox and run history show what the rule did on your authority. Issuing, sending a document and webhooks keep their per-step approval; trust never covers them.

Trust is bound to the rule version. Saving a change, Stop rule and Deactivate rule clear it. Activating again without the mark leaves the rule untrusted. Choose Revoke trust to end it; unfinished runs are cancelled. Sample rules start untrusted.

An AI client requests trust through the approval inbox; you approve that one request. It can revoke trust on its own, because revoking only narrows what runs.

If another session saves first, choose Reload latest version. Review the current rule with your retained proposal before saving again.

If a response is uncertain, retry the same proposal. Changing the input creates a new request.

Check a run and recover

  1. Open the rule.
  2. Choose All runs under Run history, or choose Run history from the rule's … menu.
  3. Open a run.
  4. Check its source, Inputs, step results and any error.
  5. Open a created record to check the work itself.
State What to do
Queued or Running Let the scheduler continue, then check again
Waiting A wait step is running. Run history shows Waiting until with the date and time
Waiting for approval Open Review exact action and check the full proposal
Finished Check each action result. For a webhook, also check its current delivery state
Failed Correct the cause. Use Retry run when offered
Needs attention Review changed access, rule input or source records before preparing work again
Cancelled or Skipped Read the retained result. These states do not confirm an action happened. A run skipped after a wait names the reason: the record is gone or no longer readable
Blocked (message delivery) The address is on the blocked list. The step shows the reason and a link to Blocked addresses, where a person who manages settings can lift the block

Retry run keeps completed steps and retries eligible ordinary work. It does not resend an uncertain sensitive action.

Each sensitive action needs a fresh exact approval when the run reaches it. By default, you review each request. You can set approval rules with limits for supported actions from that automation.

A rule can cover invoice issue, an exact document email, or an exact payment or refund record. Other sensitive actions still wait. Changing the automation invalidates its earlier consent. An expired, changed or rejected proposal cannot authorize an action.

Account deactivation, changed permissions, unavailable apps or lost record access can block a run. A changed source version also requires review.

Rule details unavailable hides the saved steps and targets while your access is insufficient. Stop rule remains available for your owned rule.

Restore the necessary access, reopen the rule and review it. Do not replace hidden steps with an empty rule. History also follows current record access.

Connect a webhook receiver

A webhook sends a JSON message to an outside service. Configure the receiver to check Pepper's signature and prevent duplicate processing before approving a send.

  1. Open a rule and choose Webhook endpoints.
  2. Choose Add endpoint.
  3. Enter an Endpoint name and the receiver's HTTPS address.
  4. Choose Save endpoint.
  5. Copy Signing secret before closing the dialog.
  6. Store the secret at your receiver.
  7. Add Send a signed webhook to the rule.
  8. Select the endpoint and enter Exact JSON body.
  9. Save and activate the rule after reviewing its steps.

The endpoint name accepts 120 characters. The browser address field accepts 2,000 characters. The body must be a JSON object of at most 262,144 bytes.

Only public HTTPS destinations on port 443 are allowed. Private, local and reserved addresses, embedded credentials and fragments are refused. Redirects are refused.

Pepper checks DNS again for each attempt. A saved endpoint can still fail when its current destination is unsuitable.

The secret appears once. If you lose it or miss the response, choose Rotate signing secret from that endpoint's … menu.

Update the receiver before approving another send. Rotation makes unexecuted preparations for the old secret stale.

See the receiver reference for exact headers and signature verification.

Read the delivery result

Delivery state Meaning
Queued or Sending No confirmed acceptance yet
Waiting for another attempt A known retryable failure has another scheduled attempt
HTTP accepted The receiver returned HTTP 2xx. This does not prove it processed the contents
Refused The destination, response or retry limit stopped delivery
Outcome unknown An attempt may have reached the receiver. Pepper does not resend it automatically

One approval allows at most 5 attempts. Known retryable failures wait 1 minute, 5 minutes, 30 minutes and 2 hours.

A timeout, interrupted worker or oversized response can leave an unknown outcome. Check the receiver before requesting another attempt; it may already have processed the message.

For an eligible rule delivery, choose Review another attempt in its run. Review the new request and its duplicate warning before approving.

Recovery keeps the same delivery ID and exact body. It allows up to 5 more attempts. Your receiver must prevent processing that ID twice.

A delivery first requested by a connected app needs recovery through that original connection. See connected-client recovery.

Hand rules to a successor

Offboarding lists Owned automation rules for an eligible successor with permission to read owned rules.

The rules move stopped and inactive. Old pending work and approvals do not transfer authority. Earlier runs keep their original actor; the successor gains no access to that history.

To continue a rule, the successor also needs management permission. They must review permitted steps and targets, clear the stop, then activate it. Webhook endpoints remain with their creator.

Review work after recovery

Full exports keep rules, run history, endpoints and encrypted delivery data. Follow the backup and recovery guide to preserve the required keys.

Before enabling the replacement's scheduler, review active rules and current delivery states. Run only one installation against the business's outside receivers.

Imported pending approvals no longer authorize their actions. Review the current records before preparing another exact request. Keep unknown delivery outcomes until you check the receiver.

Review sample rules

With fresh-install sample data enabled, these rules start inactive:

Sample Work it proposes
Weekly planning task Create a planning task on a weekly schedule
Follow up after a completed task Create a follow-up in the source task's project
Open work after a won deal Open a project from the won deal
Thank you two days after payment Wait two days after an invoice is fully paid, then send Thank you after payment to the billing contact
Ask for a review a week after a project closes Wait a week after a project closes, then ask the customer for a testimonial
Start the work when a quote is accepted Create a task when a quote is accepted

Review the dates, values and access before activating a sample. Samples send no webhook and issue no invoice. The two follow-up samples start untrusted: each message or request waits for your approval.

Need help with the product?

Contact support