Integrations

Connect Kwirker to the tools your team already uses.

• Slack — let agents post, read, and summarise channel content.
• GitHub — review PRs, triage issues, run CI-adjacent tasks. You can also link a repo for agents to search by meaning, separately from this personal connection.
• Discord, WhatsApp — bot-style conversation surfaces.
• Zoom — agents can join calls as a participant (add-on).
• Google Meet — link your Google account so agents can create and manage meeting spaces, and pull recordings, transcripts, and participant info after a call ends. Joining a live meeting isn't supported yet.
• Gmail — link your Google account, listed separately as "Gmail (Mailbox skill)," so agents can read, search, label, archive, and send mail as you. This is a distinct link from Google sign-in and Google Meet, so linking one doesn't grant the others. If you link more than one Gmail account, an agent asks which mailbox to use before it acts. Agents can archive a message but never permanently delete one — removing mail for good still means opening Gmail yourself.
• merge.dev — link your tenant's HRIS, accounting, or CRM for agent access.
• Langflow — a visual flow builder (add-on) for designing sub-agent flows on a canvas. Each tenant gets its own workspace, provisioned the first time an owner or admin opens it.

Personal connections — Slack, GitHub, Discord, WhatsApp, Zoom, Google Meet, Gmail — are set up under Settings → Linked identities. Tenant-wide connections like merge.dev and Langflow are set up under Organization → Integrations by an owner or admin.

Langflow is available if your plan includes it. If it doesn't, an owner or admin can subscribe to it directly as an add-on from Organization → Billing — look for the Langflow sub-agent composer card and click Subscribe to Langflow. Once it's available, the Integrations page shows a Build and compose sub-agent flows visually, then promote them to agents tile with a button to provision and open your workspace; once it's running the same tile becomes an Open shortcut back into it.

Promoting a flow to an agent

Once your workspace is running, an owner or admin sees a Promote a flow to agent button next to Open on the Integrations page. It turns a flow you've built in Langflow into a first-class agent with its own source repository:

1. Click Promote a flow to agent and search for the flow by name — you pick from a list of your workspace's flows rather than typing an id.
2. Optionally give the new agent a name and slug; leave either blank and it's derived from the flow's name.
3. Confirm in the dialog that appears — this step is a deliberate checkpoint because promoting creates a new agent immediately and isn't undone from here (you'd delete the agent afterward to remove it).
4. Once promotion finishes, a link takes you straight to the new agent.

Which flows can be promoted. Promotion covers flows built around a single language model — optionally with an agent component and tools wired into it. That's the shape it can turn into an agent faithfully. Flows that do more than one model call, or that add retrieval/RAG, routing, memory, or other multi-step components, aren't promoted: rather than quietly creating an agent that drops part of what your flow does, promotion stops and reports which components it couldn't carry over, so nothing is created. Simplify the flow (or split a multi-step pipeline into separate single-model flows) and promote each one.

If a flow's name is already taken by an existing agent's slug, pick a different slug and try again. Promotion also respects your plan's agent-creation limit, the same as creating an agent any other way.