Skip to content
Trelyn from Nexstap
Log inStart free

Automations

Reliable follow-through on every handover.

80 Standard automations cover what every agency repeats: a won deal becomes an engagement, quiet deals and approaching deadlines are flagged, the next period of a retainer is created. Each is a fixed rule you switch on, and every run is logged.

Start freeSee all of the product

Deterministic by design

Automations you can predict.

An automation that sometimes does something else is worse than none. Trelyn's are plain rules: you can read what each one does before you switch it on, and see afterwards what it did.

  • Readable

    Each automation states when it runs and what it then does, in one line.

  • Adjustable

    Set the timing: days before a deadline, days without activity, who is told.

  • Logged

    Every run, with the record it acted on and whether it succeeded, failed or was skipped.

  • Recovering

    Temporary failures are retried; a failed run can be retried by hand.

Examples

Handovers that happen by themselves.

Every step below is an automation in the Standard catalog, named as it is in the product.

  • A proposal is accepted

    The client accepts in the portal. The deal is won, the engagement exists, and the people who need to act have a task.

    1. Proposal acceptedIn the client portal
    2. Win dealAccepted proposal → Win deal
    3. Create engagementWon deal → Create engagement
    4. Company ownerDeal owner becomes account owner
    5. Handoff, kickoff, billingThree tasks for the team

  • The work starts

    When the start date is reached the engagement is activated, and its account manager gets the onboarding task.

    1. Start date reachedActivate engagement
    2. Engagement startedOnboarding task
    3. New projectEngagement owner assigned

  • A deadline is approaching

    Seven days before a project's end date, or whatever you set, its owner is reminded. Overdue projects and tasks escalate.

    1. Project deadline is approachingRemind the project owner
    2. Project is overdueWarn the owner
    3. Task is very overdueEscalate to admins

  • A retainer rolls over

    As a cycle period ends, the next period is created on the engagement's cadence, optionally with the recurring deliverables planned again.

    1. Period endingCreate next period
    2. Finished period still openRemind to close it
    3. Engagement endingRenewal task

Overview, Library, Activity

Switch on, tune, and watch it work.

01Library

80 automations in 23 areas.

Browse the catalog by area, deals, engagements, projects, tasks, reviews, finance, data quality and more, read what each one does, set its timing and switch it on.
  • On or off per automation
  • Scheduled checks run on their own
  • Reminders are not sent twice

02Activity

Every run, and why.

The Activity log lists each run with the automation, the record and the result, succeeded, failed, skipped or still running, over the period you pick. The Overview shows what needs setup, failed runs and the most active automations.
  • Overview of runs, failures and what needs setup
  • Skipped runs say why they were skipped
  • Retry a failed run

Custom workflows

Your own, where the catalog stops.

Build simple workflows of your own: start one by hand or when a form is submitted, check a value, and add a note to the CRM. Save as a draft, publish when it is right.

  • Triggers: run by hand, or on a form submission
  • Draft and publish, with runs in the same Activity log
  • Custom workflows: Every plan
What automations will not do

No automation in Trelyn is driven by AI, and none acts on a guess. AI in Trelyn suggests and drafts; changing records stays with your rules and your people. That is the point: you know what happened to a client record, and why.

Questions

About automations.

Are these AI automations?
No. Standard automations are fixed rules: a clear trigger, a condition and an action, with settings such as how many days before a deadline. They do the same thing every time, and every run is logged with its result.
Which automations are on by default?
Most reminders and data-quality checks are on from the start: deals gone quiet, approaching deadlines, unanswered reviews, duplicates. Everything that creates or changes records, winning a deal, creating an engagement, opening the next period, is off until you switch it on.
What happens when an automation fails?
Temporary errors are retried automatically, up to four attempts with increasing pauses. A run that still fails shows as failed in Activity, with the reason, and can be retried by hand.
Can we build our own automations?
Yes, in a first version: a workflow starts by hand or from a form submission, checks a value and adds a note to the CRM. More steps are being added; the Standard catalog covers the common handovers today.

Keep exploring