Communication · Integration
Blink
Add Blink to your product for your customers, and give your AI agents governed access to it.
Blink is an employee app for frontline and deskless staff, so its data centres on people rather than documents: user profiles, teams, the company directory and the feed that internal communications are published to, alongside chat. The API on api.joinblink.com is token authenticated and returns a structured error body such as {"code":"UNAUTHORIZED","message":"Missing token"} rather than an HTML login page, which makes credential problems easy to distinguish from routing ones. The population is the awkward part for integrators: frontline workers frequently have no corporate email address, so identity is anchored on a Blink user id or phone number and matching against an HR system on email alone will silently miss most of the workforce. Access tokens are issued per organisation and scoped to that tenant, so a multi-brand customer needs a connection per Blink instance. Chat content is personal communication and should be treated as out of scope for automation even where it is reachable, with feed posts being the appropriate write surface. fastn holds each customer's token, keeps the per-organisation scoping straight and maintains the connection.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Blink organisation so joiners and leavers in your HR product are provisioned and deprovisioned automatically
Publish an announcement to the right team's feed when an event happens in your system
Keep team structure and job titles in the Blink directory aligned with your source of record
Match frontline workers to your own records using Blink user ids where no work email exists
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent which Blink users in one tenant have no matching record in the HR system
Have an agent draft a feed post for a named team and hold it for human approval before publishing
Let an agent deactivate a leaver's profile, with the change audited per tenant against that tenant's own token
Example prompt
Which staff in the Warehouse team are still active in Blink but have left in our HR system?
Set up Blink in 4 steps
- 01Enable the Blink connector from your fastn dashboard.
- 02Have each customer authorise their own Blink account, so calls run under their credentials rather than a shared key.
- 03Decide which messages, conversations and participants your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Blink integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Blink integration without building it. Your customers connect their own Blink account inside your product and work their messages, conversations and participants there, with no per-customer code on your side.
- Handle the part that actually costs time: anything sent is user-visible, so duplicates and misfires are immediately embarrassing. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Blink update is not your on-call problem.
- One integration serves your product and your agents. The same governed Blink connection powers in-product features and gives AI agents scoped, audited access, so you put the right message in front of the right team automatically without wiring it twice.
Used by these teams
Compare with
Slack
Microsoft Teams
TwilioOften used alongside
Tools the same teams tend to run next to Blink, across other categories.
Aircall
Calendly
Gong
Google CalendarBlink integration FAQ
How do I add a Blink integration to my product?
Enable the Blink connector in your fastn dashboard, then let each customer authenticate their own Blink account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Blink client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Blink account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Blink account and only ever sees their own messages, conversations and participants. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Blink integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent which Blink users in one tenant have no matching record in the HR system
Who maintains the Blink integration?
fastn does. When Blink changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does each customer connect their own Blink account?
Yes. Every customer authorises their own Blink account, so messages, meetings and notifications originate from their workspace under their permissions. You never proxy through a shared account, which also means a customer revoking access affects only their own connection.
How are duplicate notifications avoided?
Sends are deduplicated per event, so a retry after a network failure does not post the same message twice into a channel people are reading.
What can I build with the Blink integration?
A common starting point: let a customer connect their own Blink organisation so joiners and leavers in your HR product are provisioned and deprovisioned automatically. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Blink integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Blink does not change your per-connector cost. You can start free with 3 connected accounts.
Add Blink to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.