Cloud and Enterprise Community customers can create automated workflows between Invision Community and over 3,000 other apps including Google Documents, MailChimp, Facebook and Twitter with just a few clicks.
If you haven’t integrated your Invision Community with Zapier yet, you’re leaving organic growth on the table!
It’s been a wild year, so we’d like to refresh your memory regarding the very powerful Invision and Zapier marriage (hey, remember when weddings were a thing?).
Zapier is a service that allows you to connect over 3,000 web apps.
Last year, Invision Community released the 4.5 update, and with it a beta service of Zapier integration.
Zapier is the first smart community enhancement available for Cloud and Enterprise Community customers exclusively.
It’s worth it’s weight in gold. Or, crypto? However we quantify value these days, Invision Community and Zapier together creates real value and has the potential to elevate your community (and bottom line).
If you haven’t yet set up Zapier, you can follow our guide to creating your first ‘Zap’ with Invision Community.
As @Matt previously mentioned in our announcement post, the Invision and Zapier integration can communicate with some of the Internet’s most wide-reaching platforms, including Google Docs, Twitter, Facebook, Slack, Trello, Facebook Ads, ActiveCampaign, Zendesk, Asana, Salesforce, Hubspot, Discord, Stripe and more.
There are three key items we want to highlight:
Triggers: Invision → Zapier
A “trigger” takes place when there’s a specified signal in your community. For instance, a member registering or a topic being posted.
A trigger can be sent to Zapier to then run actions in other apps.
Here are a few examples:
- When a member registers, add their email to a Mailchimp list.
- When a moderator posts a topic in a news forum, share it on Facebook, Twitter and other social platforms.
- When a member posts something that requires moderator approval, send a message to a Slack channel for your moderators.
Actions: Zapier → Invision
An “action” is similar to a “trigger” in that there’s movement, but it happens by setting up an action in Zapier first which then tells your community to perform X action.
Whereas a “trigger” happens by setting up an action in your Invision community first, which then tells Zapier to perform X action.
Here are some examples to wrap your mind around:
- When you add an event in a Google Calendar, create a Calendar Event on your community.
- When you receive an email to a feedback email address, create a topic on your community in a forum for moderators.
- When you create a task in Trello, add a record to a Pages Database on your community.
- When a new member registers, add them to your mailing list via MailChimp, ActiveCampaign, etc.
Self-integrated: Invision → Invision
We also included a self-integrated option that allows community owners to connect an Invision Community trigger to an Invision Community action. For example: when a member registers, create a topic in a welcome forum.
In a nutshell:
Triggers = Invision talks to → Zapier, then Zapier takes action.
Actions = Zapier talks to → Invision, then Invision takes action.
Self-integrated = Your Invision community talks to → your Invision community, then your Invision community takes action.
If you have any questions, please feel free to comment below! I’m here to help you transform your Invision community into an engaging and efficient world with automated systems powered by Zapier.
Already on Zapier? What’s been your experience? Sound off and let us know what features you’ve utilized thus far and which triggers or actions you’d like to see for the future.