When does Lyro send asynchronously instead of synchronously?

Send Push Notification Async is the recommended path above roughly ten devices, because it does not hold the request open while every device is reached. Send Notification Sync is the one to use when you need immediate confirmation that delivery to all devices and teams succeeded.

Can Lyro list the devices on an account or check delivery history?

No. The toolkit exposes four ways to send and two team-management actions, with no device listing and no delivery-history lookup. Send Notification Sync returning success is the only confirmation available, so a delivery audit trail has to live in the system that asked for the push.

Does removing someone also cancel an invitation they never accepted?

Yes. Delete Team Member or Invite is keyed to an email address and handles both cases - an active member losing access and a pending invitation being revoked - so a mistyped invite can be withdrawn before it is ever opened.

How is a webhook POST notification targeted?

Send Notification via Webhook POST delivers to all devices associated with a specific API key, so segmentation happens at the key or team level rather than per recipient. For narrower targeting Lyro uses Send Notification to Device Group instead.

Push by Techulus MCP integration

Pushes alerts to every device, to a single device group, or through a webhook, and manages who is on the team receiving them.

Connect Push by Techulus See all integrations

6actions available

Three actions you can hand over today

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

Send notification sync
Lyro delivers a push notification synchronously to all a user's linked devices. Messages arrive immediately and you know delivery succeeded before returning.
Invite user to team
Lyro sends a team invitation email to a user's address in Push. Users join your team instantly upon accepting the email without manual account creation.
Delete team member or invite
Lyro removes a user from your Push team or cancels their pending invitation. Access is revoked immediately and you maintain accurate team membership.

See all 6 actions

How businesses use Push by Techulus + Lyro

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

Alert the on-call device group, not everyone
Lyro pushes to a single device group with its own title, body, sound, and media, so a routine notice does not wake the whole account at three in the morning.
Send Notification to Device GroupSend Notification SyncSend Push Notification Async
Turn an upstream event into a push
A webhook POST against an API key lets another system's event reach the devices behind that key, with Lyro deciding the wording and which group actually needs to see it.
Send Notification via Webhook POSTSend Push Notification AsyncSend Notification to Device Group
Get a new responder onto the alert rota
Lyro sends the email invitation to join the team and confirms with a test push that the new member's devices are actually receiving alerts before the next shift starts.
Invite User to TeamSend Notification SyncDelete Team Member or Invite
Cut alert access the day someone leaves
Lyro removes the departing member or revokes their still-pending invite by email address, so alerts containing internal detail stop reaching a device the company no longer controls.
Delete Team Member or InviteInvite User to TeamSend Notification to Device Group

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 Push by Techulus actions it has and picks the ones a request needs.

01
Connect Push by Techulus
Authorize the Push by Techulus 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 Push by Techulus 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

Push by Techulus · Lyro

Everything else about Push by Techulus

Setup, permissions, and the limits of what Lyro can do inside Push by Techulus.

Send Push Notification Async is the recommended path above roughly ten devices, because it does not hold the request open while every device is reached. Send Notification Sync is the one to use when you need immediate confirmation that delivery to all devices and teams succeeded.

Every action available in Push by Techulus

All 6 actions your agent can call on Push by Techulus, straight from the live MCP connection.

Delete team member or invite
Remove a user from the team or revoke a pending invitation.
Invite user to team
Invite a user to a team by sending an email invitation.
Send push notification async
Send push notification asynchronously to all devices in an account or team.
Send notification sync
Send push notifications synchronously to all linked devices.
Send notification to device group
Send push notification to a specific device group.
Send notification via webhook post
Send push notifications to all devices associated with a specific API key via POST request.