Use TimeCamp from Claude
Add the TimeCamp connection to a Space that runs Claude, then use it from every channel in that Space.
Connect TimeCamp once, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.
Add the TimeCamp connection to a Space that runs Claude, then use it from every channel in that Space.
Add the TimeCamp 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.
TimeCamp tracks time against projects and tasks so teams can see where billable hours actually go. The current type.com connection covers one action, pulling the list of root-level projects, so a manager can ask Claude for a quick view of what's active before digging into billing or reporting elsewhere.
Connect TimeCamp once, then decide which Spaces can use it in threads, skills, automations, and coding work.
Once TimeCamp 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 TimeCamp 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.
Pull the list of active root-level projects before a status meeting, instead of logging into TimeCamp to check.
Get the list of TimeCamp projects so I know what's currently active before our standup.
Check that a client's project is set up in TimeCamp before asking the team to log hours against it.
List TimeCamp projects and confirm Acme Q4 Retainer is already set up.
Compare the TimeCamp project list against another system's project list to spot anything missing.
Get the TimeCamp project list and tell me which of our 10 active clients aren't on it yet.
Returns TimeCamp's root-level projects, which represent top-level tasks in the account.
TimeCamp provides an API for time-tracking automation, including projects, tasks, users, entries, reports, attendance-style data, exports, and token-authenticated access to workspace time data.
The current connection supports pulling the list of root-level projects, so it's useful for a quick status check rather than detailed time-entry reporting.
TimeCamp uses an API key. An admin adds it once when creating the connection, then controls which Spaces can use it.
Yes. An automation can pull the project list periodically and flag anything new or missing in a channel.
Yes. Once TimeCamp 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 TimeCamp 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 Smartsheet to Claude in type.com with OAuth sign-in, so a Space is ready to work with sheets and reports over time.
Connect WordPress.com to Claude in type.com to plan, draft, and review posts and pages with the agent before anything goes live.
Connect Gmail and Google Calendar to Claude in type.com to search inbox context, draft replies, and schedule meetings from a shared thread.
Connect Google Drive & Docs to Claude in type.com to search for files, read Doc contents, and update Sheets from a shared thread.