Boomship/Integrations
Work where your company already works.
Connect what you use. Every card says what Boomship can read, what it can change, what it cannot do, and how it is allowed in. Nothing is written to a service until you allow it.
Mission 0218·Launch Northstar v4Illustration
- Reading the current productnorthstar/web · release/v4
- Finding the launch briefNotion · Launch v4
- Checking brand decisionsmemory · 3 confirmed
- Reviewing customer researchDrive · 14 interviews
- Looking at the launch calendarLinear · NS-412
Context ready.a repository · 3 connectors · memory
Act 01What each one can do
Exactly what it reads, and nothing more.
Each verb below is the product’s own sentence for that connector, read from the code that does it. A verb the code lacks does not appear.
GitHub
CodeA connected repository is what Build Missions read, change and prove.
- Reads
- Indexes a repository into the project’s Brain: its code, its symbols and what imports what.
- Writes
- Commits a Mission’s change to a boomship/ branch. Never to your main branch.
- Verifies
- Fetches a pull request, tests it in a sandbox and reviews it before you merge.
- Cannot
- Push to your main branch or merge. On a host with no shell it edits through the git-data API and runs nothing, so tests stay “not run” there.
- Permission
- A GitHub token you store. Encrypted; only its last four characters are ever shown again.
Notion
Knowledge and toolsPages shared with the integration become project knowledge that runs read and cite.
- Reads
- Reads the pages you choose, nested blocks included, into a project’s Files.
- Keeps in sync
- Re-reads an imported page on your schedule when Notion says it was edited.
- Changes
- Nothing at the source. Boomship reads Notion; it never changes a page.
- Cannot
- Change a page, or read one that was not shared with the integration.
- Permission
- Connected by you: internal integration secret you paste, or sign-in through the host’s Notion app.
Linear
Knowledge and toolsIssues become project knowledge: what was asked, decided and discussed, cited by runs.
- Reads
- Reads the issues you choose, with description, labels and comments, into a project’s Files.
- Keeps in sync
- Re-reads an imported issue on your schedule when Linear says it was updated.
- Changes
- Nothing at the source. Issues are read, never edited.
- Cannot
- Create or change an issue, or comment on one.
- Permission
- Connected by you: personal api key you paste, or sign-in through the host’s Linear app.
Slack
Knowledge and toolsA channel’s conversation becomes project knowledge, with who said what.
- Reads
- Reads the latest 200 messages of a public channel you choose into a project’s Files.
- Keeps in sync
- Re-reads an imported channel on your schedule when a new message arrives.
- Changes
- Nothing at the source. Boomship reads a channel; it never posts.
- Cannot
- Post a message, or read private channels and direct messages.
- Permission
- Connected by you: bot token you paste, or sign-in through the host’s Slack app.
Gmail
Knowledge and toolsEmail threads you pick become project knowledge. Access is read-only.
- Reads
- Reads the threads you find with Gmail search into a project’s Files, one document per thread.
- Keeps in sync
- Re-reads an imported thread on your schedule when Gmail records a change to it.
- Changes
- Nothing. Mail is read-only; Boomship never sends.
- Cannot
- Send, reply, archive or label. The scope is read-only.
- Permission
- Connected by you: sign-in through the host’s Google app. Read-only scopes.
Google Drive
Knowledge and toolsDocs, Sheets, Slides, PDFs and Word files become project knowledge. Access is read-only.
- Reads
- Reads the files you choose (Docs, Sheets, Slides, Markdown, PDF, Word) into a project’s Files.
- Keeps in sync
- Re-reads an imported file on your schedule when Drive’s change feed lists it.
- Changes
- Nothing. Files are read-only; Boomship never edits one.
- Cannot
- Create, edit or share a file. The scope is read-only.
- Permission
- Connected by you: sign-in through the host’s Google app. Read-only scopes.
Airtable
Knowledge and toolsTables become project knowledge, and runs can update records in the tables you allow.
- Reads
- Reads the tables you choose, every field of up to 500 records, into a project’s Files.
- Writes
- Runs can find and update records, field by field, only in the tables you allow here. Each update is a step on the run.
- Keeps in sync
- Re-reads an imported table on your schedule. Airtable gives no change marker, so each check reads the records and compares them.
- Cannot
- Create a base or a table, delete a record, or touch a table you did not allow.
- Permission
- Connected by you: personal access token you paste, or sign-in through the host’s Airtable app.
Anthropic, OpenAI, Google, OpenRouter
ModelsBoomship Auto picks a model for each step; you choose whose keys pay for it.
- Your keys
- Stored encrypted; only the last four characters are ever shown again. Your provider bills you directly.
- Or ours
- Where a deployment has managed keys, Auto can use them. Settings says which providers are available.
- Cannot
- Show a key again after it is saved, or bill you: your provider does.
- Permission
- Your provider keys, encrypted, last four shown; or the host’s managed keys where it has them. Settings says which.
Act 02Not yet
Not in this release.
People ask for these. Boomship does not do them yet; when it does, they will appear in the directory above with their own card.
- Phone and voice callsNot yet
- Sending email or messages for youNot yet
- Image and video generationNot yet
- Writing to CRMs such as HubSpot or SalesforceNot yet