--- title: "Push by Techulus Integration" description: "Send instant push notifications to phones, tablets, and desktops from any flow with Push by Techulus. Agents deliver a title, message, and custom link straight to the device." url: https://flowrunner.ai/integrations/techulus-push date_modified: 2026-08-07T17:20:23-07:00 --- # Push by Techulus [Messaging](https://flowrunner.ai/integrations/category/communication-messaging) Send instant push notifications to phones, tablets, and desktops from any flow with Push by Techulus. Agents deliver a title, message, and custom link straight to the device. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 5 actions · API key · available Capability data verified 2026-08-04 1. A deployment health check fails for the fourth time in twenty minutes 2. Agent confirms the failures are the same check on the same service rather than four unrelated blips 3. Agent sends a normal push to its own devices with the run link, no Do Not Disturb override 4. Agent waits out the response window and confirms nothing has changed on the service 5. Agent reads the local time for the on-call rotation and recognises it is outside working hours 6. Agent posts the failure history and the proposed escalation into the platform channel 7. The on-call lead decides whether to break Do Not Disturb across the team's devices or hold until morning ## What This Integration Enables Push by Techulus is the connector you reach for when the recipient is you and the people you work with. Five actions: three ways to send, two ways to change who is on the receiving end. An agent can broadcast to every device on the account, broadcast to every device of every member of a team by supplying that team's API key, or narrow to a specific device group so an alert reaches desktops and leaves phones alone. A notification carries a title and message plus a custom sound, a grouping channel, a tap through link and an image, so the person who gets it can go straight to the run rather than hunting for it. Two mechanical details shape how you build with it. Send Notification waits for delivery and returns per device results, which is genuinely useful for small device counts and turns into timeouts past about ten devices, which is what Send Notification Asynchronously exists for. And the iOS time-sensitive flag is available on every send action, which means the ability to override someone's Do Not Disturb is one boolean away from every alert in your flow. That is not a reason to avoid it. It is a reason to decide, deliberately and in advance, which alerts are allowed to use it and who gets to say so. That decision is [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) applied to the alerting layer itself rather than to the work the alert is about. ### Without FlowRunner **Alerts stop at the dashboard**: A failing check is visible to anyone who happens to be looking at a screen **Team routing lives in someone's head**: Who receives which alert depends on which personal key was hardcoded where **Urgency is claimed, not decided**: Every alert either shouts or whispers, with no step in between ### With FlowRunner **The alert reaches the device**: A push lands on phones, tablets and desktops with a tap through link to the run **Routing follows the team**: Team keys broadcast to every member's devices and membership is managed from a flow **Urgency escalates deliberately**: The Do Not Disturb override is a separate decision, taken by a person, on the alerts that earn it ## Use Case Scenarios ### Build failure that lands where the fix happens A pipeline in [GitHub](https://flowrunner.ai/integrations/github) fails on the main branch. The agent reads the failing job and the first error line, then calls Send Notification with the job name as the title, the error as the message, a link straight to the run and the build channel for grouping. The developer taps the notification and is looking at the log. No dashboard, no search, no asking in chat which build broke. ### Broadcasting a maintenance window to a whole team A planned maintenance window opens. The agent sends with the platform team's API key so every member's devices receive it at once, using Send Notification Asynchronously because the team is well past ten devices and a synchronous send would sit there waiting for per device results. It posts the same message into [Slack](https://flowrunner.ai/integrations/slack) for the searchable record, because a push is a nudge and a channel is a log, and the two jobs are different. ### Alerting the desktops and leaving the phones alone A long running report finishes and the people who care about it are at their desks. Rather than pushing to every device, the agent calls Send Notification To Group against the desktops group created in the Push console. Phones stay quiet. This action requires the account API key rather than a team key, which is a constraint worth encoding in the flow rather than discovering at runtime. ## Human-in-Loop Highlight The iOS time-sensitive flag pierces Do Not Disturb. That is a phrase worth reading slowly, because what it means in practice is that your automation is overruling a decision a human being made about their own evening. There is no undo and no way to soften it after the fact: the phone rings, in a meeting, in a cinema, at two in the morning, and the credibility of every future alert you send is decided by whether the thing on the screen was worth it. Nothing in the connector can judge that. It does not know where the recipient is, what time it is for them, or whether the check that failed four times is a real outage or a flapping probe. So the agent handles the ordinary path on its own, a normal push with the run link. When the escalation ladder reaches the step that would set time-sensitive and broadcast on a team key, it stops and asks: "Check payments-api-health has failed 4 times in 20 minutes and has not recovered. Escalate to a time-sensitive push across all 14 devices on the Platform team key, breaking Do Not Disturb, or hold until 08:00?" One person decides whether this is worth waking people for. Two other actions on this connector deserve the same care for a quieter reason: Invite Team Member and Remove Team Member change alert routing immediately, so an offboarding sweep that removes the wrong member silently un-pages whoever is actually on call this week. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 5 actions ### Notifications 3 - **Send Notification** Sends a push notification to every device connected to the account and waits for delivery to complete before returning per device results. Supports a custom notification sound, a grouping channel, a tap through link, an image, and the iOS time-sensitive flag that pierces Do Not Disturb. Supplying a team API key broadcasts to all devices of every member of that team. - **Send Notification Asynchronously** Queues a push notification for every connected device and returns as soon as it is accepted, without waiting for per device delivery results. The recommended action past roughly ten target devices, since it avoids long running requests and timeouts. Accepts the same sound, channel, link, image and time-sensitive options. - **Send Notification To Group** Sends only to the devices in a specific device group, letting a flow target a subset such as desktops or tablets. Groups are created in the Push console and identified by group ID. This action requires the account API key and does not accept team keys. ### Team Management 2 - **Invite Team Member** Invites a user by email to join one of your Push teams. Once accepted, their devices start receiving every notification sent with that team's API key. Requires the account API key plus the team's key. Part of the Push management API, which is currently in beta. - **Remove Team Member** Removes a member from a team or revokes a pending invitation. The removed user's devices immediately stop receiving notifications sent with that team's key, which makes this an alert routing change as much as an access change. Requires the account API key plus the team's key. Part of the Push management API, which is currently in beta. ## Frequently Asked Questions ### What can FlowRunner do with Push by Techulus? FlowRunner agents can run Send Notification, Send Notification Asynchronously, and Send Notification To Group in Push by Techulus, plus 2 more actions. ### Does connecting Push by Techulus to FlowRunner require OAuth? No. Push by Techulus connects to FlowRunner with an API key, no OAuth flow required. ### Can Push by Techulus trigger a FlowRunner workflow automatically? Push by Techulus doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Push by Techulus?** This integration exposes Push by Techulus to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/techulus-push. Site index: https://flowrunner.ai/llms.txt