As an Account Executive at Orbit, I speak with dozens of DevRel leaders and community builders each week. I have a front row seat to the opportunities and challenges faced by our industry, and week over week, one big problem seems to surface in every call: community data is spread across dozens of platforms.
In fact, “Not able to access the data I need” is one of the most common frustrations for community professionals, according to The 2022 Community Industry Report by Bevy.
The same report says, “There’s a wide range of community platforms that companies use.” The most popular forums and messaging platforms, per the report, are Slack, Facebook, Discord, LinkedIn, Khoros, Salesforce, and Discourse.
And that doesn’t include the ever-growing list of other social media, events, video, and blog platforms.
No wonder it’s a common frustration for community professionals that they’re not able to access the data they need. Community is happening everywhere, but it’s impossible for community professionals to be everywhere at once.
Or, is it?
One of my favorite things about Orbit is that it enables you to pull in your community data from any platform and view it all in one place. Many of our customers describe us as “a single pane of glass” for their communities, and it all starts with getting data into the platform.
Then, once you have all your community data flowing into Orbit, you can consistently engage with community members, automate repetitive manual tasks, and even quantify the value of your community with reports.
But first, how do you get all the data in?
Here are 11 different ways to get your DevRel and community data into Orbit!
We’ve built a library of plug-and-play integrations that are completely self-serve. Just connect the source and watch the data begin flowing into Orbit.
Some of our most popular integrations are:
Even though the Orbit library of integrations is extensive, there still might be some sources of data for which Orbit has yet to build an integration.
As you’ll see below, we’ve covered every edge case.
The Orbit API allows you to send data to your Orbit workspace from the comfort of your own programs, apps, and tools.
This is the most powerful and most flexible option, but it will also require the most technical expertise.
Here are some capabilities of the Orbit API:
And here are some common use cases:
Zapier lets you define “triggers” from connected apps, then pass those straight into Orbit using our Zapier app’s “actions.”
For example, you can create activities in Orbit from new entries in Typeform. The Trigger is a new entry in Typeform, and the Action is to Create activity in Orbit.
Here are some of the most popular Orbit workflows with Zapier:
n8n is another workflow automation tool, like Zapier, but is open source and offers the technical user a lot more flexibility and opportunities for customization.
These are some reasons that users prefer n8n:
On the other hand, there are still some reasons to prefer Zapier:
If you opt for n8n, here’s the documentation for Orbit’s n8n node.
Make (formerly known as “Integromat”) is yet another workflow automation tool.
This is what Make says about how they’re different: “Traditional no-code integration and automation platforms are linear and non-intuitive. Make allows you to visually create, build, and automate workflows that are limited only by your imagination.”
Tray.io is another no- or low-code automation tool, but it’s more robust and typically better suited for enterprises.
They have many native integrations and a robust suite of tools to build workflows to connect to any other service with an API. Tray.io offers robust conditionals, logic, and sub-tasks that differentiate it from other automation platforms.
Tray.io doesn’t yet support a ready-to-use Orbit connection, but you can still connect to Orbit using the various advanced tools—script connector, webhook trigger, HTTP client, and more.
Workato is another automation tool that, like Tray.io, is better suited for enterprises.
There’s a relatively new development in the never-ending game of sending data back and forth between every app imaginable; it’s called “reverse ETL.”
“ETL” stands for “extract, transform, and load.” This is the standard process for taking data from a source, structuring it, and then sending it to a data warehouse.
Reverse ETL sends data in the opposite direction. It sends data from a data warehouse to a business application, like Orbit.
Companies store a lot of data in their data warehouses, so a process for moving that data into other apps can be very powerful.
Census is a reverse ETL tool popular among Orbit customers.
Hightouch is another reverse ETL tool, like Census.
Ultimately, the two tools seem comparable, and you can use either one to send data from your warehouse to Orbit.
All the options we’ve discussed so far have involved automatically sending data from other platforms to Orbit, but what if you want to manually add a one-off member or a one-off activity to your workspace?
For example, maybe you’re at a conference and you had an in-person conversation with someone. There’s no platform that captures that interaction, but you can still manually add that interaction to your Orbit workspace as a custom activity.
This is similar to the manual approach, but instead of adding members and activities one-by-one, you can add them in bulk.
For example, let’s say you talked to a bunch of people at a conference, so now you have a spreadsheet of the 50 different people you talked to at a conference.
You can import members and activities into Orbit via a CSV file (up to 5 MB per file).
Hopefully this has been a helpful overview of the various ways to get data flowing into your Orbit workspace. Before we wrap up, I’d like to leave you with two more thoughts about data in Orbit.
First, Orbit is a community growth platform that allows you to quantify the value of your community, engage with members, and automate repetitive manual community tasks.
Orbit is not a data warehouse, so we suggest that you only pipe in the data you need to achieve those community goals. Otherwise, your workspace will quickly become crowded and confusing. Not to mention, you’ll give yourself a headache trying to figure out how to cram the sum total of all your company’s data into Orbit.
Second, a note about our data model: Orbit is about members and activities. Everything you send to Orbit should either be about creating a new community member or adding an activity to an existing community member.
If you need any help getting your community data into Orbit, send us an email at [email protected].
If you’d like a demo, send me an email at [email protected].