Create a duplicate of an existing spreadsheet.

These Headers are ignored if a "Spreadsheet to Copy" is selected.

The Google Drive where your spreadsheet resides. If nothing is selected, then your personal Google Drive will be used. If you are connected with any Google Team Drives, you can select it here.

Use a search step before this to get the row to delete.

Determines which App Extensions will appear in the dropdown below.

The Google Drive where your spreadsheet resides. If nothing is selected, then your personal Google Drive will be used. If you are connected with any Google Team Drives, you can select it here.

You must have column headers. See here for more information.

Let us know which column you want to search by with the value below. We will grab the latest matching row and give you all of its values.

Optionally, specify another column you want to search by. Note that if you supply this, the Zap will trigger only on rows that match both columns. (An example column might be something like Email Address or Phone Number)

An example value might be me@example.com or 555-5555

Search from bottom of the sheet?

Number of rows to return. Max is 500.

The Google Drive where your spreadsheet resides. If nothing is selected, then your personal Google Drive will be used. If you are connected with any Google Team Drives, you can select it here.

You must have column headers. See here for more information.

Let us know which columns to return. e.g. A:Z

Number of rows to return. Max is 500.

Number of the first row to return (1 is the header)

The Google Drive where your spreadsheet resides. If nothing is selected, then your personal Google Drive will be used. If you are connected with any Google Team Drives, you can select it here.

Value of the Worksheet Title to match exactly. Search is case-sensitive.

If a worksheet with the specified title exists, its content would be lost. Please, use with caution.

If no, only messages sent by users will trigger the Zap. If yes, messages sent by users and slackbots will trigger the Zap.

Warning: Slackbots don't have profiles. If yes, don't depend on user profile information being present. Also, avoid Zap loops where Zaps trigger and post slackbot messages to the same channel!

Only channels you are a member of will appear in this list. If you can't find your channel, click the Load More button or switch to the Custom tab and enter the channel's ID. Once live, the trigger will work even if you are not a member of the channel. Note: This trigger only supports attachment information for messages generated by bots. If you need to retrieve attachment information from non-bots, see this help document.

If no, only messages sent by users will trigger the Zap. If yes, messages sent by users and slackbots will trigger the Zap.

Warning: Slackbots don't have profiles. If yes, don't depend on user profile information being present. Also, avoid Zap loops where Zaps trigger and post slackbot messages to the same channel!

Only channels you are a member of will appear in this list. If you can't find your channel, click the Load More button or switch to the Custom tab and enter the channel's ID. Once live, the trigger will work even if you are not a member of the channel.

Trigger on files created by a single user.

Trigger when files are shared with you. Please note that this will trigger on created files as well.

Only channels you are a member of will appear in this list. If you can't find your channel, click the Load More button or switch to the Custom tab and enter the channel's ID. Once live, the trigger will work even if you are not a member of the channel.

If no, only messages sent by users will trigger the Zap. If yes, messages sent by users and slackbots will trigger the Zap.

Warning: Slackbots don't have profiles. If yes, don't depend on user profile information being present. Also, avoid Zap loops where Zaps trigger and post slackbot messages to the same channel!

Only triggers when this reaction is added to a message. Use the dropdown to select one of your team's custom emoji or select Use a Custom Value and enter the name of a standard emoji. Use this cheat sheet for reference and be sure not to include the colons. Note that you cannot use an emoji's alias in this field.

Only triggers on reactions added on messages in this public channel. Only channels you are a member of will appear in this list. If you can't find your channel, click the Load More button or switch to the Custom tab and enter the channel's ID. Once live, the trigger will work even if you are not a member of the channel.

Only triggers on reactions added by this user.

Toggle to send to multiple users.

Specify text of the message to send. Check out the formatting help doc for advanced options.

If you choose no, this message will appear to come from you. Direct messages are always sent by bots.

Specify the bot name which appears as a bold username above the message inside Slack. Defaults to Zapier. When using Schedule At, this field will be ignored by slack.

Either an image url or an emoji available to your team (surrounded by :). For example, https://site.com/icon_256.png or :robot_face:. When using Schedule At, this field will be ignored by slack.

If you choose yes, a link to this Zap will be added to the end of the message, making it easy for you and your team to edit the Zap with one click.

If specified, this will upload the given image URL to Slack and attach it to the message separately.

Should Slack try to automatically expand links in this message? For example: turn a YouTube link into a playable widget.

If no, any usernames and channels mentioned won't be linked (or mentioned). Also affects @channel and @group. Unfortunately, @here notifications cannot be sent by Zapier.

Schedule the message to be posted later. Cannot be more than 120 days in the future. If you do schedule a message, rather than post it immediately, this Zap step will not return a ts or permalink field. This option does not support Bot Name and Bot Icon customization and will default to Zapier as bot name and icon.

Only channels you are a member of will appear in this list. If you can't find your channel, click the Load More button or switch to the Custom tab and enter the channel's ID. Once live, the trigger will work even if you are not a member of the channel.

Specify text of the message to send. Check out the formatting help doc for advanced options.

If you choose no, this message will appear to come from you. Direct messages are always sent by bots.

Specify the bot name which appears as a bold username above the message inside Slack. Defaults to Zapier. When using Schedule At, this field will be ignored by slack.

Either an image url or an emoji available to your team (surrounded by :). For example, https://site.com/icon_256.png or :robot_face:. When using Schedule At, this field will be ignored by slack.

If you choose yes, a link to this Zap will be added to the end of the message, making it easy for you and your team to edit the Zap with one click.

If specified, this will upload the given image URL to Slack and attach it to the message separately.

Should Slack try to automatically expand links in this message? For example: turn a YouTube link into a playable widget.

If no, any usernames and channels mentioned won't be linked (or mentioned). Also affects @channel and @group. Unfortunately, @here notifications cannot be sent by Zapier.

Schedule the message to be posted later. Cannot be more than 120 days in the future. If you do schedule a message, rather than post it immediately, this Zap step will not return a ts or permalink field. This option does not support Bot Name and Bot Icon customization and will default to Zapier as bot name and icon.

Include a file to send along with your message. NOTE: Bot names/icons cannot be customized when sending a File.

If you want this to be part of a thread, you'll need the timestamp (Ts) of the parent message. For example: 1345232312616.1231232.

If you get the message from a trigger, select "use a custom value" from the dropdown and connect accordingly by selecting the Ts field.

Otherwise, add a search step and fetch the message you want.

If true, posts in the thread and channel. See here for more info. Ignored unless the message is part of a thread.

Fields left blank will be ignored.

Fields left blank will be ignored.

Fields left blank will be ignored.

Changing a user's email address will send an email to both the old and new addresses, and also post a slackbot to the user informing them of the change.

Update selected values on this user's profile. This argument may only be specified by team admins on paid teams. Defaults to your status, when blank.

Determines which App Extensions will appear in the dropdown below.

Search query to use for finding matching messages. See the Slack Search Documentation for more information on constructing a query.

Sort messages by their match strength or by their date. Default is score.

Sort matching messages in ascending or descending order. Default is descending.

Search is case-insensitive

For most responses, we prettify the result we get from Slack. If we're missing a field you're expecting, set this to true

The leading @ is optional

For most responses, we prettify the result we get from Slack. If we're missing a field you're expecting, set this to true

Select your Team or leave empty to use your Personal account.

Optionally use a Team account when sending the SignRequest or leave empty to use your Personal account.

You have 2 options to create a SignRequest:

1. Upload a File: Use a trigger that provides a File Object.
2. Provide an URL: SignRequest will download the document from that location.

Option 1: Upload a File

PDF's are preferred. If you do not provide a File here you need to provide a url in 'File From Url' where SignRequest can download the file. Generally you'll want to use this if your trigger provides a File Object.

Option 2: Provide an URL

When not using 'File' provide a url here where SignRequest can download the file. If the download location returns a content type of text/plain or text/html SignRequest will do its best to make a pdf out of it. This can be used if you want to dynamically create pdf documents from web pages without making a pdf yourself.

By default the Sender is the email address of the connected SignRequest account. When using a Team this may also be one of email addresses of Team members.

By default only the signer(s) you add need to sign. If the Sender also needs to sign, choose 'Me & Others'.

By default we use the filename as the name of a SignRequest.

Generally you'll want to leave this empty as SignRequest generates one automatically.

A custom message to show in the SignRequest email. If left empty SignRequest will generate one for you.

Automatically remind signer(s) when the document hasn't been signed.

Your ID as a reference. Can be anything.

The email address of the signer. When multiple emails are added these signers will all have the same configuration and receive a SignRequest. When different configurations are required for separate signers please use the 'Advanced Signers Configuration' field.

Set to 'no' if this signer only needs to receive a copy of the signed document.

Set to 'yes' if this Signer only needs to approve this document ('approve' button instead of signature).

By default all signers receive the SignRequest at the same time. If you want a signer to receive the SignRequest after another signer has signed increase the order level for that signer. E.g. if you have one signer with order 0 and two with order 1, the two with order 1 will get the SignRequest simultaneously when the signer with order 0 has signed (or approved). Generally useful when a document must first be approved internally before it goes to a customer.

Sets the language of the SignRequest emails. While signing the browser of the signer determines the language of the interface.

To force the SignRequest browser interface to use the Signer Language set this to 'yes'. By default the browser language settings are used.

To enable Text Message Verification provide a mobile phone number including the country code.

For advanced users only. This field can be used to used when multiple signers or complex setups are required. This overrides all other signers related configuration fields. The value must be a valid JSON structure (array). Please note that there should be no , after the last Object {...} in the list.

For example to have the first signer to only approve a document and send the second SignRequest to the second signer only after the first signer has approved:

[
{"email": "first_signer@example.com", "needs_to_sign": true, "approve_only": true, "order": 0},
{"email": "second_signer@example.com", "needs_to_sign": true, "order": 1}
]

To just have 2 signers: sign a document at the same time:

[
{"email": "first_signer@example.com"},
{"email": "second_signer@example.com"}
]

Please also refer to our API documentation for all possible configuration options for the signer object: https://signrequest.com/api/v1/docs/. You can also l...

For advanced users only. This field can be used to prefill (template) tags in a document. The value must be a valid JSON list structure (array). Please note that there should be no , after the last Object {...} in the list.

Example:

[
{"external_id": "customer_name", "text": "John Smith"},
{"external_id": "customer_birth_date", "date_value": "1984-12-31"},
{"external_id": "customer_city", "text": "New York"},
{"external_id": "checkbox_1", "checkbox_value": "true"},
{"external_id": "checkbox_2", "checkbox_value": "false"}
]

The "external_id" is the External ID set when creating a template tag. The "date_value" field must be in ISO format ([YYYY]-[MM]-[DD]). The "checkbox_value" can only be "true" or "false". The "text" field may have any value.

Please also refer to the api documentation and our help section on the topic.

*Please note that wh...

API docs for SignRequest are located here https://signrequest.com/api/v1/docs/

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.

The Google Drive where your spreadsheet resides. If nothing is selected, then your personal Google Drive will be used. If you are connected with any Google Team Drives, you can select it here.

If a worksheet with the specified title exists, its content would be lost. Please, use with caution.

The Google Drive where your spreadsheet resides. If nothing is selected, then your personal Google Drive will be used. If you are connected with any Google Team Drives, you can select it here.

If you want to update the same row each time select a row from the dropdown box. To dynamically update the row, click open the dropdown and choose the "Custom" tab, then the "Add a search step" button.

Choose from your current custom Theme Color in your Spreadhseet, or enter a color #rrggbb in hexadecimal format.

Choose from your current custom Theme Color in your Spreadhseet, or enter a color #rrggbb in hexadecimal format.

True if the text is bold.

True if the text is italicized.

True if the text is strikethrough.

API docs for Google Sheets are located here https://developers.google.com/sheets/api/reference/rest

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.

The Google Drive where your spreadsheet resides. If nothing is selected, then your personal Google Drive will be used. If you are connected with any Google Team Drives, you can select it here.

Value of the Worksheet Title to match exactly. Search is case-sensitive.

The Google Drive where your spreadsheet resides. If nothing is selected, then your personal Google Drive will be used. If you are connected with any Google Team Drives, you can select it here.

You must have column headers. See here for more information.

Specify the column we should search for cells which match the Lookup Value.

Optionally, specify another column you want to search by. Note that if you supply this, the Zap will trigger only on rows that match both columns. (An example column might be something like Email Address or Phone Number)

An example value might be me@example.com or 555-5555

Search from bottom of the sheet? In other words, pick the most recent match?

The Google Drive where your spreadsheet resides. If nothing is selected, then your personal Google Drive will be used. If you are connected with any Google Team Drives, you can select it here.

You must have column headers. See here for more information.

Specify the column we should search for cells which match the Lookup Value.

Optionally, specify another column you want to search by. Note that if you supply this, the Zap will trigger only on rows that match both columns. (An example column might be something like Email Address or Phone Number)

An example value might be me@example.com or 555-5555

Search from bottom of the sheet? In other words, pick the most recent match?

Choose yes to trigger when someone creates a new name for an existing emoji.

Linked mentions of this user will trigger the zap. Make sure to specify a value for one or both of username or a highlight word. Specifying both a username and a highlight word means that both the linked username and word need to be included in a message to trigger the zap.

Mentions of this word will trigger the zap. Case insensitive. Make sure to specify a value for one or both of username or a highlight word. Specifying both a username and a highlight word means that both the linked username and word need to be included in a message to trigger the zap.

If no, only messages sent by users will trigger the Zap. If yes, messages sent by users and slackbots will trigger the Zap.

Warning: Slackbots don't have profiles. If yes, don't depend on user profile information being present. Also, avoid Zap loops where Zaps trigger and post slackbot messages to the same channel!

The actual reminder text that should be sent to yourself or a user. To include URLs, Slack uses this syntax.

Slack parses natural language like "in 15 minutes" or "every Thursday". Times are relative to when the Zap actually runs.

Pick a user to remind. If you pick no one, you will be reminded.

Only channels you are a member of will appear in this list. If you can't find your channel, click the Load More button or switch to the Custom tab and enter the channel's ID. Once live, the trigger will work even if you are not a member of the channel.

Specify text of the message to send. Check out the formatting help doc for advanced options.

If you choose no, this message will appear to come from you. Direct messages are always sent by bots.

Specify the bot name which appears as a bold username above the message inside Slack. Defaults to Zapier. When using Schedule At, this field will be ignored by slack.

Either an image url or an emoji available to your team (surrounded by :). For example, https://site.com/icon_256.png or :robot_face:. When using Schedule At, this field will be ignored by slack.

If you choose yes, a link to this Zap will be added to the end of the message, making it easy for you and your team to edit the Zap with one click.

If specified, this will upload the given image URL to Slack and attach it to the message separately.

Should Slack try to automatically expand links in this message? For example: turn a YouTube link into a playable widget.

If no, any usernames and channels mentioned won't be linked (or mentioned). Also affects @channel and @group. Unfortunately, @here notifications cannot be sent by Zapier.

Schedule the message to be posted later. Cannot be more than 120 days in the future. If you do schedule a message, rather than post it immediately, this Zap step will not return a ts or permalink field. This option does not support Bot Name and Bot Icon customization and will default to Zapier as bot name and icon.

Include a file to send along with your message. NOTE: Bot names/icons cannot be customized when sending a File.

If you want this to be part of a thread, you'll need the timestamp (Ts) of the parent message. For example: 1345232312616.1231232.

If you get the message from a trigger, select "use a custom value" from the dropdown and connect accordingly by selecting the Ts field.

Otherwise, add a search step and fetch the message you want.

If true, posts in the thread and channel. See here for more info. Ignored unless the message is part of a thread.

Name for the channel to be created. Channel names are normalized by converting to lowercase, replacing any non-allowed characters with hyphens or underscore, and truncating to 80 characters.

Slack will auto-link @names and #channels where applicable.

Leave empty to clear.

Use any emoji that's available in your Slack team, with leading and trailing :.

If emoji is blank when text isn't, :speech_balloon: is used by default. If both text and emoji are empty, your status will be cleared.

Provide a specific date & time for this status to expire. Statuses will not expire by default.

You can also specify a duration for this status by entering in a value like in 60 minutes, for example. Check out other ways you can use this field here.

Note: Zapier's Slack app supports a limited set of OAuth scopes/permissions, thus many of Slack's API endpoints aren't currently feasible.

API docs for Slack are located here https://api.slack.com/methods

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.

Search is case-insensitive

For most responses, we prettify the result we get from Slack. If we're missing a field you're expecting, set this to true

We search the normalized name, so don't worry about accents

For most responses, we prettify the result we get from Slack. If we're missing a field you're expecting, set this to true

Select your Team or leave empty to use your Personal account.

Select your Team or leave empty to use your Personal account.

Optionally use a Team account when sending the SignRequest or leave empty to use your Personal account.

The templates you can select depend on whether or not you've selected a Team.

Note: If you get the error 'Invalid hyperlink - Object does not exist.' this means that you've changed your Team / Personal account after selecting a template. Please make sure the selected template is available for your current Team..

By default the Sender is the email address of the connected SignRequest account. When using a Team this may also be one of email addresses of Team members.

By default only the signer(s) you add need to sign. If the Sender also needs to sign, choose 'Me & Others'.

By default we use the filename as the name of a SignRequest.

Generally you'll want to leave this empty as SignRequest generates one automatically.

A custom message to show in the SignRequest email. If left empty SignRequest will generate one for you.

Automatically remind signer(s) when the document hasn't been signed.

Your ID as a reference. Can be anything.

The email address of the signer. When multiple emails are added these signers will all have the same configuration and receive a SignRequest. When different configurations are required for separate signers please use the 'Advanced Signers Configuration' field.

Set to 'no' if this signer only needs to receive a copy of the signed document.

Set to 'yes' if this Signer only needs to approve this document ('approve' button instead of signature).

By default all signers receive the SignRequest at the same time. If you want a signer to receive the SignRequest after another signer has signed increase the order level for that signer. E.g. if you have one signer with order 0 and two with order 1, the two with order 1 will get the SignRequest simultaneously when the signer with order 0 has signed (or approved). Generally useful when a document must first be approved internally before it goes to a customer.

Sets the language of the SignRequest emails. While signing the browser of the signer determines the language of the interface.

To force the SignRequest browser interface to use the Signer Language set this to 'yes'. By default the browser language settings are used.

To enable Text Message Verification provide a mobile phone number including the country code.

For advanced users only. This field can be used to used when multiple signers or complex setups are required. This overrides all other signers related configuration fields. The value must be a valid JSON structure (array). Please note that there should be no , after the last Object {...} in the list.

For example to have the first signer to only approve a document and send the second SignRequest to the second signer only after the first signer has approved:

[
{"email": "first_signer@example.com", "needs_to_sign": true, "approve_only": true, "order": 0},
{"email": "second_signer@example.com", "needs_to_sign": true, "order": 1}
]

To just have 2 signers: sign a document at the same time:

[
{"email": "first_signer@example.com"},
{"email": "second_signer@example.com"}
]

Please also refer to our API documentation for all possible configuration options for the signer object: https://signrequest.com/api/v1/docs/. You can also l...

For advanced users only. This field can be used to prefill (template) tags in a document. The value must be a valid JSON list structure (array). Please note that there should be no , after the last Object {...} in the list.

Example:

[
{"external_id": "customer_name", "text": "John Smith"},
{"external_id": "customer_birth_date", "date_value": "1984-12-31"},
{"external_id": "customer_city", "text": "New York"},
{"external_id": "checkbox_1", "checkbox_value": "true"},
{"external_id": "checkbox_2", "checkbox_value": "false"}
]

The "external_id" is the External ID set when creating a template tag. The "date_value" field must be in ISO format ([YYYY]-[MM]-[DD]). The "checkbox_value" can only be "true" or "false". The "text" field may have any value.

Please also refer to the api documentation and our help section on the topic.

*Please note that wh...