Select the community for which you'd like to select the topics for.

Select the space for which you'd like to select the topics for.

Select the community you'd like to post the comment in.

Select the space you'd like the post the comment in.

The email of the member to post this comment on behalf of. If none is specified, the comment will be posted by the community admin.

Select the community you'd like to create it in.

Select the channel you'd like to create it in.

Email of the user for who you want to create topic.

If toggled on, "...see more" truncation will be disabled on this topic.

If toggled on, meta information such as the topic author's name will be hidden from this topic.

Email of user to remove from space group.

The email of the community member to remove.

Select the community you'd like to send message in

Email of the community member

The email of the tagged community member to remove member tag.

Select the community you'd like to add the user to.

Select member whom you want to update

Please provide the updated name.

Please provide the updated profile image.

Please provide the updated Headline.

Please provide the updated Bio.

Please provide the updated Location.

Please provide the updated website URL.

Please provide the updated twitter URL.

Please provide the updated facebook URL.

Please provide the updated Instagram URL.

Please provide the updated linkdin URL.

If you'd like the member to be added to space(s), select them here.

If you'd like the tag member to Member Tag(s), select them here.

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

Select custom event to be triggered. Create custom events in an Omnisend App, if you haven't done that yet.

Enter for which contact (subscriber) this custom event should be triggered.

Enter custom field system name and select its value. fields is an object with your defined (in Omnisend app) keys and values with predefined corresponding types. Custom fields can contain any information needed on automated emails.

The URL for your virtual event. Example: https://your-event-url-here.com/

The location for your virtual event. Example: New York, NY

If enabled, non-attendees will not be able to see the location of your event until they RSVP.

If enabled, no one will be able to RSVP into your event. You can change this later.

If enabled, attendees will be sent an email reminder an hour before the event.

If enabled, attendees will receive an in-app notification reminder an hour before the event.

If enabled, attendees will receive an email confirmation when they RSVP.

If enabled, attendees will receive an in-app notification in their 'Following' tab when they RSVP.

Set a custom thank you message to be shown on the confirmation modal and email

Customize the title meta tag for SEO. If empty, we'll use the name of the event.

Customize the description meta tag for SEO.

Customize the Open Graph title. If empty, we'll use the event name.

Customize the Open Graph description.

Hide author name and information.

Prevent members from liking each other's comments.

Prevent members from posting comments.

If enabled, members will not able to see the attendee list.

Hide event from the homepage and weekly digest.

The email of the user you'd like to invite to your community.

Optionally, pre-set a password for this user.

The name of the user you'd like to invite to your community.

Select the community you'd like to add the user to.

Add link of profile image.

If you'd like the member to be automatically added to space(s), select them here.

Add this user to a space group and all the spaces within it, including future ones.

If you'd like the automatically tag member to Member Tag(s), select them here.

Optionally, you can skip sending the email invitation (i.e. if you've already set a password for them that they'll know.)

Email of user to remove from space

Email of member who need to be RSVP'd

Select the community you'd like to start a group chat in.

A comma-separated list of community member emails for this group chat. For members to be added to the group chat, they'll already need to be a member of your community.

Email of member you want to UnRSVP from event.

The URL for your virtual event. Example: https://your-event-url-here.com/

The location for your virtual event. Example: New York, NY

If enabled, no one will be able to RSVP into your event. You can change this later.

If enabled, non-attendees will not be able to see the location of your event until they RSVP.

If enabled, attendees will be sent an email reminder an hour before the event.

If enabled, attendees will receive an in-app notification reminder an hour before the event.

If enabled, attendees will receive an email confirmation when they RSVP.

If enabled, attendees will receive an in-app notification in their 'Following' tab when they RSVP.

Set a custom thank you message to be shown on the confirmation modal and email

Customize the title meta tag for SEO. If empty, we'll use the name of the event.

Customize the description meta tag for SEO.

Customize the Open Graph title. If empty, we'll use the event name.

Customize the Open Graph description.

Add link of opengraph image

Hide author name and information.

Prevent members from liking each other's comments.

Prevent members from posting comments.

If enabled, members will not able to see the attendee list.

Hide event from the homepage and weekly digest.

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.

Email is required if Phone Number is not provided.

Phone Number is required if Email is not provided.

Can be:

• -subscribed - Contact is subscribed (default)
• -unsubscribed - Contact has unsubscribed
• -nonSubscribed - Contact's status is unknown (contact hasn't subscribed or unsubscribed yet)
• -removed (DEPRECATED) - Contact was removed by system (bounced emails, etc.) or administrator.

If empty - will be pre-filled with current date.

We strongly recommend to add at least one tag so you could separate among all contacts, i.e. source: mailchimp. Enter one tag per input. Press '+' button to add more tags.

Contacts creation date, ISO 8601 format. (example: 2017-05-30T14:11:12Z).

ISO 3166-1 alpha-2 (2 letter) country codes. More info here.

Contact's gender. Can be: m - male, f - female.

Date format. Example: 1981-11-05.

ISO 8601 format.

Opt-in IP address in ipv4 or ipv6 format. Opt-In Date is required if this field is passed.

Enter custom properties name and select field so that values would be assigned.

Name restrictions:

• • Can contain only Latin characters, numbers, "_" (underscore) sign
• • Name is case sensitive
• • Max name length - 128 symbols. Bellow entered custom properties name will be filled after predefined "zapier_", i.e. zapier_[YOUR_ENTERED_PROPERTIES_NAME]. So you have 122 symbols left.

Value restrictions:

• • String max length - 2048 characters
• • List and object types are not supported
• • Floats are rounded to 6 digits precision.

Read more here.

Send welcome email (will be sent only if welcome workflow is turned on) or not. Default value - true.