Only trigger when a Task is due on a Box in this Pipeline.

The box this organization will belong to.

The name of the organization.

Organization's website.

Either the name of the box to edit (case sensitive), or the key of the box.

New name of the box (leave empty to not change).

Notes field on the Box (leave empty to not change).

Assign this to yourself or someone on your team. The assigned user will be need to have access to the pipeline.

If left blank, the assignee will not change.

This will attach the Gmail Thread to this box. Beware that this ID is scoped to a single users inbox and that user should be the same user using this action.

If set to Yes, we will create new tag and dropdown options based on the input given. These options will appear in your pipeline. If set to No, anything that does not match a current tag or dropdown option will be ignored and no new options will be created.

The key of the file you'd like to retrieve.

If box name is used, only update the box on this pipeline.

Box to link other boxes to. Either the name of the box (case sensitive) or the key.

A list of box names or keys to link to the first box.

The key of the contact you'd like to update.

First name of updated contact.

Last name of updated contact.

The only email addresses associated with the contact will be the ones you include here; make sure to include any previously associated addresses as well as the new one(s).

The title of the updated contact.

The Twitter handle of the updated contact.

The Facebook link of the updated contact.

The LinkedIn url for the updated contact.

A url for the photo of the updated contact.

The only phone numbers associated with the contact will be the ones you include here; make sure to include any previously associated numbers as well as the new one(s).

The only addresses associated with the contact will be the ones you include here; make sure to include any previously associated addresses as well as the new one(s).

Any other notes or information you'd like to include about the contact.

API docs for Streak are located here https://www.streak.com/api/

Requests can only be made to domains associated by this application.

These params will be URL-encoded and appended to the URL when making the request.

Authentication headers are included automatically

Zapier will apply these optional headers and values to the request in addition to any headers created as part of the authentication mechanism.

Zapier will pass this along raw. If you would like to provide complex JSON, try a "Code by Zapier" step to build the structure and pass it along here. For example, {"foo": "bar"} is perfectly valid.

If given a box key, this search will returns the first contact or the first starred contact from the specified box. If given a contact key, this search will return the details of the specified contact. You must provide either a key or a query; you can not provide both.

Your search query should be unique to the user -- email address, phone number, or street address are great options. You must provide either a key or a query; you can not provide both.

List of teams to search on. If no teams are specified, it will default to all teams. Only applicable for use with Search Queries.

Exact box name or key. You must provide either a key/name or a query; you can not provide both.

Not an exact search. Searches the contents of a box. You must provide either a key/name or a query; you can not provide both. Not for use with the create-if-not-existing option.

List of the pipelines to search on. If no pipelines are specified, it will default to all pipelines. Only applicable for a Search Query.

The pipeline this box is found under.

The name of the box.

Set this value to the email address you want to make the box automatically assigned to. If you leave this blank, then the assigned to gets set as the person who creates the box.

The box notes.

The Gmail thread ID. This will automatically create the box and add the specified Gmail thread to the newly created box. Beware that this ID is scoped to a single users inbox and that user should be the same user using this action.

Use the a standard format for a future date, like "2021-02-28" or "Feb 28, 2021".

The box the contact will be added to.

The email address(es) of a contact who will be added to the box.

The first name of a contact who will be added to the box.

Contact's position/title.

The last name of a contact who will be added to the box.

The phone number(s) associate with this contact.

Contact's Twitter handle.

Contact's Facebook page.

Contact's LinkedIn page.

Contact's address(es).

Notes specific to the contact.

The pipeline this box is found under.

The name of the box.

Assign this to yourself or someone on your team. The assigned user will be need to have access to the pipeline.

If left blank, this will be assigned to you.

The box notes.

The Gmail thread ID. This will automatically create the box and add the specified Gmail thread to the newly created box. Beware that this ID is scoped to a single users inbox and that user should be the same user using this action.

If set to Yes, we will create new tag and dropdown options based on the input given. These options will appear in your pipeline. If set to No, anything that does not match a current tag or dropdown option will be ignored and no new options will be created.

Assign this to yourself or someone on your team. The assigned user will be need to have access to the pipeline.

If left blank, the assignee will not change.

The box of the key you'd like to edit tasks on. You must also provide task text with this option, and may not provide a task key.

The text of the task you'd like to edit. Task text is case sensitive and must be used with a box key. Do not provide a task key.

The specific task key you'd like to update. Do not provide a box key or task text if you are providing a task key.

Leave blank to not change.

The thread key for the contents you'd like to retrieve.

A box key is its unique ID (not its name). You will likely need to get this key from a previous step.

Meeting or call?

Start time for the meeting or call.

End time for the meeting or call.

Meeting/Call Log Notes.

Determines which App Extensions will appear in the dropdown below.

Exact box name or key. You must provide either a key/name or a query; you can not provide both.

Not an exact search. Searches the contents of a box. You must provide either a key/name or a query; you can not provide both. Not for use with the create-if-not-existing option.

List of the pipelines to search on. If no pipelines are specified, it will default to all pipelines. Only applicable for a Search Query.

If given a box key, this search will returns the first organization or the first starred organization from the specified box. If given an organization key, this search will return the details of the specified organization. You must provide either a key or a query; you can not provide both.

Your search query should be unique to the organization – website, phone number, or street address are great options.

The team on which to search for the organization. If left blank, all teams will be searched.

List of the pipelines to search on. If no pipelines are specified, it will default to all pipelines.

Search for the contents of a box (not to be used with search by name or search and create).

The name of the box.

The pipeline this box is found under.

Set this value to the email address you want to make the box automatically assigned to. If you leave this blank, then the assigned to gets set as the person who creates the box.

The box notes.

The Gmail thread ID. This will automatically create the box and add the specified Gmail thread to the newly created box. Beware that this ID is scoped to a single users inbox and that user should be the same user using this action.

Use the a standard format, like "2021-02-28" or "Feb 28, 2021". You can record past absences or future planned leave.

Email address or full name of the team member associated with this activity. Must match what's in Status Hero.

A brief description of the activity. For example, Moved user story "Reporting" from "Doing" to "QA".

Source of the activity, most likely the application you're calling this action from. E.g., "Asana".

An external URL for the source of the activity.