Resources · Make integration

Streak Make integrationAutomate Streak with Make.

Can Make keep your Streak pipelines moving while you stay in Gmail? The Streak Make integration gives you 56 modules, including 6 instant triggers. This guide is for sales and ops people new to Make: connect your account, build a first scenario, then pick the right module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Streak Make integration do for you?

The Streak Make integration links your Streak account to Make, a tool where you build a scenario: an automation made of modules, each one a brick that watches, creates, reads or deletes something. Streak tells Make the moment a box, contact or task changes, and your scenario reacts without anyone copying data by hand.

Follow-ups that write themselves. Watch Comments notices a new comment on a box, and Create a Task adds the next action for the right teammate. Nobody has to remember to turn a remark into a to-do.

A clean contact base. When a lead fills a form in another app, Search Boxes/Organizations/Contacts checks whether the person already exists, then Create a Contact or Update a Contact does the rest and Add Contacts To a Box ties them to the deal.

Emails filed where they belong. Put an Email in a Box attaches a Gmail thread to a box, and Get a Thread pulls its details for a summary elsewhere. Keep in mind that a thread lives in one box only: sending it to a second box fails.

The Streak documentation lists no further limit for these modules, so the constraints you will meet are Make's own plan rules. If a module is missing, Make an API Call reaches the rest of the Streak API with the same connection. Still hesitating between tools? The n8n vs Make comparison sets out the criteria, and the Make pricing page explains how operations are counted. Teams that prefer to learn step by step can start with Make training.

Connect

How do you connect Streak to Make?

  1. 01

    Copy your Streak API key

    Open Gmail and click the Streak icon in the right sidebar. Choose Integrations, find the Streak API section, click Create New Key and copy the key shown on screen. You need an active Streak account for this.

  2. 02

    Add a Streak module in Make

    In your scenario, add any Streak module and click Create a connection. The connection is your Streak account linked to Make once, then reused by every Streak module. You can give it a name in Connection name, which helps if you run several accounts.

  3. 03

    Paste the key and save

    Paste the API key you copied into the credentials field and confirm. Make checks it and the module now lists your pipelines and boxes, so you pick them from a menu instead of typing IDs.

First scenario

Your first scenario: turn a Streak comment into a task

GoalWhen someone comments on a box in Streak, Make creates a follow-up task on that same box.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. That empty circle becomes your first module, the one that starts everything.

  2. 02

    Add Watch Comments

    Search for Streak, pick Watch Comments, click Create a webhook, then Create a connection and paste your API key. Streak can now call Make whenever a comment event happens.

  3. 03

    Add Create a Task

    Click the + on the right of the trigger and choose Streak Create a Task. Pick the box, write the task and map values from the trigger's bundle, the item it received, then choose an assignee.

  4. 04

    Test with Run once

    Click Run once, then post a comment on a test box in Streak. Read the bundles each module received and check the task appeared.

  5. 05

    Switch the scenario on

    Save and turn the scenario on. Because the trigger is instant, Streak calls Make each time a comment is added, and each module run counts as one operation on your plan.

Triggers

Streak triggers: what starts your scenario

6 modules start a scenario when something happens in Streak. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Streak as soon as it happens.

Streak1Watch Boxes

Watch Boxes

Instant trigger

In MakeTriggers when a new event regarding boxes is occured.

Watch Boxes starts your scenario whenever something happens to a box, the record Streak keeps inside a pipeline. Each event reaches Make as a bundle, a single item handed to the next module, so you can map its details straight away.

How it fires
instant: Streak calls Make through a webhook as soon as the event happens, with no polling interval to choose.
When to use it
when the box itself is what you track, for example to copy each deal change into a reporting sheet.
Watch out
click Create a webhook before Create a connection, in that order.
Streak2Watch Comments

Watch Comments

Instant trigger

In MakeTriggers when a new event regarding comments is occured.

Comments are where teammates leave the small facts that matter, and this trigger passes each comment event to Make the moment it exists. You get one bundle per event, ready to feed a task, a message or a log.

How it fires
instant: Streak calls Make through a webhook as soon as the event happens.
When to use it
to alert a manager in chat when a colleague writes on a sensitive deal.
Watch out
avoid adding Create a Comment later in the same scenario, or each run could post a comment that starts the scenario again.
Streak3Watch Contacts

Watch Contacts

Instant trigger

In MakeTriggers when a new event regarding contacts is occured.

Your contact list can stay in sync with other tools thanks to Watch Contacts, which reports every contact event from Streak to Make. The contact arrives as a bundle you can send to a newsletter tool, a sheet or a second CRM.

How it fires
instant: Streak calls Make through a webhook as soon as the event happens.
When to use it
when marketing needs each new Streak contact in its mailing tool without an export.
Watch out
if the same scenario runs Update a Contact, that change could come back as a new event, so add a filter before it.
Streak4Watch Organizations

Watch Organizations

Instant trigger

In MakeTriggers when a new event regarding organizations is occured.

Companies matter as much as people in B2B sales, and Watch Organizations lets Make react to every organization event in Streak. Each one flows on as a bundle, so the account record can be copied or enriched elsewhere.

How it fires
instant: Streak calls Make through a webhook as soon as the event happens.
When to use it
to mirror each account created by sales into the tool your finance team uses for billing.
Watch out
if the same scenario also runs Update an Organization, that change could come back as a new event, so add a filter before it.
Streak5Watch Stages

Watch Stages

Instant trigger

In MakeTriggers when a new event regarding stages is occured.

Stages are the columns of a Streak pipeline, and this trigger tells Make when an event touches one of them. It suits people who maintain the pipeline structure rather than the deals inside it.

How it fires
instant: Streak calls Make through a webhook as soon as the event happens.
When to use it
to keep a shared process document or a dashboard aligned with the stages your pipeline actually uses.
Watch out
a stage can only be deleted when no box still sits in it, which explains a Delete a Stage that fails right after this trigger.
Streak6Watch Tasks

Watch Tasks

Instant trigger

In MakeTriggers when a new event regarding tasks is occured.

Watch Tasks gives Make a signal for each task event in Streak, so a to-do set in Gmail can travel to the tool where your team actually plans its day. The task arrives as a bundle with its content ready to map.

How it fires
instant: Streak calls Make through a webhook as soon as the event happens.
When to use it
to copy Streak tasks into a project board or a calendar used by people who never open the CRM.
Watch out
creating tasks in the same scenario can restart it, so keep Create a Task in a separate one.
Modules

Streak modules in Make: what each one does

Streak gives you 50 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Streak1

Add Contacts To a Box

Action

In MakeAdds selected contacts to a box.

Linking people to a deal is what this action does: it attaches one or more existing contacts to a box, so the whole buying group shows up on the record.

When to use it
right after Create a Contact, when a new lead writes in and must join the deal their colleague opened.
Watch out
the contacts must already exist in Streak, so create or find them first.
Streak2

Add Organizations to a Box

Action

In MakeAdds selected organizations to a box.

With this module a box gains the company behind it: you attach one or several organizations, and anyone opening the deal sees which account it belongs to.

When to use it
after a form reveals the prospect's company and you want the box tied to the right account.
Watch out
pair it with Search Boxes/Organizations/Contacts so you link an existing organization instead of a duplicate.
Streak3

Create a Box

Action

In MakeCreates a new box inside a selected pipeline.

A new deal, candidate or case appears in your pipeline without anyone typing it: Create a Box adds a fresh box inside the pipeline you select.

When to use it
when a quote request lands in another app and sales should see it in Streak at once.
Watch out
run a search before it if the same request can arrive twice, or you will get twin boxes.
Streak4

Create a Comment

Action

In MakeCreates a new comment for a selected box.

You leave a written trace on a box from outside Streak: this action posts a comment on the box you pick, visible to everyone who follows the deal.

When to use it
to log that an invoice was paid or a contract signed in another tool, right on the deal.
Watch out
never place it in a scenario started by Watch Comments, or it may keep triggering itself.
Streak5

Create a Contact

Action

In MakeCreates a new contact.

Each new person you meet can land in Streak as a contact, created by Make from the data of another app, with no copy and paste.

When to use it
when a webinar sign-up or a form entry should become a Streak contact before sales calls back.
Watch out
it always creates, it never merges, so check with Search Boxes/Organizations/Contacts whether the person already exists.
Streak6

Create a Field

Action

In MakeCreates a new field for a selected pipeline.

Pipeline columns can be added by a scenario: Create a Field adds a new field to the pipeline you choose, ready to hold a value on every box.

When to use it
when you set up several similar pipelines and want the same custom fields on each without clicking through settings.
Watch out
this changes the structure your whole team sees, so test it on a sandbox pipeline first.
Streak7

Create an Organization

Action

In MakeCreates a new organization.

Accounts get their own record thanks to this action, which creates a new organization in Streak from whatever data the previous module passes along.

When to use it
when a signed contract in your e-signature tool should give the client company a home in the CRM.
Watch out
like any create module, it does not check for duplicates, so search for the name first.
Streak8

Create a Pipeline

Action

In MakeCreates a new pipeline.

An entire process can be spun up from Make: Create a Pipeline builds a new pipeline, the board that will then receive its stages, fields and boxes.

When to use it
for agencies that open one pipeline per new client project and want the setup repeated identically.
Watch out
the pipeline starts empty, so chain Create a Stage and Create a Field right after it.
Streak9

Create a Stage

Action

In MakeCreates a new stage for a selected pipeline.

Stages give a pipeline its steps, and this module adds one to the pipeline you select, so boxes can move through it.

When to use it
just after Create a Pipeline, to lay out columns such as lead, proposal and won in one go.
Watch out
a scenario that runs twice adds the same stage twice, so guard it with a filter.
Streak10

Create a Task

Action

In MakeCreates a new task for a selected box. The task assignees must have access to the containing pipeline.

Reminders stop living in people's heads: Create a Task attaches a to-do to a chosen box and can assign it to a teammate.

When to use it
when a new comment, email or stage change calls for a clear next step on the deal.
Watch out
every assignee needs access to the pipeline that holds the box.
Streak11

Delete a Box

Action

In MakeDeletes a selected box.

Clutter leaves the pipeline for good with this action, which removes the box you point it to.

When to use it
to clear test boxes or spam leads once another module has confirmed they are junk.
Watch out
a deleted box does not come back from Make, so put a filter in front and test with Run once on a dummy box before you switch the scenario on.
Streak12

Delete a Comment

Action

In MakeDeletes a selected comment.

Removing a comment from a box is all this module does, which is handy when an automated note turned out to be wrong.

When to use it
to clean up comments your own scenario posted during a faulty run.
Watch out
you need the comment's identity, so run List Comments first and filter the bundles to the one you mean before deleting anything.
Streak13

Delete a Contact

Action

In MakeDeletes a selected contact.

This action erases a contact from Streak, the step you reach for when a person must disappear from your CRM.

When to use it
when someone asks to be forgotten and your process removes them across every tool at once.
Watch out
the deletion is final from the scenario's side, so confirm the right contact with Get a Contact before this module runs.
Streak14

Delete a Field

Action

In MakeDeletes a selected field and removes the values of this field for every box in the pipeline.

A pipeline field you no longer use can be dropped by Make, keeping the box view short and readable for the team.

When to use it
when you retire an old custom column across several cloned pipelines.
Watch out
removing the field also wipes its values on every box of the pipeline, so export them with List Field Values first if they still matter.
Streak15

Delete an Organization

Action

In MakeDeletes a selected organization.

Old or duplicated company records go away through this module, which deletes the organization you select in Streak.

When to use it
after a merge in your source system, to remove the account that no longer exists.
Watch out
check the organization with Get an Organization before this step, because a wrong mapping would erase the wrong account.
Streak16

Delete a Pipeline

Action

In MakeDeletes a selected pipeline.

The heaviest cleanup tool in the list: Delete a Pipeline removes a whole pipeline you name from your Streak account.

When to use it
to close a temporary project pipeline that a scenario created for a one-off campaign.
Watch out
treat it with care, map the pipeline explicitly rather than from a search, and test on a throwaway pipeline before activating anything.
Streak17

Delete a Stage

Action

In MakeDeletes a selected stage. This call will only succeed if there are no boxes tagged with the key of the selected stage.

Removing a column from a pipeline keeps your process lean, and this module deletes the stage you pick.

When to use it
when a step of your sales process disappears and the stage no longer has a purpose.
Watch out
Streak refuses the deletion while any box is still tagged with that stage, so move those boxes with Update a Box first.
Streak18

Delete a Task

Action

In MakeDeletes a selected task.

Tasks that lost their reason to exist can be removed by Make, which keeps each teammate's list honest.

When to use it
when a deal is lost and the follow-up reminders attached to it should vanish too.
Watch out
list the box's tasks with List Tasks or read one with Get a Task first, so the scenario deletes the right reminder and not a live one.
Streak19

Get a Box

Action

In MakeRetrieves details for a selected box.

Everything Streak knows about one box comes back as a bundle with this module, ready to map into a message, a document or another app.

When to use it
when a trigger from another tool gives you a box reference and you need its full details before acting.
Watch out
it reads one box you already identify; to find boxes by name, use Search Boxes/Organizations/Contacts instead.
Streak20

Get a Comment

Action

In MakeRetrieves details for a selected comment.

This read-only module fetches the details of a single comment, which lets you reuse its text somewhere else without opening Streak.

When to use it
to quote a colleague's comment in a client update written in another app.
Watch out
you must point it to one comment; for all comments on a box, List Comments returns them as separate bundles.
Streak21

Get a Contact

Action

In MakeRetrieves details for a selected contact.

Pulling one contact's full record into your scenario is the job here, so later modules can use the name, email or other details Streak stores.

When to use it
before sending a personalised email from another tool to a person linked to a deal.
Watch out
it needs the contact already identified; if you only know an email or a name, search first.
Streak22

Get a Field

Action

In MakeRetrieves details for a selected field.

You learn how a pipeline field is defined with this module, which returns its details rather than the values stored on boxes.

When to use it
when a scenario must check a field's setup before it writes into it on many boxes.
Watch out
the values themselves come from List Field Values, not from this module, which only describes the field.
Streak23

Get a File

Action

In MakeRetrieves details for a file by ID.

File details reach your scenario through Get a File, which looks up one file by its ID and returns what Streak holds about it.

When to use it
after List Files on a box, to read the details of the proposal or contract you want to route onward.
Watch out
on the Free plan, Make handles files up to 5 MB, a limit to keep in mind before you route a heavy attachment.
Streak24

Get an Organization

Action

In MakeRetrieves details for a selected organization.

Company data you already stored in Streak comes back through this module, as one bundle describing the organization you pick.

When to use it
to add the client's account details to an invoice or a contract generated in another app.
Watch out
it retrieves a known organization; to look one up by name, start with Search Boxes/Organizations/Contacts.
Streak25

Get a Pipeline

Action

In MakeLists a selected pipeline's details.

A pipeline's setup, as Streak describes it, lands in your scenario through Get a Pipeline, so you can read its details before touching it.

When to use it
when a scenario copies one pipeline's structure to build another, or documents your process somewhere.
Watch out
it describes the pipeline itself; the boxes inside come from List Boxes.
Streak26

Get a Stage

Action

In MakeRetrieves details for a selected stage.

Reading one stage gives your scenario its name and details, useful for writing human-friendly messages instead of raw keys.

When to use it
to add a stage's readable name to an alert you post in your team chat.
Watch out
each call costs an operation, so avoid running it on every box if List Stages can fetch them once.
Streak27

Get a Task

Action

In MakeRetrieves details for a selected task.

This module returns one task with its details, handy when a scenario must decide what to do with a specific reminder.

When to use it
after Watch Tasks, to check a task's current content before copying it to a project board.
Watch out
it works on one task; to see everything open on a box, List Tasks is the right choice.
Streak28

Get a Thread

Action

In MakeRetrieves details for a selected email thread.

Email threads are where Streak shines, and Get a Thread brings one of them into Make with its details, ready for a summary or an archive.

When to use it
when a deal closes and you want the key email conversation saved in a shared drive or a client file.
Watch out
you need the thread identified, usually from List Threads on the box first.
Streak29

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Anything the listed modules leave out can still be reached: Make an API Call sends your own request to any endpoint of the Streak API, reusing the connection you already set.

When to use it
when a Streak feature has no dedicated module and you know which endpoint serves it.
Watch out
you write the request yourself, so keep the Streak API documentation open next to the module.
Streak30

Put an Email in a Box

Action

In MakeMakes an email thread a part of a selected box. A thread can only be part of a single box at any one time. Trying to add it to a second box will result in an error.

Attaching a Gmail thread to a deal is the core Streak gesture, and this module does it for you: the thread becomes part of the box you choose.

When to use it
when an email from a known client should be filed on their open deal without anyone dragging it.
Watch out
a thread can belong to one box only, and trying to add it to a second box ends in an error.
Streak31

Update a Box

Action

In MakeUpdates a selected box.

Keeping a deal current is this module's role: it changes the box you select, for instance to reflect news that arrived in another app.

When to use it
when a payment tool confirms a deposit and the box should move forward in the pipeline.
Watch out
map the box from a trusted source, then test with Run once on a test box and compare it before and after.
Streak32

Update a Comment

Action

In MakeUpdates a selected comment for a box.

A comment already posted on a box can be corrected by Make, so an automated note stays accurate when the facts change.

When to use it
to refresh a status line your scenario wrote earlier, such as a delivery date that moved.
Watch out
keep track of which comment the scenario owns, for example by listing the box's comments and filtering on its text.
Streak33

Update a Contact

Action

In MakeUpdates a selected contact. For any field on a contact that is a list, only the values you put into the array will appear for that contact; calls are not aware of previous values and will not keep them.

Contact details drift, and this action rewrites the contact you pick with fresher data from another source.

When to use it
when a customer changes job or phone in your support tool and Streak should follow.
Watch out
for list fields, only the values you send are kept and earlier ones are dropped, so fetch them with Get a Contact and send the full list.
Streak34

Update a Field

Action

In MakeUpdates a selected field.

Changing how a pipeline field is set up, not what it contains, is what Update a Field handles, directly from your scenario.

When to use it
when you rename a custom column across several pipelines built from the same model.
Watch out
every box of the pipeline shows the change, so try it on a test pipeline before running it on live ones.
Streak35

Update an Organization

Action

In MakeUpdates a selected organization. For any field on an organization that is a list, only the values you put into the array will appear for that organization; calls are not aware of previous values and will not keep them.

Company records stay current thanks to this module, which edits the organization you select with new data.

When to use it
when your billing or enrichment tool learns something new about an account.
Watch out
list fields are replaced, not merged, so read the current values with Get an Organization and send the complete list back.
Streak36

Update a Pipeline

Action

In MakeUpdates a selected pipeline.

This action edits an existing pipeline, the board itself rather than the deals it carries, from inside a scenario.

When to use it
when a project changes name or scope in your project tool and its Streak pipeline should reflect it.
Watch out
map the pipeline explicitly, since a wrong reference would change a board your whole team uses.
Streak37

Update a Stage

Action

In MakeUpdates a selected stage.

Stage settings can change without anyone opening the pipeline menu: Update a Stage edits the stage you pick.

When to use it
to keep stage names aligned across several pipelines when your process vocabulary changes.
Watch out
boxes stay where they are, only the stage changes, so check that reports built on the old name still work.
Streak38

Update a Task

Action

In MakeUpdates a selected task.

A task can be edited on the fly by Make, for example to change its text or its assignee as the deal evolves.

When to use it
when a task is marked done in your project tool and the Streak copy should match.
Watch out
a new assignee still needs access to the pipeline that holds the box.
Streak39

List Boxes

Search

In MakeLists all boxes in a selected pipeline.

This search returns every box of a pipeline, each as its own bundle, so later modules can process them one by one.

When to use it
to export a pipeline into a spreadsheet or run a bulk update after a process change.
Watch out
a large pipeline means many bundles and many operations downstream, so filter early to keep your plan usage in check.
Streak40

List Comments

Search

In MakeLists all comments for a selected box.

The full conversation on a box comes back with List Comments, one bundle per comment, which you can gather into a single text for a recap.

When to use it
to prepare a handover when a deal moves from one salesperson to another.
Watch out
a box without comments returns zero bundles, so the rest of the scenario simply does not run for it.
Streak41

List Contacts

Search

In MakeLists all contacts for a selected team.

This search pulls every contact of the Streak team you pick into Make, one bundle per person. It is the quickest way to move a whole address book out of the CRM.

When to use it
when your mailing tool should start from the same contact base as your sales team.
Watch out
every module placed after it runs once per contact, and Make counts each of those runs as an operation on your plan.
Streak42

List Fields

Search

In MakeLists all fields in a selected pipeline.

With List Fields, your scenario knows which fields a pipeline defines before it writes anything. You read the structure of the pipeline here, not the data inside the boxes.

When to use it
when a teammate added columns to the pipeline and you want to check what the scenario can now fill.
Watch out
it returns field definitions only; to read what a given box holds in those columns, pick List Field Values.
Streak43

List Field Values

Search

In MakeLists values of custom fields for a selected box.

The custom field values stored on one box leave Streak through this module, which hands them to the next one. The figures and labels your team keeps in pipeline columns become usable elsewhere.

When to use it
right after Watch Boxes fires, to copy the values of the changed box into a reporting sheet.
Watch out
it reads one box at a time, so the scenario must already know which box, either from a trigger or from List Boxes.
Streak44

List Files

Search

In MakeLists all the files associated with a particular box.

Every file attached to one box comes back with List Files, each as its own bundle, so you see what a deal holds without digging through the inbox.

When to use it
when a box moves to a new stage and the people following the deal want its attachments listed in a shared sheet.
Watch out
this search lists what is there; when you already hold the ID of one file, Get a File reads its details directly.
Streak45

List Organizations

Search

In MakeLists all organizations for a selected team.

This search returns the organizations of the Streak team you select, each company as a separate bundle. Useful when the accounts you sell to have to exist in another tool as well.

When to use it
when your accounting app or a spreadsheet should use the same company names as Streak.
Watch out
a search can come back with zero bundles, so click Run once on a team that really holds organizations before you trust the result.
Streak46

List Pipelines

Search

In MakeLists all pipelines.

A sales pipeline next to a hiring one: List Pipelines returns every pipeline your Streak account can reach and passes each on as a bundle. It is the starting point for a scenario that works across all your pipelines.

When to use it
when you build an overview sheet with one row per pipeline, or check which pipelines exist before Create a Box writes into one.
Watch out
every pipeline comes out; when you only care about one you already know, Get a Pipeline targets it directly.
Streak47

List Stages

Search

In MakeLists all stages in a selected pipeline.

Stages are how Streak shows where a box stands. List Stages reads the stages of one pipeline, one bundle each, and gives your scenario the map of that progress.

When to use it
before a report that groups boxes by stage and needs the stage names first.
Watch out
Delete a Stage only succeeds when no box is tagged with that stage, so list the stages and check their boxes with List Boxes before any cleanup.
Streak48

List Tasks

Search

In MakeLists all tasks for a selected box.

The follow-ups your team keeps in Streak can reach your other tools through this search, which brings back the tasks of one box, one bundle per task.

When to use it
when Watch Boxes reports a change on a deal and you want its to-dos copied into a team chat or a project board.
Watch out
it covers a single box; to reach tasks across a whole pipeline, start with List Boxes and run this search on each box it returns.
Streak49

List Threads

Search

In MakeLists all email threads associated with a selected box.

The email history of a deal becomes data a scenario can work with: List Threads retrieves the threads filed in one box, one bundle per conversation.

When to use it
when a box reaches a new stage and the account manager wants its conversations logged in a sheet.
Watch out
a thread belongs to one box at a time in Streak, so it will not also appear under a second box; Get a Thread then reads one conversation in detail.
Streak50

Search Boxes/Organizations/Contacts

Search

In MakeSearches for boxes, Organizations or Contacts by query in a pipeline

Before you create anything, this search checks whether the record is already in Streak. It looks up boxes, organizations or contacts that match a query inside a pipeline.

When to use it
when a lead comes in from a form: you search Streak for the name and only go on to Create a Box when nothing comes back.
Watch out
it can return zero, one or several bundles; click Run once with a known name, then an unknown one, and compare what reaches the next module.
Need help

Need help automating Streak with Make?

A person reads every message.

FAQ

Streak and Make: common questions

01Is the Streak Make integration free?
Yes, on Make's side. Streak is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans remove the scenario cap, allow a 1 minute interval and runs of up to 40 minutes. Usage is counted in operations, one per module run. You still need an active Streak account, and Streak's own subscription is listed on its pricing page.
02What do you need to connect Streak to Make?
An active Streak account and a Streak API key. To get the key, open Gmail, click the Streak icon in the right sidebar, choose Integrations, find the Streak API section and click Create New Key, then copy it. In Make, add any Streak module, click Create a connection, optionally name it, and paste the key. For a trigger, click Create a webhook before Create a connection. The same connection then serves all 56 Streak modules.
03Do Streak triggers in Make fire in real time?
Yes. All 6 Streak triggers are instant: Streak calls Make through a webhook as soon as an event happens on a box, comment, contact, organization, stage or task. You do not wait for the 15 minute default schedule that applies to scheduled triggers. Each event arrives as a bundle, and every module that processes it uses one operation. On the Free plan, keep in mind that only 2 scenarios can be active at once, so choose the events that matter most.
04What if a Streak module you need is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Streak API with the connection you already created, so you can cover what the 56 listed modules leave out. You write the request yourself, which means reading the Streak API documentation for the endpoint you need. Also check the Streak rules built into existing modules: a thread fits in one box only, a stage with boxes cannot be deleted, and list fields on contacts are overwritten on update.
05Streak integration: Make or n8n?
It depends on the tool your team already uses and on what each one covers for your case. On Make, Streak comes with 56 modules, including 6 instant triggers, and Make an API Call for the rest. The same app often has an n8n node as well, so compare the actions it lists with the ones you need before choosing. Neither answer is right for everyone: start from the scenario you want to build and pick the tool that covers it.