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.

Filter the trigger by activity types. Leave this blank if you'd like to trigger on all activity types.

Filter the trigger by activity tags. Please enter one tag per line. Leave this blank if you'd like to trigger on all activity tags.

Filter activities by member tags. Please enter one tag per line. Leave this blank if you'd like to trigger on all member tags.

Filter the trigger by keywords that appear in the activity. Please enter one tag per line. Leave this blank if you are not filtering on specific keywords

By default, we will not send you activities that happen from your teammates in Orbit. Change this to true if you'd like to get these activities.

The slug for the member you want to add the Identity to, for example sally-tibro.

The name of the source platform for this Identity, for example discord.

The full name of the member in the source system, if known.

Specifies the location of the source, such as the host of a Discourse instance.

The username of the person in the source system. For example sally_tibro45.

If the source system uses a UID as well as a username, add this here. UID will be shown on the Member profile instead of the username if specified.

The email of the person in the source system.

For custom identities, an optional link to the profile on the source system.

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

These details will appear below the Activity Title.

Use this to categorize and group activities, e.g. form submission, event registration, etc.

The Activity Type Key is a predefined key from your Activity Types list that references which Activity Type to use. Such as eventbrite:rsvp.

Add a link to this activity that points to further information.

The URL of the Link Text. Be sure to include https://

A custom weight to be used in filters and reports; defaults to 1.

Capture facets of the activity to group by later e.g. locations or channels. Each should be provided as a key value pair, eg. Event Name with a value of "March Meetup".

This should be a valid ISO 8601 date.

Keys are used to ensure that duplicate events are not created. Orbit will automatically create a key if this field is left blank, but you can create your own if you want to.

Add tags to the member's profile, separated by commas. This is a non-destructive action. It will not remove any existing member tags.

Replaces all existing tags for the member; comma-separated list. This is a destructive action, it will remove any and all existing member tags for the member.

Orbit will add this activity to the Member who did the action. You can use email address, GitHub handle, or Twitter handle. At least one is required. If a member doesn't exist with that info, Oribt will create a new member.

Just the text after the @ symbol

Biographical details about the member

The job title associated with this member

The member's preferred pronouns

The member's geographic location, for example: Paris, France.

The member's birthdate

The t-shirt size of the member, for example: small, medium, large, x-large, etc.

Is the member a teammate of your workspace?

Optional for custom identity sources.

Add the member name from a custom identity source.

Required if custom identity information is included.

The type of custom identity. Known values include github, twitter, discourse, email, linkedin, devto.

Custom values can also be used.

Optional data for custom identities.

Specifies the location of the custom identity source, such as the host of a Discourse instance.

A custom identity username, email, or uid is required if a custom identity is provided.

The username of the person in the custom identity source system.

A custom identity username, email, or uid is required if a custom identity is provided.

The email of the person in the custom identity source.

A custom identity username, email, or uid is required if a custom identity is provided.

The user ID (uid) of the person in the custom identity source.

An optional link to the profile of the person on the custom identity source.