Yes. 93 native integrations, and your session for everything else
A companion works the seams: the ticket that should become a Linear issue, the deal that should update the onboarding board, the four dashboards that should be one report.
Yes, in four tiers. Strawberry ships 93 native integrations carrying 1,257 hand-written operations, including Slack, Notion, Linear, Jira, Asana, Airtable, Gmail, Salesforce and GitHub, where a companion acts through the tool’s real API. Another 1,975 apps connect as accounts, with 11,417 actions between them. Anything in neither list is worked in the browser you are already signed into, and MCP covers products that ship their own AI-facing servers.
The value sits in the seams, because a companion holds all the tabs at once: read here, transform, write there, approval card, done. Reads flow freely, while consequential writes (the Slack message, the Jira transition, the record change) pause on approval cards, and Ask Always mode in Settings → AI permissions extends the pause to everything.
What cross-tool work does this open up?
The ferrying.
Most SaaS pain sits in the seams rather than inside any one tool: the support ticket that should become a Linear issue, the closed deal that should update the onboarding board, the standup notes that should land in the right channel, the numbers in four dashboards that should be one report.
A single vendor’s workflow builder never crosses its own walls. The browser is the one place all your tools already coexist, and job-shaped examples are collected in use cases.
What does a worked cross-tool run look like?
A quarterly access review, the task everyone defers.
The instruction: "list every user with access to our five core tools, flag people who left, and draft the removals." The companion opens each admin console in the session, two of which have no API worth the name, extracts the user lists into one sheet, and checks them against the team roster in the HR tool.
Four departed contractors turn up still holding seats. The sheet is the deliverable, and the de-provisioning clicks stay with a person. Ninety minutes of nobody-wants-to became ten minutes of review, over the same long tail of tools no connector catalog will ever reach.
Native, connected, or your session
Native integrations act through real APIs, so actions are exact (the right record, the right field) and the approval policy is enforced per tool in code. The CRM tier is detailed at how to automate CRM data entry, and the pattern holds across the catalog.
Session work is more universal and more like a careful person: it reads screens and clicks, and it benefits from spot checks. Check whether your core tools are among the 93 native or the 1,975 connectable, and treat the remainder as session territory. Pricing is flat and public at pricing; credits meter the work, not the number of tools.
What stays with a person
Granting access, changing billing, deleting a workspace.
A companion reads the user list, builds the sheet and drafts the removals, and the click that actually removes somebody is yours.
The approval model enforces the pause, and the fuller picture is on the security page.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents