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.

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.

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.

Returns the raw response from the request, in the following keys: response, status, headers. Ignores `Unflatten`.

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.

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.

Webhooks simply POST data (or JSON) to a specific URL every time we see something new. Webhooks can also accept data (or JSON) to kick off a workflow in Zapier.

Webhooks by Zapier

Where the message it sent from and may be any of the following types.
ALPHANUMERIC is max 11 characters. 
MSISDN, the mobile number with contry code and starts with +. 
SHORTNUMBER is country specific and usually 4 to 6 digits.
See [Source](https://www.linkmobility.com/partners/zapier).

The recipient of the message. Starts with + followed by country code and mobile number. 

Example: +1234567890

See [Destination](https://www.linkmobility.com/partners/zapier)

This is the message content itself. The data coding scheme specifies the format, encoding, on this value. See [User data](https://www.linkmobility.com/partners/zapier) for more details.

Your platformId. Provided to you by [Support](https://www.linkmobility.com/support). 

Your user may have a default Platform id.

Your platformPartnerId. Provided to you by [Support](https://www.linkmobility.com/support).

Your user may have a default Platform id.

One or more gates that should be used for sending delivery reports back to the client. Contact [Support](https://www.linkmobility.com/support) for more information and options.

Your own internal transaction ID. Not used for anything except as a reference.

Specify the format and encoding of the User data.

TEXT (default), auto detect encoding of GSM7 or UCS2 text. GSM, standard GSM7 encoding with up to 160 characters per SMS. UCS2, UTF-16 compatible format with up to 70 characters per SMS. BINARY, used when sending legacy logo, etc with up to 140 bytes per SMS. See [Data Coding Scheme](https://www.linkmobility.com/partners/zapier)

Hex encoded value that may be used for splitting messages manually. See [User data header](https://www.linkmobility.com/partners/zapier)

Used for premium SMS when charging the end user. Price in cents. Requires configuration by [Support](https://www.linkmobility.com/support). See [Premium SMS](https://www.linkmobility.com/partners/zapier) for more details.

Used for premium SMS when charging the end user. Requires configuration by [Support](https://www.linkmobility.com/support). See [Premium SMS](https://www.linkmobility.com/partners/zapier) for more details.

Used for premium SMS when charging the end user. This will be printed on the end-user’s phone bill. Requires configuration by [Support](https://www.linkmobility.com/support). See [Premium SMS](https://www.linkmobility.com/partners/zapier) for more details.

Used for premium SMS when charging the end user. Specify type of product. Requires configuration by [Support](https://www.linkmobility.com/support). See [Premium SMS](https://www.linkmobility.com/partners/zapier) for more details.

This specifies how long the message is supposed to live in milliseconds. Default is 48 hours (172800000). Requires configuration by [Support](https://www.linkmobility.com/support).

An easy tool for companies to send SMS to cell phones world wide. Requires an agreement with LINK Mobility.

LINK Mobility

Effortlessly send an SMS via Link Mobility whenever a new webhook is caught. Automate trusted communication from any source you wish!

LINK Mobility + Webhooks by Zapier

Send SMS messages via LINK Mobility for newly caught webhooks

Supported triggers and actions

Catch Raw Hook

Retrieve Poll

GET

PUT

Catch Hook

Custom Request

POST

Send SMS

About LINK Mobility

Related categories

About Webhooks by Zapier

Related categories