Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Streak

CRM built into Gmail. Manage pipelines, boxes, tasks, comments, contacts and organizations from your flows.

CategorySales And Crm
Authenticationcustom
Version0.1.0
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect Streak with Flows360

CRM built into Gmail. Manage pipelines, boxes, tasks, comments, contacts and organizations from your flows.

Use the Streak connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 11 actions and 11 triggers.

Available actions

  • Create Box
  • Update Box
  • Get Box
  • Find Boxes
  • Create Stage
  • Create Task
  • Create Comment
  • Create or Find Contact
  • Plus 3 additional declared actions.

Available triggers

  • New Box
  • Updated Box
  • Box Stage Changed
  • Box Moved to Different Pipeline
  • New Comment
  • New Task
  • Plus 5 additional declared triggers.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Streak
  • Package: @activepieces/piece-streak@0.1.0
  • Exact artifact digest: sha256:42390d826763ee9ce105ed4b45e0007c874c6bd3edd8c78ab4bc68c2e84d27f6
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Box (create_box), Create a new box (record) in a pipeline. Classification: read.
  • Update Box (update_box), Update the name, notes, stage, assignees, or custom fields on an existing box. Classification: read.
  • Get Box (get_box), Fetch a single box with its current stage, fields, and counts. Classification: read.
  • Find Boxes (find_box), Search boxes by name or query. Returns matching boxes across all pipelines, optionally filtered to one pipeline. Classification: read.
  • Create Stage (create_stage), Add a new stage (column) to a pipeline. Classification: read.
  • Create Task (create_task), Create a new task on a box. Classification: read.
  • Create Comment (create_comment), Add a comment to a box. Classification: read.
  • Create or Find Contact (create_contact), Create a contact in a team. If a contact with the same email already exists, return that contact instead of creating a duplicate. Classification: read.
  • Create or Find Organization (create_organization), Create an organization in a team. If an organization with the same domain already exists, return that organization instead of creating a duplicate. Classification: read.
  • Get Current User (get_current_user), Get the Streak user associated with the connected API key. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Box, webhook.
  • Updated Box, webhook.
  • Box Stage Changed, webhook.
  • Box Moved to Different Pipeline, webhook.
  • New Comment, webhook.
  • New Task, webhook.
  • Task Completed, webhook.
  • Task Due, webhook.
  • New Meeting or Call Log, webhook.
  • New Contact, webhook.
  • Updated Contact, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects22
Supported actionsNot published
Triggers11

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create Box Yes No Create a new box (record) in a pipeline.
Update Box Yes No Update the name, notes, stage, assignees, or custom fields on an existing box.
Get Box Yes No Fetch a single box with its current stage, fields, and counts.
Find Boxes Yes No Search boxes by name or query. Returns matching boxes across all pipelines, optionally filtered to one pipeline.
Create Stage Yes No Add a new stage (column) to a pipeline.
Create Task Yes No Create a new task on a box.
Create Comment Yes No Add a comment to a box.
Create or Find Contact Yes No Create a contact in a team. If a contact with the same email already exists, return that contact instead of creating a duplicate.
Create or Find Organization Yes No Create an organization in a team. If an organization with the same domain already exists, return that organization instead of creating a duplicate.
Get Current User Yes No Get the Streak user associated with the connected API key.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Box Yes No webhook trigger declared by the pinned package.
Updated Box Yes No webhook trigger declared by the pinned package.
Box Stage Changed Yes No webhook trigger declared by the pinned package.
Box Moved to Different Pipeline Yes No webhook trigger declared by the pinned package.
New Comment Yes No webhook trigger declared by the pinned package.
New Task Yes No webhook trigger declared by the pinned package.
Task Completed Yes No webhook trigger declared by the pinned package.
Task Due Yes No webhook trigger declared by the pinned package.
New Meeting or Call Log Yes No webhook trigger declared by the pinned package.
New Contact Yes No webhook trigger declared by the pinned package.
Updated Contact Yes No webhook trigger declared by the pinned package.

Triggers

New Box · Webhook

Triggers when a new box is created in the selected pipeline.

Inputs

  • pipelineKey · string
Updated Box · Webhook

Triggers when a field on a box is updated in the selected pipeline.

Inputs

  • pipelineKey · string
Box Stage Changed · Webhook

Triggers when a box moves between stages in the selected pipeline.

Inputs

  • pipelineKey · string
Box Moved to Different Pipeline · Webhook

Triggers when a box is moved out of (or into) the selected pipeline.

Inputs

  • pipelineKey · string
New Comment · Webhook

Triggers when a comment is added to a box in the selected pipeline.

Inputs

  • pipelineKey · string
New Task · Webhook

Triggers when a task is created on a box in the selected pipeline.

Inputs

  • pipelineKey · string
Task Completed · Webhook

Triggers when a task on a box in the selected pipeline is marked complete.

Inputs

  • pipelineKey · string
Task Due · Webhook

Triggers when a task becomes due (but has not yet been completed) on a box in the selected pipeline.

Inputs

  • pipelineKey · string
New Meeting or Call Log · Webhook

Triggers when a meeting note or call log is created on a box in the selected pipeline.

Inputs

  • pipelineKey · string
New Contact · Webhook

Triggers when a new contact is created in the selected team.

Inputs

  • teamKey · string
Updated Contact · Webhook

Triggers when a contact in the selected team is updated.

Inputs

  • teamKey · string

Setup

Setup

  1. Add the Streak connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-streak@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 11 actions and 11 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Streak connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-streak@0.1.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com