Connected Services

ThinkForge connects to 11 external services through the CallConnectedAPI skill. Connected services let tools read data from and push data to the platforms you use daily — project management, communication, CRM, scheduling, and financial tools.

The Integration Model

All external integrations share a common architecture:

  1. One skill, many services — A single CallConnectedAPI skill handles all 11 services. You specify which service and operation in the tool definition.

  2. Credential-gated — Each service requires credentials (API keys, OAuth tokens) configured through a dedicated UI. Tools cannot run API operations until credentials exist.

  3. Target parameters saved per-tool — When an operation needs to know where to operate — which repo, which channel — those targets are configured once and saved with the tool. They don't change between runs.

  4. Content flows from the pipeline — The actual data being sent (message text, issue body, task name) comes from previous steps in the tool's execution flow.

For beta, credentials for all 11 direct integrations are managed from API → Service Credentials... in the main menu. The older individual per-service API test dialogs are not exposed as product UI. n8n is not a connected service in this catalog; current tools call each provider directly.

Supported Services

Project Management

GitHub — Repositories, issues, and pull requests. Use for development workflow integration: pull open issues for standup reports, create issues from processed input, monitor PR status.

ClickUp — Workspaces, tasks, and lists. Use for task management: pull tasks for reporting, create tasks from processed content, update task status.

Linear — Teams and issues. Use for engineering project management: pull team issues, create issues from bug reports or feature requests.

Asana — Projects and tasks. Use for team task coordination: pull project tasks, create tasks from meeting notes or action items.

Communication

Slack — Channels and messages. Use for team communication: pull channel messages for summarization, post updates or reports to channels.

Discord — Servers, channels, and messages. Use for community management: pull channel activity, post notifications or content.

Knowledge & Content

Notion — Pages and databases. Use for knowledge management: search pages, create documentation, query structured databases.

CRM & Sales

HubSpot — Contacts and deals. Use for sales workflow: pull contact lists, create contacts from processed leads, manage deal pipeline.

Scheduling

Calendly — Event types and scheduled events. Use for scheduling insights: pull upcoming events, generate availability reports.

Financial

Stripe — Customers, payments, and subscriptions. Use for revenue reporting: pull payment data, generate subscription reports, monitor customer status.

QuickBooks — Customers and invoices. Use for accounting workflows: pull invoice data and generate financial reports. Initial OAuth authorization is configured manually with Intuit credentials and the company Realm ID. Fire then refreshes expiring access tokens automatically, retries once after an authorization failure, and persists the latest rotated access and refresh tokens. A revoked or expired refresh token requires authorization again.

Common Tool Patterns

Daily digest tools — Pull data from a service on a schedule, summarize with AI, write a report or post to Slack.

Intake processing — Receive content (from email, web capture, or manual input), process it with AI, then create items in a project management tool.

Cross-service sync — Pull from one service, transform, push to another. GitHub issues to Linear, Slack messages to Notion, etc.

Report generation — Pull data from a financial or CRM service, filter and aggregate with data skills, format with AI, write to file.

Security Model

Credentials are stored locally. They never leave the machine except when making API calls to the respective services. No credentials are sent to ThinkForge servers or stored in the cloud.

When a tool runs without a person present — from a trigger, Power Strip, or the mobile app — it uses the same stored credentials. If credentials are missing or unusable, the operation fails with a clear error rather than prompting. QuickBooks access-token renewal works in that state as long as its stored client credentials and refresh token remain valid.