Optional. If you specify a project we will assign this task to the project.

Enter time in 12h or 24h format. Examples: 14:30 / 2:30pm

You can enter time in 12h or 24h format. Examples: 14:30 / 2:30pm

Format: YYYY-MM-DD. Example: 2021-12-02

Name must exactly match.

(Optional) Limit to records added to a specific View, and return records in the View order.

Returns an extra File field with file contents. Set this field to Yes if you have trouble with Airtable file URLs expiring. File contents greater than 100MB will cause an error.

Base in which to create the record.

Pick the Airtable base containing the records you wish to update.

Pick the Airtable table containing the records you wish to update.

Pick the Airtable record that you wish to update.

Base to search for a record.

Pick an Airtable table that you want to search.

Pick a field from the base to match against the search value.

The value of unique identifier for the record.

(ADVANCED) Alternatively, you can use an Airtable search formula to find records based on advanced conditions and any number of fields. Learn more.

You can optionally limit the search to a specific view id.

Base in which to create the record.

Pick an Airtable table that you want to search.

Pick a field from the base to match against the search value.

The value of unique identifier for the record.

(ADVANCED) Alternatively, you can use an Airtable search formula to find records based on advanced conditions and any number of fields. Learn more.

You can optionally limit the search to a specific view id.

The HTTP method we'll use to perform the request.

Any URL with a querystring will be re-encoded properly.

If yes, request data below will be overridden with the raw data from the previous step (you are still responsible for headers though, like Content-Type). Defaults to no.

Place raw data for the request here. Could be JSON, XML, etc. Nothing is parsed for you here (including extra line breaks or spaces -- everything is sent verbatim). You probably need to define a header below corresponding to your data Content-Type. Reminder: data provided in this field is completely ignored if you chose "yes" to pass-through.

By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.

Any URL with a querystring will be re-encoded properly.

Pay special attention to the proper mapping of the data below.

These are key-value pairs that will form the data portion of the request. If you leave these empty, all fields from the previous step will be used. If you want to send your own raw JSON or form-encoded values here, please use the Custom Request action instead.

Wraps the request in an array if that is something the service requires.

A file object to be attached to the request. The request will automatically be converted to multipart/form-data, with the above payload type defining the sub content-type for the data being passed.

By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.

Enter time in decimal or hh:mm format. Examples: 1.5, 1:30

Format: YYYY-MM-DD. Example: 2021-12-02

Format: YYYY-MM-DD. Example: 2021-12-02

Name must exactly match.

Name must exactly match.

You must have at least one "Last Modified Time" type column in your Table in order to use this Trigger. Learn more about those here.

When this column changes to a new timestamp, your Zap will trigger on the corresponding record. Note: Must be a Last Modified Time column type.

Filter on updates to a specific View in your Table.

Returns an extra File field with file contents. Set this field to Yes if you have trouble with Airtable file URLs expiring. File contents greater than 100MB will cause an error.

Base in which to create the record.

Base to search for a record.

Pick an Airtable table that you want to search.

Pick a field from the base to match against the search value.

The value of unique identifier for the record.

(ADVANCED) Alternatively, you can use an Airtable search formula to find records based on advanced conditions and any number of fields. Learn more.

Limit the search to a specific view. Useful for sorting results.

Returns an extra File field with file contents. Set this field to Yes if you have trouble with Airtable file URLs expiring. File contents greater than 100MB will cause an error.

Base in which to create the record.

Pick an Airtable table that you want to search.

Pick a field from the base to match against the search value.

The value of unique identifier for the record.

(ADVANCED) Alternatively, you can use an Airtable search formula to find records based on advanced conditions and any number of fields. Learn more.

Limit the search to a specific view. Useful for sorting results.

Returns an extra File field with file contents. Set this field to Yes if you have trouble with Airtable file URLs expiring. File contents greater than 100MB will cause an error.

This should return a list of dictionaries of content type JSON in reverse chronological order. For example: [{"id":1234},{"id":1235}]

If the returned JSON is not a list and is instead an object (maybe paginated), enter the key that contains the results. Example: "results", "items", "objects", etc... (children via dot syntax supported)

Zapier deduplicates the array we see each poll against the id key. If the id key does not exist, you should specify an alternative unique key to deduplicate off of. If neither are supplied, we fallback to looking for the shortest key with id in it otherwise we will raise an error.

If the content fetched is XML or HTML, optionally define an xpath to extract data from the content. Will trigger whenever the content at the xpath changes!

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.

By default, Zapier gives you the entire payload of the webhook. If this is specified, Zapier will only grab the child key from the object(s) sent to Zapier. For example, given {"contact": {"name": "Mike"}}, add "contact" here to only return {"name": "Mike"}. Traverse more deeply nested children by using dot-separated syntax. Line item payloads will run your Zap for each instance of the child key.

We recommend not putting any query string arguments in the URL (use "Query String Params" below).

These params will be URL-encoded and appended to the URL when making the request. Note: If you specify nothing for this field, we will automatically encode and include every field from the previous step in the query string. If you don't want this, use the "Custom Request" action.

If "yes", this dumps the results directly to a key (set below) as JSON. If "no", we simulate a form.

Only used if As JSON.

By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.

Any URL with a querystring will be re-encoded properly.

Pay special attention to the proper mapping of the data below.

These are key-value pairs that will form the data portion of the request. If you leave these empty, all fields from the previous step will be used. If you want to send your own raw JSON or form-encoded values here, please use the Custom Request action instead.

Wraps the request in an array if that is something the service requires.

A file object to be attached to the request. The request will automatically be converted to multipart/form-data, with the above payload type defining the sub content-type for the data being passed.

By default we convert fields with double underscores into nested dictionaries. Select no here to turn this behavior off.

A pipe (|) separated username, password combo for standard HTTP authentication.

Key, value pairs to be added as headers in all requests.