What does the Bench integration actually let Lyro do?

Only one thing: pause for a set interval through the Sleep action. It doesn't run benchmarks, read results, or connect to any other Bench functionality - Lyro uses it purely to pace a sequence of steps.

Why would a pause matter inside a conversation Lyro is handling?

Some workflows call a slow or rate-limited system as part of resolving a request. A Sleep pause lets Lyro hold between those calls instead of firing them back to back and risking a failed or throttled request.

Can Lyro use Sleep alongside other connected tools in the same workflow?

Yes - Sleep is a pacing step, so it can sit between calls to any other integration Lyro has connected, holding for the set interval before the next action runs.

Does the length of the pause change from one use to another?

The interval is set for each call, so a workflow can pause for as long or as short as that step needs before Lyro continues.

Bench MCP integration

Pauses a step for a set interval through Bench's single Sleep action, pacing a run of calls instead of firing them at once.

Connect Bench See all integrations

1actions available

What your agent can do with Bench

Every action runs live through MCP. Nothing to build, nothing to maintain.

Sleep.

See all 1 actions

How businesses use Bench + Lyro

Each card is one request a support team gets, and the Bench actions Lyro runs to close it.

Pace calls to a rate-limited system
When a workflow needs to hold off between requests to a slow or rate-limited system, Lyro uses Bench's Sleep action to wait the set interval before the next call.
Run SleepPace Workflow Steps
Space out a retry after a failure
If a step needs to be retried, Lyro can pause with Sleep first so the retry doesn't hit the same system again immediately.
Run SleepDelay Retry
Stagger a batch of updates
When several updates need to go out one after another, Lyro inserts a Sleep pause between them instead of sending them all at once.
Run SleepStagger Updates
Sequence a step in a wider workflow
When one action needs to finish settling before the next starts, Lyro holds with Sleep for the set interval before continuing the workflow.
Run SleepSequence Workflow Step

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Bench actions it has and picks the ones a request needs.

01
Connect Bench
Authorize the Bench account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Bench actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Bench · Lyro

Everything else about Bench

Setup, permissions, and the limits of what Lyro can do inside Bench.

Only one thing: pause for a set interval through the Sleep action. It doesn't run benchmarks, read results, or connect to any other Bench functionality - Lyro uses it purely to pace a sequence of steps.