--- title: Flock API Integration on Truto slug: flock category: Default canonical: "https://truto.one/integrations/detail/flock/" --- # Flock API Integration on Truto **Category:** Default **Status:** Generally available ## How it works 1. **Link your customer's Flock account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Flock.** The Proxy API is a 1-to-1 mapping of the Flock API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Push real-time alerts into Flock channels** — SaaS companies offering monitoring, incident management, or DevOps tools can send automated notifications—like build failures, P1 alerts, or deployment statuses—directly into designated Flock channels, keeping engineering teams informed without context-switching. - **Sync user directories for targeted messaging** — B2B SaaS products need to map their own user records to Flock user IDs so they can route notifications, @mentions, and DMs to the right people. Pulling the Flock roster eliminates manual mapping and keeps recipient lists accurate as teams change. - **Send interactive messages that drive action from chat** — CRM, HR, and project management tools can send FlockML-powered messages with inline buttons—approve an expense, acknowledge an incident, rate your week—so end users take action inside Flock and the response syncs back to the originating SaaS platform. - **Automate channel creation for structured workflows** — SaaS products that manage projects, deals, or incidents can programmatically create and organize Flock channels—one per deal, one per sprint, one per incident—giving teams a dedicated space that's provisioned automatically when a workflow begins. - **Enable conversational commands via slash integrations** — By registering slash commands through FlockOS, a SaaS product lets end users trigger workflows—logging a call note, creating a task, pulling a report—directly from the Flock chat box, reducing the need to switch to a separate dashboard. ## What you can build - **Channel-based alert routing** — Let your users select a Flock channel during setup and automatically deliver event-driven notifications—new tickets, deal stage changes, deployment results—into that channel in real time. - **Actionable incident response messages** — Send rich FlockML messages with Acknowledge, Escalate, or Resolve buttons so on-call engineers can update incident status without leaving the chat. - **Automated employee pulse DMs** — HR and engagement platforms can send scheduled direct messages to employees with inline rating buttons, capturing sentiment data back via webhook for analytics dashboards. - **Dynamic incident or deal channels** — Programmatically create a new Flock channel when a critical event occurs—like a P1 alert or a new enterprise deal—and auto-invite the relevant team members. - **User directory sync for identity mapping** — Pull the full Flock roster so your product can reliably resolve internal user IDs, enabling accurate @mentions, DM routing, and permission-aware notifications. - **Rich link previews for SaaS records** — Unfurl URLs pasted into Flock conversations into visual cards showing record details—task title, assignee, status, due date—so teammates get context at a glance. ## FAQs ### What authentication method does Flock use for API access? FlockOS uses OAuth 2.0. When an end user installs your app in their Flock workspace, an access token is issued that your integration uses to call Flock APIs on behalf of that workspace. Truto handles the OAuth flow, token storage, and refresh so you don't have to manage credentials directly. ### Is the Flock integration available as a pre-built Unified API in Truto? Not yet. Flock is available as a custom integration built on request. Truto will handle auth, pagination, and API abstraction for your specific use case. Contact the Truto team to scope and prioritize the endpoints you need. ### What Flock API endpoints are most commonly needed? The most requested capabilities are chat.sendMessage for posting messages, roster.listContacts for fetching the team directory, groups.list and groups.create for channel management, and webhook event subscriptions for capturing user actions and real-time events. ### Does Flock support interactive messages and inline actions? Yes. Flock supports FlockML, a markup language for rendering buttons, dropdowns, and other interactive elements inside chat messages. User interactions with these elements are delivered to your app via webhooks, enabling two-way workflows without leaving the chat. ### Are there rate limits on the Flock API? FlockOS enforces rate limits on API calls per token. Exact thresholds depend on the endpoint and your app's plan. Truto can implement retry logic and request throttling to help you stay within limits without dropping events. ### Can I target both channels and individual users with messages? Yes. The Flock messaging API supports sending to public channels, private groups, and individual users via direct messages. You can let your customers configure routing rules—for example, alerts go to a channel while personal reminders go as DMs.