Key at which to store the value. Keys must be 32 characters or less in length.

Child Key & Values to set. Child values already stored and not in this list will not be modified or removed.

Key at which to store the value. Keys must be 32 characters or less in length.

Value to set. Leave blank to remove this key from the store.

Key at which to lookup the list value.

Items from the list will be combined together into a single value with this format. Use %s as a placeholder for each list item.

For example:

If your list has two items "1234" and "6789"
And your format is "number %s, "
The output will be: "number 1234, number 6789"

Optionally, define what should be used to separate each item. (Default: nothing).

Key at which to store the value. Keys must be 32 characters or less in length.

Child keys to retrieve. Child keys not in this list will not be returned.

Child Key & Values to set. Child values already stored and not in this list will not be modified or removed.

WARNING: Looping by Zapier is an advanced feature currently in Beta. Learn how to create loops here and understand limitations here.

Type loop value name(s) in the field(s) on the left. Map Line Item value(s) to loop through on the right.

Remove whitespace surrounding each individual value? Defaults to 'True'.

A counter value called 'loop_iteration' will be added to each iteration of the loop. Does not affect the data to loop through. Defaults to '1'.

Set this value to limit the number of loops performed. Data in iterations past the limit will be ignored. A number higher than 500 will be reduced to 500. A number less than 1 will halt this step.

WARNING: Looping by Zapier is an advanced feature currently in Beta. Learn how to create loops here and understand limitations here.

Type loop value name(s) in the field(s) on the left. Map and/or type values separated by a delimiter (ex: ',') on the right.

Supports Special Characters. Defaults to ','

Remove whitespace surrounding each individual value? Defaults to 'True'.

A counter value called 'loop_iteration' will be added to each iteration of the loop. Does not affect the data to loop through. Defaults to '1'.

Set this value to limit the number of loops performed. Data in iterations past the limit will be ignored. A number higher than 500 will be reduced to 500. A number less than 1 will halt this step.

Set this to true to list test mode orders.

The website profile’s unique identifier, for example pfl_3RkSN1zuPE. Omit this parameter to retrieve all orders across all profiles.

Set this to true to embed payments in the response.

Set this to true to embed refunds in the response.

Set this to true to embed shipments in the response.

The payment profile's unique identifier.

The description of the payment you are creating. This will be shown to your customer on their card or bank statement when possible. We truncate the description automatically according to the limits of the used payment method. The description is also visible in any exports you generate. We recommend you use a unique identifier so that you can always link the payment to the order in your back office. This is particularly useful for bookkeeping.

The URL your customer will be redirected to after the payment process.

The URL Mollie will call as soon the payment changes status. This is useful for updating your local order status.

Allows you to preset the language to be used in the hosted payment pages shown to the consumer.

Normally, a payment method screen is shown. However, when using this parameter, you can choose a specific payment method and your customer will skip the selection screen and is sent directly to the chosen payment method. The parameter enables you to fully integrate the payment method selection into your website.

Set this to true to make this order a test order.

Set this to true to search for test orders.

The order unique identifier.

The information to embed to the order.

Set this to true to search for shipments in test orders.

The order unique identifier.

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.

Keys at which to store the value must be 32 characters or less in length. Leave values blank to remove the key from the store.

Key at which to store the value. Keys must be 32 characters or less in length.

Value to set. Leave blank to remove this key from the store.

Only set the value if the stored value matches this. Leave blank to only set if a value is not already stored.

Keys at which to lookup the values.

Key at which to lookup the value.

Key at which to store the value. Keys must be 32 characters or less in length.

Value to set. Leave blank to remove this key from the store.

WARNING: Looping by Zapier is an advanced feature currently in Beta. Learn how to create loops here and understand limitations here.

A counter value called 'loop_iteration' will be added to each iteration of the loop. Does not affect the data to loop through. Defaults to '1'.

Set the iteration number to end the loop at here. Defaults to '1'. Cannot be less than Loop iteration counter start.

Set the amount to increment the counter for each iteration of the loop. Defaults to '1'. Cannot be '0' or negative. Must be an whole number.

Set this value to limit the number of loops performed. Data in iterations past the limit will be ignored. A number higher than 500 will be reduced to 500. A number less than 1 will halt this step.

This settings defines whether test or live data should be retrieved from Mollie.

This settings defines whether test or live data should be retrieved from Mollie.

The website profile's unique identifier, for example pfl_3RkSN1zuPE. Omit this parameter to retrieve all orders across all profiles.

Set this to true to make this order a test order.

The payment profile’s unique identifier.

The URL your customer will be redirected to after the payment process.

The URL Mollie will call as soon the payment changes status. This is useful for updating your local order status.

The date of when the payment will expire.

Allows you to preset the language to be used in the hosted payment pages shown to the consumer.

Normally, a payment method screen is shown. However, when using this parameter, you can choose a specific payment method and your customer will skip the selection screen and is sent directly to the chosen payment method. The parameter enables you to fully integrate the payment method selection into your website.

The order number. For example, 16738. We recommend that each order should have a unique order number.

The person’s organization, if applicable.

The title of the person, for example Mr. or Mrs..

The given name (first name) of the person.

The family name (surname) of the person.

The email address of the person.

The email address of the person.

The email address of the person.

The email address of the person.

The email address of the person.

The type of product bought, for example, a physical or a digital product.

The category of product bought.

A description of the order line, for example LEGO 4440 Forest Police Station.

The number of items in the order line.

The SKU, EAN, ISBN or UPC of the product sold. The maximum character length is 64.

A link pointing to an image of the product sold.

A link pointing to the product page in your web shop of the product sold.

The payment profile’s unique identifier.

The URL Mollie will call as soon the payment changes status. This is useful for updating your local order status.

The date of when the payment will expire.

The description of the payment you are creating. This will be shown to your customer on their card or bank statement when possible. We truncate the description automatically according to the limits of the used payment method. The description is also visible in any exports you generate. We recommend you use a unique identifier so that you can always link the payment to the order in your back office. This is particularly useful for bookkeeping.

Set this to true to make this order a test order.

This settings defines whether test or live data should be retrieved from Mollie.

The Id of the payment you are searching for

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.