Your privacy, your choices

We use necessary features to run the website and platform. With your permission, we also measure usage and performance and use marketing cookies for advertising and remarketing. Your choice applies in this browser across the website, signup and platform. Cookie policy

Closing this notice or pressing Esc lets you continue with necessary features only.

Skip to content

Platform · Automations

The routine runs on schedule. The result arrives with an owner.

An agent, a team or a flow runs the task on schedule, at the press of a button or when another system calls, and the result reaches whoever follows it.

Talk to a specialistTry it free
See how it works
Skyller · Team pending-task summary

Team pending-task summary

1 · Identity2 · When to run3 · What to run

Schedule preview

Every day · 09:00 · America/Sao_Paulo

Demonstration · illustrative data

SCHEDULE · BUTTON · EVENT

three ways to trigger, always with an owner and a history

NEXT 5 RUNS

the preview shows when it will run, before you save

STOPS AND ASKS FOR APPROVAL

a sensitive action with nobody on screen becomes a pending item

NOTICE TO COLLABORATORS

completed, failed or awaiting approval: owner and collaborators are notified

Where this shows up in your day

What repeats every week and depends on someone remembering.

Finance

The Monday summary

Someone gathers the open items, checks the procedure and sends the summary to the manager. When that person is out, the summary does not go out.

Every Monday, 9 a.m.

Customer service

The ticket that arrives after hours

The request arrives at 10 p.m., and triage only happens in the morning, when someone opens the queue.

Triggers when the ticket comes in

Quality

The check nobody wants to do

Comparing the published procedure with the week's records gets left for later. And later becomes never.

Runs on its own, tells the owner

How it works

From a written task to a run with a history.

  1. 01

    Describe the task

    Write the request as you would in the chat, or answer three questions and Skyller drafts the task and suggests the frequency and the agent.

  2. 02

    Choose who performs it

    An existing agent, team or flow, with its knowledge, tools and AI level.

  3. 03

    Set the trigger

    Every day, every week or every N hours or minutes, with a time zone and a preview of the next five runs. Or on demand: by the button and, depending on the plan, by another system.

  4. 04

    Adjust the follow-up

    The same conversation or a new one for each run, time limit, retries and who gets the notice.

  5. 05

    Follow the history

    Each run shows status, duration, who triggered it and the conversation it generated; failures and approval requests show up with the reason.

Live proof

Monday, 9 a.m.: the summary went out with nobody asking.

  1. Starting point

    The “Team open-items summary” automation runs every Monday at 9 a.m. with the operations agent, which checks the published procedure.

  2. What happens

    1. 01At 9 a.m., Skyller runs it: the agent checks the week's open items against the procedure and drafts the summary.
    2. 02The history records the run as completed, with its duration and the “View generated conversation” link.
    3. 03The owner and collaborators get the notice in the bell, with a preview of the result.

  3. Result

    The summary went out on time without depending on anyone remembering, and whoever follows it knows when and how it ran.

Skyller · Team pending-task summary

Team pending-task summary

1 · Identity2 · When to run3 · What to run

Schedule preview

Every day · 09:00 · America/Sao_Paulo

TimeStatusResult
09:00PreviewThe run has not been simulated yet

Demonstration · illustrative data

Good to know

  • The run uses the permissions of whoever created the automation, not a special access.
  • A sensitive action pauses the run until someone approves. A pending item with no decision does not become an action: it expires.
  • It triggers by schedule, by the button or by another system; a published document or a received message does not trigger it.

Fictional company and open items; the builder, the history and the notice are the product's.

To evaluate calmly

How it triggers, what it keeps and who follows along.

Select a topic to see its capabilities, conditions, and limits.

Clock with preview
Ready-made options (every day, every week, every N hours or minutes) and an advanced mode, with an explicit time zone and a preview of the next five runs.
Run now
Any automation runs at once from the button, in the background; the result appears in the history and in the notification bell.
Trigger from another system
In on-demand mode, the automation gets an address that the ticketing system, the CRM or the ERP calls with an API key, depending on the plan. The event data comes in as fields, and a missing field stays visible.

Real application

Ticket triage, built by the people who answer tickets.

  1. 01Support analyst

    Creates the on-demand automation “Ticket triage” with the support agent, whose base is the published documentation.

  2. 02Company IT

    Creates the API key, on plans with API access, and has the ticketing system call the automation for each new ticket.

  3. 03Skyller

    For each ticket, it classifies, points to the applicable procedure with the source and drafts the first reply.

  4. 04Support analyst

    Gets the notice, adjusts the reply and sends it; what falls outside the pattern, she handles directly.

  5. 05Coordination

    Follows in the history how many runs went through, how many failed and how long they took, and adjusts the task for the next ones.

Questions from whoever decides

What people ask before letting something run on its own.

Next step

Pick the routine someone forgets to do.

Write the task as you would ask in the chat, set the time and see the preview of the next runs.

Talk to a specialistTry it free