E-mail address of client to activate.

E-mail address of client to assign to a trainer.

Pick a trainer to client to.

If the test trigger returns the owner's email, the send action may fail because a program cannot be copied to the owner account. To ignore this error, skip the test and the Zap should work properly.

Leave blank to start immediately.

E-mail address of client to deactivate.

If the test trigger returns the owner's email, the action may fail because the owner account cannot be removed from a group. To ignore this error, skip the test and the Zap should work properly.

If the test trigger returns the owner's email, the send action may fail because the owner account cannot be subscribed to a program. To ignore this error, skip the test and the Zap should work properly.

If the start type is Fixed, the start date is required.

If the test trigger returns the owner's email, the action may fail because the owner account cannot be unsubscribed from a program. To ignore this error, skip the test and the Zap should work properly.

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.

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.

The email address for the client you want us to copy training plans from.

Email address for the client to whom the new plans will be applied. The copied plans will be queued after any existing training plans and will start on the same day of the week as the previous plan did.

If the test trigger returns the owner's email, the send action may fail because the meal plan cannot be attached to owner's account. To ignore this error, skip the test and the Zap should work properly.

File to attach.

Email address of the new user.

First name of the user.

Last name of the user.

Status of the client, pending, active or deactivated.

Client's Activity Level.

Pick a trainer to assign to.

Pick an existing group to add this new client to.

Pick an existing custom client tag to apply to this new client.

Select existing main program to add this client to.

Select start date of existing main program to add this client to.

Email of client to remove tag from.

Pick a tag to remove from client.

If the test trigger returns the owner's email, the send action may fail because the account receiving the message cannot have the same email as the account sending the message. To ignore this error, skip the test and the Zap should work properly.

If the test trigger returns the owner's email, the send action may fail because the owner account cannot be subscribed to a program. To ignore this error, skip the test and the Zap should work properly.

If the start type is Fixed, the start date is required.

Email of the client.

File to attach.

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.

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.