Select “Yes” to [stop this Zap step](https://help.zapier.com/hc/en-us/articles/20505304170637-Review-Zap-run-statuses#h_01HD20969HPZ01ENM30NQR79X5) if the app returns an error and enable automatic authentication refresh. Select “No” to run the Zap step regardless of errors. Learn more about [API Request action error handling](https://help.zapier.com/hc/en-us/articles/12899473501453#h_01JKRBY68EDXBB1V817DSTRZ0N).

Requests can only be made to domains associated by this application. Read more about [API Request Setup](https://help.zapier.com/hc/en-us/articles/12899607716493).

Any parameters added to a URL will be URL-encoded and appended to the request URL to pass additional data to the API request.

These headers and values will be applied to the request in addition to any headers created as part of authentication. Authentication headers are added automatically.

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.

Google Forms is an easy way to collect data from the web with a simple UI and powerful editor. Works hand-in-hand with Google Sheets!

Google Forms

Instantly build dynamic interfaces that connect to Zaps and a data source (like Tables). Interfaces gives you a drag-and-drop way to build visual workflows for any business process, without writing code.

Zapier Interfaces

Your LRS endpoint URL. Does not end in / or /statements.

Email address of the agent to filter. Do not include "mailto:".

Only 1 agent identifier will be used in the filter.

The hex-encoded SHA1 hash of a mailto IRI (i.e. the value of an mbox property).

Only 1 agent identifier will be used in the filter.

An openID that uniquely identifies the Agent to filter.

Only 1 agent identifier will be used in the filter.

The unique id or name used to log in to the account you want to filter by.

Only 1 agent identifier will be used in the filter. Account Name will only be used if Account HomePage is also provided.

The canonical home page for the system the account you want to filter is on.

Only 1 agent identifier will be used in the filter. Account HomePage will only be used if Account Name is also provided.

Filter, only return Statements matching the specified Verb id.

Filter, only return Statements for which the Object of the Statement is an Activity with the specified id.

Filter, only return Statements matching the specified registration id. Note that although frequently a unique registration will be used for one Actor assigned to one Activity, this cannot be assumed. If only Statements for a certain Actor or Activity are required, those parameters also need to be specified.

Apply the Activity filter broadly. Include Statements for which the Object, any of the context Activities, or any of those properties in a contained SubStatement match the Activity parameter, instead of that parameter's normal behavior. Matching is defined in the same way it is for the "activity" parameter.

Apply the Agent filter broadly. Include Statements for which the Actor, Object, Authority, Instructor, Team, or any of these properties in a contained SubStatement match the Agent parameter, instead of that parameter's normal behavior. Matching is defined in the same way it is for the "agent" parameter.

Only Statements stored since the specified Timestamp (exclusive) are returned.

Only Statements stored at or before the specified Timestamp are returned.

Maximum number of Statements to return. 0 indicates return the maximum the server will allow.

If ids, only include minimum information necessary in Agent, Activity, Verb and Group Objects to identify them. For Anonymous Groups this means including the minimum information needed to identify each member.

If exact, return Agent, Activity, Verb and Group Objects populated exactly as they were when the Statement was received. An LRS requesting Statements for the purpose of importing them would use a format of "exact" in order to maintain Statement Immutability.

If canonical, return Activity Objects and Verbs populated with the canonical definition of the Activity Objects and Display of the Verbs as determined by the LRS, after applying the language filtering process defined below, and return the original Agent and Group Objects as in "exact" mode.

Enter the complete Statement JSON here, including any variables form the source app.

Use the [statement generator](http://tincanapi.com/statement-generator/) to build and validate your statement. This Zap performs no validation and will not work if this statement JSON is not perfect. [Contact Watershed support](https://watershedlrs.zendesk.com/hc/en-us/requests/new) for help with statement JSON.

Warning: if you use variables that could contain double quotes, this will break your JSON. There is no way to escape variables used within the Statement JSON field.

Value to be inserted into other action fields. Use the syntax [[placeholder]] to insert the value.

The full name of the person who did the thing. You should normally map this to a variable.

Either Email or Account should be completed (not both). If both or none are completed, the value of Email will be used.

Do *not* include "mailto:" at the start of the email. This will be added before the statement is sent to the Learning Record Store.

The name or id of the actor's account on the system identified by the Actor Account HomePage.

The system the actor's account exists on.

The id of the verb relating to the action taken by the actor. Select a verb from the dropdown. If the verb you need is not on this list, [register it](https://registry.tincanapi.com) and it will automatically appear here in Zapier.

The human readable display for the verb. Normally the same as the label of the verb above.

This method only supports objects which are activities. This field is the activity id. The activity id must be an IRI e.g. http://example/com/xapi/activities/12345. Normally this is the unique URL of where the thing that your tracking (and only that thing) can be found.

See [get the activity id right](http://tincanapi.com/content/) for tips on choosing good activity ids. [Contact Watershed Support](https://watershedlrs.zendesk.com/hc/en-us/requests/new) if you need help.

URL where more information about the activity can be found.

JSON representing an activity definition extensions object. Must start with { and end with }.

Line breaks will be removed but double quotes within keys or values will not be escaped, even if they are entered via variables.

Leave this field blank if you are unsure what to enter here.

The scaled score for the experience. Raw, min and max score are not supported by this action. [Contact Watershed support](https://watershedlrs.zendesk.com/hc/en-us/requests/new) to request support for raw, min and max in a future version of this Zap.

Length of the experience in *milliseconds*. This will be converted to an ISO 8601 duration of the format PT12345.67S before the statement is sent to the Learning Record Store (LRS). Milliseconds will be rounded to centi-seconds.

JSON representing a result extensions object. Must start with { and end with }.

Line breaks will be removed but double quotes within keys or values will not be escaped, even if they are entered via variables.

Leave this field blank if you are unsure what to enter here.

JSON representing a complete context object. Must start with { and end with }.

Line breaks will be removed but double quotes within keys or values will not be escaped, even if they are entered via variables.

[Contact Watershed support](https://watershedlrs.zendesk.com/hc/en-us/requests/new) if you need help with this, or any other, field.

The scaled score for the experience. Min and max score are not supported by this action. [Contact Watershed support](https://watershedlrs.zendesk.com/hc/en-us/requests/new) to request support for min and max in a future version of this Zap.

Watershed LRS is a learning analytics platform that provides actionable insights from your training and performance data.

Watershed LRS

Optimize your process of managing and assessing new Google Forms responses with this ingenious workflow. Once a new form response lands on your Google Forms, it prompts Watershed LRS to log the data immediately for updating and instant processing. This ensures you can evaluate your form responses quickly within your Watershed LRS account, saving you time and improving efficiency.

Google Forms + Watershed LRS

Send a statement in Watershed LRS for new form responses in Google Forms

Supported triggers and actions

New Form Response

API Request (Beta)

Send a Statement (Advanced)

New or Updated Form Response

New Statement

Send a Statement

About Google Forms

Related categories

Similar apps

Zapier Interfaces

About Watershed LRS

Related categories