Use Roam from Claude
Add the Roam connection to a Space that runs Claude, then use it from every channel in that Space.
Connect Roam once, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.
Add the Roam connection to a Space that runs Claude, then use it from every channel in that Space.
Add the Roam connection to a Space that runs Codex, then use it from every channel in that Space.
Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.
Roam HQ provides secure messaging and group collaboration built for enterprise access control, with SCIM support for provisioning users at scale. With Roam connected to a type.com Space, the agent can create a group chat, add a new user through SCIM, or react to a message, so team setup and day-to-day chat tasks happen in the same place.
Connect Roam once, then decide which Spaces can use it in threads, skills, automations, and coding work.
Once Roam is connected in type.com, install the type.com CLI, and Claude Code or Codex can call its tools with type-cli integrations call. Calls run with your type.com access, and the credentials stay on type.com's servers.
In a Space with Roam connected, describe the job, and type.com proposes an automation with its trigger, schedule, and destination. Runs can start on a schedule or from a webhook, Slack, GitHub, Linear, email, or RSS, and each run leaves a thread the team can read.
Create a group address with an admin set, ready for the right people to join.
Create a Roam group called Launch War Room with Dana as admin.
Add a new user through SCIM so access is set up consistently.
Create a Roam user for our new hire using their work email.
Add a reaction to acknowledge a message without typing a full reply.
React with a thumbs up to the message confirming the deploy went out.
Adds members or admins to an existing Roam group, including bulk additions.
Reacts to a specific chat message with an emoji.
Creates a group address for chat, optionally with an admin-only management mode.
Provisions a new group through SCIM for managing access permissions.
Provisions a new user through SCIM using their primary email as the username.
Roam HQ provides APIs for secure collaboration and event-oriented communication workflows. The On-Air API can create and manage events, guest lists, RSVPs, and attendance; integrations can also describe chat, file-sharing, messaging, and enterprise collaboration capabilities conservatively.
Yes. With a Roam connection shared to a type.com Space, the agent can create a group, provision a user through SCIM, or react to a message from a thread.
Roam supports an API key or OAuth. An admin sets up the connection with either method and picks which Spaces can use it.
Yes. Ask the agent to add several users or group members at once, referencing the SCIM-based creation tools.
Yes. Once Roam is connected in type.com, install the type.com CLI, and Claude Code or Codex can call its tools with type-cli integrations call. Calls run with your type.com access, and the credentials stay on type.com's servers.
Yes. In a Space with Roam connected, describe the job, and type.com proposes an automation with its trigger, schedule, and destination. Runs can start on a schedule or from a webhook, Slack, GitHub, Linear, email, or RSS, and each run leaves a thread the team can read.
Not exactly. type.com uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.
Connect Listclean to Claude in type.com to verify email lists and download clean results in a shared thread.
Connect Loops.so to Claude in type.com to create, find, and clean up SaaS email contacts and properties from shared threads.
Connect Mailboxlayer to Claude in type.com to check email syntax, domain, and SMTP validity in a shared thread.
Connect Mailcheck to Claude in type.com to validate domains and verify email addresses from a shared thread.