API docs for Typeform are located here https://www.typeform.com/help/data-api/

Requests can only be made to domains associated by this application.

These params will be URL-encoded and appended to the URL when making the request.

Authentication headers are included automatically

Zapier will apply these optional headers and values to the request in addition to any headers created as part of the authentication mechanism.

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.

Valid email address of recipient.

Valid email address of the sender. (must be associated with your SendGrid account)

The name added to the From email field; your name or company name.

Add a Reply-To field to your email message.

Subject of the email.

A plain-text body of the email. (This or the HTML version is required.)

HTML body of the email. (At least one of the text or HTML parameters must be provided.)

If you belong to one or more Zapier Teams, select your desired account.

Will only list "Sub-Zaps", which require the use of both the "Start a Sub-Zap" trigger and a "Return from a Sub-Zap" action.

To properly use a "Call a Sub-Zap" action you must create another Zap that contains both the "Start a Sub-Zap" trigger and "Return From a Sub-Zap" action. For your convenience, you can use this link to create a Sub-Zap.

Limit request to responses submitted since the specified date and time. Could be passed as int (timestamp in seconds) or in ISO 8601 format, UTC time, to the second, with T as a delimiter between the date and time

Limit request to responses submitted until the specified date and time. Could be passed as int (timestamp in seconds) or in ISO 8601 format, UTC time, to the second, with T as a delimiter between the date and time. NOTE: until must be after since if both parameters are specified

List the inputs to accept from "Call a Sub-Zap" and they will show up as fields. Add the word "required" to the label if you would like it to be required in the calling Zap.

List the keys and values to return to the original "Call a Sub-Zap". For example, you could ask for an email address and use it later in the Zap. It is generally safe to add more return values, but be careful about removing items that parent Zaps may rely already on!