Skip to content
StellarFirmStellarFirm
Mission manual
Esc

Type a word to search every page. Try , or .

Module 06 · Integrations

Integrations

Connect the tools you already use. Learn how integrations work, which ones are available now, and which are Coming soon.

View as Markdown
On this page

Integrations connect your assistants to the tools you already use: your code host, your mail, your calendar, your issue tracker. An assistant that can see the right tool does better work, and an assistant that has to ask you for every detail does not.

Today three integrations are available, all for source control: GitHub, GitLab, and Bitbucket. Every other integration on this page is Coming soon.

How integrations work#

  1. Create an access token in the tool. Give it only the permissions the assistant needs. Each page lists them in plain words.
  2. Connect it. Open Integrations, pick the tool, paste the token, and press Connect.
  3. Ask for the work. In chat, tell the assistant what you want. It uses the tool without you pasting anything again.

Your token stays with your StellarFirm workspace. It is never shown back to you after you connect: the page shows only that the tool is connected. You never paste a token into a chat message.

Reads on its own, or waits for your Approve#

Every ability falls into one of two groups, and each integration page tells you which.

KindWhat it meansExamples
Reads on its ownThe assistant can do it without asking, because nothing leaves your controlList issues, read a pull request, list upcoming events, create a draft that is not sent
Waits for your ApproveThe assistant stops and asks before it does anything that sends, deploys, charges, publishes, or createsPush a branch, open a pull request, send mail, create an event

Every integration#

IntegrationCategoryStatus
GitHubSource controlAvailable
GitLabSource controlAvailable
BitbucketSource controlAvailable
SlackChatComing soon
TelegramChatComing soon
DiscordChatComing soon
GmailMail and calendarComing soon
OutlookMail and calendarComing soon
Google CalendarMail and calendarComing soon
Google DriveFilesComing soon
LinearIssue trackingComing soon
LovableApp buildersComing soon
SentryErrors and supportComing soon
PostHogErrors and supportComing soon
ResendEmail sendingComing soon
SendGridEmail sendingComing soon
StripePaymentsComing soon
NotionDocs and wikisComing soon
Jira and ConfluenceIssue trackingComing soon
AsanaIssue trackingComing soon
DatadogMonitoringComing soon
PagerDutyMonitoringComing soon
BoxFilesComing soon
DropboxFilesComing soon
EgnyteFilesComing soon
DocusignBusiness appsComing soon
SalesforceBusiness appsComing soon
SnowflakeBusiness appsComing soon
Cursor and VS CodeCodingComing soon

Which assistants use which tool#

Every connected tool is shared with your team, so the CEO assistant knows what is connected when it briefs an assistant. Each assistant then uses the tools that fit its job. Today the Coder is the assistant that is available, so source control is where integrations matter first. The other assistants arrive with the tools that suit them, such as mail for the Accountant and Legal.

An assistant never pretends a tool is connected. If you have not connected it, the assistant leaves it out and tells you.

Preflight checklist#

Before you connect a tool:

  • You can create an access token in that tool.
  • You know the smallest set of repositories, folders, or projects the assistant should see.
  • You have decided what your house rules allow without asking.

Staying in control#

  • Connect with the least access that works. You can always make a token wider later.
  • Disconnect at any time. Revoke the token in the tool itself and the assistant loses access straight away.
  • Check what happened. Jobs and Approvals keep a record of what each assistant did with each tool. See the activity log.

Prompt#

PromptCheck what is connected

CEO, which of my integrations are connected, and which assistant would use each one? Tell me what you would not be able to do without the ones that are missing.