Email address of the assignee. If your Space allows Multiple Assignees, you can enter multiple email addresses.

If your Space has Priorities enabled, you can specify a Priority.

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.

Select your existing AutoDialer Campaign. You can create new campaigns from JustCall.io web portal.

Contact's Phone Number

Contact's First Name

Enter Contact's Last Name

first name of the contact

last name of the contact

phone number of the contact

email of the contact

company of the contact

notes related to the contact

Will create this contact only under the specified agent associated with provided agentid

Enter the recipient's number

Please select a number to text from. You can add new numbers from JustCall.io web portal.

Add the contents of your text message here.

Comma seperated links of media files. Maximum 5 links are allowed. Links should be publicly accessible and their cumulative size should not exceed 5 MB

Enter the recipient's number

Please select a number to text from. You can add new numbers from JustCall.io web portal.

Add the contents of your text message here.

Unique id of the contact

Phone number of the contact

Email address associated with the contact

API docs for ClickUp are located here https://clickup.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.

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.

The number from which you are expecting replies. This is generally your customer's number.

One of your SMS enabled numbers on JustCall. If present, JustCall will only check for replies received on this number of yours.

If your customer/client numbers are not in international format, use this field to send country code. For example US for United States, GB for United Kingdom etc.

Enter the recipient's number

Please select a number to text from. You can add new numbers from JustCall.io web portal.

Add the contents of your text message here.

Your text message will go out on this date and at a particular time

Offset value is related to Date/Time. A positive offset value will add itself to scheduled date and time. Similarly, a negative value will subtract itself from schedule date and time. Ex - A value of +15 will send this text message 15 minutes after the scheduled date and time.

Unique id of the contact

First name of the contact

Last name of the contact

Phone number of the contact

The email address associated with the contact

Company with which this contact is associated

Custom information that you need to associate with this person

Custom name of the number

Phone number of the contact