Streak
CRMConnect AI agents to Streak, the CRM built into Gmail. Agents create and advance boxes through pipeline stages, set custom field values, log comments, read email threads, and search across records to keep deals moving.
What This Integration Enables
Streak's wager is that the CRM fails not because of features but because of the tab switch: reps live in Gmail, so the pipeline should too. This connector extends that wager to your automation. FlowRunner agents create and advance boxes through pipeline stages, write custom field values in the format each field type expects, log comments teammates read inside their inbox, list the email threads linked to a record, and search across boxes when all you have is a name. Agents can even provision entire pipelines with predefined stages and fields as part of an onboarding flow. What that buys an operations leader is a pipeline that reflects reality without depending on rep discipline. The systems where events actually happen, storefront, calendar, billing, write to the record directly, and the humans spend their attention on the one thing agents route to them: the [human-in-the-loop](/concepts/human-in-the-loop) decisions that move revenue.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Orders that file themselves into the pipeline
A [Shopify](/integrations/shopify) order fires. The agent runs Search Boxes for the customer, updates the existing deal or creates a fresh box with Create Box, writes the order total through Set Box Field Value using the field key from List Fields, and logs the line items as a comment. The rep sees the deal move in Gmail before the fulfillment email arrives. No order is ever re-keyed, and no deal value is a week stale.
Meetings become boxes before they happen
When an invitee books through the scheduling tool, the agent opens a box in the sales pipeline with Create Box, sets the assignee from the booking's routing, and adds a comment with the meeting time and the prospect's answers. Because Streak lives in Gmail, the rep preparing for the call sees the box, the comment, and, via List Threads, every prior email exchange with that address in one place. First-call context stops depending on memory.
The live pipeline report and the provisioning flow
On a schedule, List Boxes In Pipeline pulls every deal with its stage and field values, writes the snapshot to [Google Sheets](/integrations/google-sheets), and posts stage-by-stage totals to [Slack](/integrations/slack). When a new sales pod spins up, the same connector provisions their workspace: Create Pipeline with the standard stages and custom fields, shared to the right team from List Teams. Every pod starts with the same structure, so the roll-up report never has to reconcile five homemade pipelines.
Human-in-Loop Highlight
Delete Pipeline is the most destructive call in this connector: it permanently removes the pipeline and every box, stage, and field definition inside it, which means one wrong key deletes not a record but an entire book of business, comments and field history included. Delete Box does the same to a single deal. Neither can be undone. So consolidation and cleanup flows in FlowRunner never execute these on their own judgment. When two pods merge and their pipelines need collapsing, the agent migrates the boxes, then presents the empty source pipeline with its box count, zero, verified by List Boxes In Pipeline, and waits. The sales ops lead confirms the kill, and only then does Delete Pipeline run. The migration is automated; the deletion of a container that held revenue history is a signature.
Agent Capabilities
19 actionsPipelines
5- List Pipelines Lists every pipeline the user can access. The top-level map of workflows, stages, and fields.
- Get Pipeline Retrieves a pipeline's name, stage order, custom field definitions, and sharing settings. The structure read before any write.
- Create Pipeline Creates a pipeline with stages and custom fields in one call, personal or shared with a team. The provisioning step for new pods and processes.
- Update Pipeline Updates a pipeline's name, description, or stage order. Only provided fields change.
- Delete Pipeline Permanently deletes a pipeline with all its boxes, stages, and fields. The operation this page's human gate exists for.
Boxes
5- List Boxes In Pipeline Lists every box in a pipeline with stage, assignees, and field values. The read behind pipeline reports and verification checks.
- Get Box Retrieves one box's full state: stage, notes, assignees, linked contacts, and custom fields.
- Create Box Creates a record in a pipeline with a name, optional initial stage, notes, and assignees. The entry point for new deals.
- Update Box Updates a box's name, notes, or stage. Moving the stage is how agents advance a deal once a person says go.
- Delete Box Permanently deletes a box with its notes, field values, and comments. Cannot be undone; runs only with review.
Stages and Fields
3- List Stages Lists a pipeline's stages with their keys. The vocabulary for creating and moving boxes.
- List Fields Lists custom field definitions with key, name, and type. Read before writing so values match the field's format.
- Set Box Field Value Sets a custom field on a box, with value formats per type: strings, Unix millisecond dates, booleans, or option keys. The step that keeps deal data current.
Comments and Threads
3- List Comments Lists a box's comments in order with author and timestamp. The record of who said what about the deal.
- Create Comment Adds a comment to a box. How agents leave context where the team actually reads it.
- List Threads Lists the Gmail threads linked to a box with subject and participants. The bridge between the record and the actual conversation.
Account
2- Get Current User Returns the authenticated user's profile and key. Used to verify credentials at flow start.
- List Teams Lists the user's teams. The key needed when provisioning shared pipelines.
Search
1- Search Boxes Free-text search across boxes, contacts, and organizations. How an agent finds the deal when all it has is a customer name.
Frequently Asked Questions
What can FlowRunner do with Streak?
FlowRunner agents can run List Pipelines, Get Pipeline, and Create Pipeline in Streak, plus 16 more actions.
Does connecting Streak to FlowRunner require OAuth?
No. Streak connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can Streak trigger a FlowRunner workflow automatically?
Streak doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Streak
$100 in credits. No card required. Connect in minutes.