Blink
HRSend feed posts, read forms, and provision users on Blink, the frontline employee experience app. Agents reach deskless staff where they already are and keep the roster in step with the HR system of record.
What This Integration Enables
Most workflow tooling quietly assumes a desk. Blink does not, and that is the reason to connect it. The workforce it serves is on a ward, in a cab, on a shop floor or in a plant, and for those people the phone app is not a convenience layer on top of email. It is the channel. FlowRunner agents use this connector to write into that channel and to keep the roster behind it honest, which are the two failure modes that actually hurt deskless teams: they are the last to hear anything, and their account state lags their employment state by weeks.
The connector covers three surfaces. Agents send, edit and dismiss feed events built as CardKit posts, with optional push notification, and can look an event back up by the external id it was sent with. They read the forms defined in the organisation and pull submissions with the submitter, the timestamp and every question and answer, which turns a completed site inspection into the ticket, task or record it deserves. And through Blink's SCIM 2.0 provisioning API, available on the enterprise plan with a separate SCIM token, agents create, patch, replace and disable users and groups so the roster tracks the HR system of record rather than a quarterly reconciliation. Blink's public API documents no webhook endpoints, so the form trigger polls and baselines its first run rather than replaying history.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Joiner, mover and leaver provisioning from the HRIS
A new hire is created in BambooHR. The agent reads the record, calls Create Provisioned User with the person's name, work email, department, manager and employee number, then patches their location group so they land in the right feed audience on day one. When someone changes site, the agent patches the group membership instead of opening a ticket. When someone leaves, the agent assembles the closure list and stops, because closing a frontline account is the one direction in this workflow that a person should confirm.
Site inspection submissions that open real work
A supervisor completes a safety inspection in the Blink app. On New Form Submission fires, the agent pulls the full submission with Get Form Submissions, reads the answers, and classifies the finding. A pass is logged and closed. A failure opens a Trello card for the maintenance queue with the site, the failing item and the submitter, and the agent sends a feed event back to the supervisor confirming what was raised and who owns it. The person who found the problem learns it went somewhere.
Targeted shift and roster announcements
A roster row changes in Google Sheets. The agent resolves the affected team, calls Get Feed Event Categories to pick the right category, and sends a feed event to that team only, with push enabled because the change lands inside the next shift. Broad announcements go out the same way but without push. The distinction matters more than it sounds: a push notification to the wrong audience at 04:00 is how frontline staff learn to ignore the app.
Human-in-Loop Highlight
The gate on this connector is Disable Provisioned User, and it is a gate because of who Blink serves. For a deskless employee the app is the route through which the employer reaches them at all, so disabling the account does not just revoke a login, it removes the person from every announcement, roster change and safety notice while they may still be on shift. The upstream signal is rarely as clean as it looks either. Termination records get entered early, transfers get typed as departures, and rehires arrive before the leaver row is corrected. So the agent does not act on that signal. It gathers the evidence, calls Get Provisioned User to confirm a single matching account, and treats the closure as a human-in-the-loop decision, posting to the People Ops channel: "Four Blink accounts are queued for disable from today's HR export. Nadia Okafor, leave date 02 Aug, no rehire flag. Tom Reilly, leave date 09 Aug, which is in three days. Confirm which of these to disable now, and which to hold." A person answers, the agent disables only the confirmed names, and every account that stays open stays open because someone decided it should.
Agent Capabilities
28 actionsFeed
6- Send Feed Event Sends a feed post to Blink users or teams. The body is CardKit JSON and at least one user id, team id or employee id recipient is required. Supports an optional push notification, comments, reactions, scheduled featuring, and a Blink-hosted attachment or image. Used for announcements, shift changes and alerts that have to reach staff without a corporate desktop.
- Update Feed Event Edits a feed event that has already been sent, replacing its CardKit body, with an optional push notification about the change. Used when a posted detail turns out to be wrong and the correction has to reach the same audience.
- Archive Feed Event Dismisses a feed event for every recipient, removing it from their feeds. Used to retire a notice once the situation it described has closed.
- Archive Feed Event for User Dismisses a feed event for one recipient while leaving it visible to the others. Used when a single person has acted on a request and should stop seeing it.
- Get Feed Event ID by External ID Returns the event id of a feed event looked up by the external id it was sent with. Used to find a post again later for an update or an archive. Where several events share an external id, which one is returned is undefined, so treat external ids as unique when sending.
- Get Feed Event Categories Returns the feed categories defined for the integration in the Blink admin panel, along with the integration's service id. Category ids are required when sending feed events, so this is the lookup step before a first post.
Users and Forms
3- Get Users Fetches users in the organisation with their profile details and linked accounts, filterable by user id, employee id, linked account id or external account id. Used to resolve a person into the identifiers the feed and linked-account actions need.
- Get Forms Returns the forms available in the organisation with their ids, names and timestamps. Used to discover which form a flow should watch.
- Get Form Submissions Returns submissions for a form with the submitter, the submission time and each question's id, title and answer, filterable by an inclusive timestamp range. Used to pull the full detail behind a submission before opening downstream work.
Linked Accounts
6- Add User Linked Account Creates a linked account for a user, storing that user's external service account details in Blink so an authenticated integration can act on their behalf. Used when connecting a person's third-party account during onboarding.
- Update User Linked Account Updates an existing linked account, replacing stored tokens, expiry or account identifiers. Only the fields supplied are sent. Used to refresh credentials before they lapse.
- Get User Linked Accounts Returns the linked accounts a single user holds for the integration. Used to check what a person has already connected.
- Get Linked Account Returns one linked account by its id, including the stored tokens, expiry and account identifiers. Used for a targeted read during a refresh flow.
- Get Linked Accounts Returns every linked account added for the integration across all users. Used to audit connection coverage across the organisation.
- Delete User Linked Account Deletes a linked account from a user, removing the stored external service details. Used during offboarding or when a person disconnects a service.
User Provisioning
7- List Provisioned Users Searches or lists users through Blink's SCIM 2.0 provisioning API, with SCIM filter expressions on id, externalId, manager, userName and employeeNumber. Used to reconcile the Blink roster against an HR system or identity provider.
- Get Provisioned User Returns one user by id through the SCIM API, including name, emails, enterprise attributes and custom Blink attributes. Used as the confirmation step before any provisioning change.
- Create Provisioned User Creates a user on the Blink platform through SCIM, with core profile fields, enterprise attributes such as department, manager and employee number, and custom Blink profile attributes. Used to onboard a joiner from the HR record.
- Replace Provisioned User Fully replaces an existing user through SCIM, so the fields supplied become the user's new state. Used when the HR system is authoritative and the whole profile is being restated.
- Patch Provisioned User Partially updates a user through SCIM with add, replace and remove operations. Used for the common case of a single changed attribute, such as a new manager or a site transfer.
- Disable Provisioned User Disables a user on the Blink platform through SCIM. This is the action that ends a frontline employee's access to the app their employer reaches them through, so route it through an approval rather than straight off an HR export.
- Get SCIM Service Provider Config Returns Blink's SCIM 2.0 service provider configuration, describing which provisioning features the API supports. Used to confirm capability before building a provisioning flow.
Group Provisioning
6- List Provisioned Groups Searches or lists groups through the SCIM API, with filter expressions on id, externalId and displayName. Used to find the group a joiner should land in.
- Get Provisioned Group Returns one group by id through the SCIM API, including its display name and members. Used to check membership before changing it.
- Create Provisioned Group Creates a group on the Blink platform through SCIM, optionally with an initial member list. Used to stand up a new site, shift or department audience.
- Replace Provisioned Group Fully replaces an existing group through SCIM, so the fields supplied become the group's new state. Used when an external directory owns the membership list outright.
- Patch Provisioned Group Partially updates a group through SCIM with add, replace and remove operations, which is how members are added or removed individually. Used for day to day roster movement.
- Disable Provisioned Group Disables a group on the Blink platform through SCIM. Used when a site closes or a shift pattern is retired.
Triggers
1 triggersEvent Triggers
1- On New Form Submission Fires for each new submission of the selected form. Used to turn a completed inspection, checklist or request into downstream work the moment it is submitted. The first run records a baseline and emits nothing, so history is never replayed. Afterwards each unseen submission fires once, oldest first, deduplicated by submission id. The trigger polls, because Blink's public API documents no webhook create or delete endpoints, and the polling interval can be set as low as 30 seconds.
Frequently Asked Questions
What can FlowRunner do with Blink?
FlowRunner agents can run Send Feed Event, Update Feed Event, and Archive Feed Event in Blink, plus 25 more actions.
Does connecting Blink to FlowRunner require OAuth?
No. Blink connects to FlowRunner with an API key, no OAuth flow required.
Can Blink trigger a FlowRunner workflow automatically?
Yes. Blink supports 1 trigger that can start a FlowRunner workflow automatically.
Start building with Blink
$100 in credits. No card required. Connect in minutes.