Warning! This is an advanced trigger! Uses Node 10.x.x. Please read the Code documentation for more information.

Use the Input Data fields above to assign key names (left) and map values (right) from previous steps. Use notation inputData.keyName or inputData['keyName'] to access the values within your code. The data will be provided as strings. Learn more here.

Warning! This is an advanced action! Uses Node 10.x.x. Please read the Code documentation for more information.

What are you connecting to Plecto? E.g. Salesforce, Calendly. Make sure to always write it the same way, if you use multiple zaps from the same 3rd party system, as we use the name to group the users together.

The User ID from the external system you want to connect with Plecto. E.g. the Salesforce User ID.

The name of the User from the 3rd party system, e.g. The name of the Salesforce User.

Use an ID number which is unique per item you want to import. For instance, if you are importing Opportunities from Salesforce you want to choose the Opportunity 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.

Warning! This is an advanced trigger! Please read the Code documentation for more information.

Use the Input Data fields above to assign key names (left) and map values (right) from previous steps. Use notation input_data['keyName'] to access the values within your code. The data will be provided as strings. Learn more here.

Warning! This is an advanced trigger! Please read the Code documentation for more information.

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.