Skip to main content

​
Overview

Cofounder’s power comes from its ability to connect and orchestrate actions across multiple platforms and tools. Whether you’re syncing data between GitHub and Linear, automating email responses, or creating complex multi-tool workflows, integrations are the foundation of powerful automation.

​
How Integrations Work

​
Connection Model

When you connect an integration to Cofounder:
  1. OAuth Authorization: You authenticate directly with the service
  2. Credential Storage: Your tokens are securely stored and encrypted
  3. Permission Inheritance: Cofounder uses your exact permissions and access levels
  4. Automatic Refresh: Tokens are automatically refreshed when needed
Cofounder never sees your passwords—all authentication happens directly with the service provider.

​
Supported Integration Categories

Development Tools:
  • GitHub (repositories, issues, pull requests)
  • LaunchDarkly (feature flags)
Communication:
  • Slack (messages, channels, reactions)
  • Email (Gmail, Outlook)
  • Loops (emails)
  • Intercom (messages)
Productivity:
  • Google Workspace (Docs, Sheets, Calendar)
  • Notion (databases, pages)
  • Airtable (bases, records)
Project Management:
  • Linear (issues, projects, teams)
Data and Product:
  • Metabase (dashboards)
  • Posthog (product analytics)
  • Supabase (database)
Other integrations:
  • PhantomBuster (linkedin and twitter automation)
  • Web search, web data, and web scraping
  • Weather
  • Enrichment via Apollo

​
Flow Creation with Integrations

​
Direct Flow Creation

You can create flows that integrate with external tools in several ways: From Slack: 
@cofounder create a flow that creates a GitHub issue 
when someone reacts with 🐛 to a message in this channel
From Web Interface:
  • Navigate to the Flows section
  • Describe your automation needs in plain English
  • Cofounder will map your requirements to the appropriate integrations

​
Flow Components

Triggers:
  • External events (new GitHub issue, Slack message, email received)
  • Scheduled events (daily, weekly, monthly)
  • Manual triggers (run on demand)
Actions:
  • Create, read, update, or delete data in connected services
  • Send notifications or messages
  • Generate reports or summaries
Conditions:
  • Filter events based on content, author, or other criteria
  • Route different scenarios to different actions
  • Handle error conditions gracefully

​
Advanced Integration Features

​
File Processing

Upload and process files across different platforms:
  • Document Analysis: Extract text and insights from PDFs, Word docs
  • Image Processing: OCR text extraction from images
  • Data Import: Parse CSV files and import data to other services
  • Automatic Organization: File uploaded to Slack can be automatically saved to Google Drive with proper naming

​
Cross-Platform Data Sync

Keep data synchronized across multiple tools:
  • Issue Synchronization: Sync GitHub issues with Linear tickets
  • Contact Management: Keep CRM data updated from email interactions
  • Project Updates: Update project status across multiple project management tools

​
Workflow Orchestration

Create complex workflows that span multiple platforms: 
Trigger: New customer email
↓
Action 1: Create CRM contact (if doesn't exist)
↓
Action 2: Create support ticket in Linear
↓
Action 3: Send acknowledgment email
↓
Action 4: Notify team in Slack
↓
Action 5: Schedule follow-up task

​
Best Practices

​
Security and Access Management

Regular Reviews:
  • Periodically review connected integrations
  • Remove access for unused services
  • Update permissions when team roles change
Principle of Least Privilege:
  • Only connect integrations you actively use
  • Review what permissions each integration requires
  • Disconnect integrations when projects end

​
Flow Design

Start Simple:
  • Begin with single-platform automations
  • Add cross-platform elements gradually
  • Test thoroughly before enabling auto-approval
Error Handling:
  • Consider what happens when external services are unavailable
  • Build in retry logic for transient failures
  • Have fallback actions for critical processes
Documentation:
  • Document complex workflows for team members
  • Include troubleshooting steps
  • Maintain up-to-date integration credentials

​
Common Integration Patterns

​
Development Workflow Automation

GitHub ↔ Linear Integration:
  • Auto-create Linear tickets from GitHub issues
  • Update ticket status when PRs are merged
  • Link commits to tickets automatically
Code Review Automation:
  • Notify relevant team members when reviews are needed
  • Track review metrics and generate reports
  • Automatically merge PRs when criteria are met

​
Project Management Sync

Multi-Tool Project Tracking:
  • Sync project status across Jira, Asana, and Slack
  • Generate unified progress reports
  • Automatically update stakeholders

​
Customer Communication

Support Ticket Automation:
  • Create tickets from customer emails
  • Route based on content and priority
  • Provide automatic status updates

​
Troubleshooting Integrations

​
Connection Issues

Authentication Failures:
  • Re-authenticate expired tokens
  • Check if service permissions have changed
  • Verify account access hasn’t been revoked
API Limits:
  • Monitor rate limiting from external services
  • Implement appropriate delays in high-volume flows
  • Use batch operations when available

​
Data Sync Problems

Missing Data:
  • Check if source data meets filter criteria
  • Verify field mappings are correct
  • Look for API permission issues
Duplicate Records:
  • Implement deduplication logic
  • Use unique identifiers for matching
  • Set up proper conflict resolution

​
Performance Optimization

Slow Flows:
  • Minimize unnecessary API calls
  • Use webhooks instead of polling when possible
  • Batch operations when supported by the API
Resource Usage:
  • Monitor flow execution frequency
  • Optimize trigger conditions
  • Consider caching for frequently accessed data
⌘I