Streamline Workflows with Omeda’s Zapier Integration

    Recorded on: May 31, 2023

    Zapier lets you send Omeda data to and from thousands of the most popular apps, so you can automate your work and have more time for what matters most — no code or CSS necessary. Discover how to use Zapier to connect data between over 5,000 apps, including SalesForce, Google suite, Cvent, GoTo Webinar, and more to Omeda.

    In this webinar, we’ll walk through how to create form submission triggers and add customer actions in Zapier. Katie Robilotta, Product Manager at Omeda, leads the webinar.

    Download Slides

    See full transcript

    Speaker 1 (00:06):
    Hi everyone and thank you for joining. This webinar will be focused on learning how you can connect Omeda to all your favorite business apps using Zapier. My name is Katie Ribolitta and I’m a product manager here at Omeda. A little about myself. I joined the team about a year and a half ago, and I’m based in Chicago. I primarily focus on and manage a few of our products here, including form builder, data loader, and our APIs and integrations. The Zapier integration has been a huge once our client base and being a big Zapier fan myself, I’m very excited to have officially launched our initial version and look forward to continue to add to it as we learn more about what our users are looking to get out of this partnership. So let’s go over a few housekeeping items before jumping in. This webinar will be recorded and we will send out an email with this PowerPoint and recording. If you have any questions during the presentation, please feel free to drop them in the chat and we will respond back to you within the next 24 hours.

    So what will we specifically be talking about today? And basically everything there is to know about Zapier. So what exactly is it, how it works, what are the main benefits we see integrating Omeda with Zapier? More specifically what Zapier trigger and Action. Omeda has built out some examples of how our users are using Omeda with Zapier today, how you can get started. And lastly preview Omeda’s new Zapier trigger and action and show you exactly how it works. So for those who are not super familiar with Zapier, let’s get started with what it is. Zapier is a process automation platform that allows you to connect and send data from one app to one or more additional apps without needing to build out a custom integration or know how to code. They have over 5,000 apps now that you can instantly connect to including Salesforce, Shopify, zoom, GoToWebinar basically the entire Google suite and much, much more.

    And the way Zapier works is the apps you want to connect to or integrate with are broken out by a single trigger app and one or more action apps. So the trigger app is what sets off the event and where the data is originally coming from. So for example, someone submits a form built in jot forms that would be a, the trigger that will set off some type of action in another app. For example, let’s say creating a new contact record in Salesforce. So the trigger is a new jot form submission and the action is creating a new contact from that jot form submission in Salesforce. So now after that Zap is created, every time that form is submitted, a new contact record is created in Salesforce. And the best part, this integration can be built out within minutes, no code necessary using Zapier comes with a lot of great benefits like having the ability to connect AMIT to over 5,000 different apps without needing any developer assistance. Again, being completely code free using their Zap builder, which I’ll show you in a bit. You are able to select what data you want from your trigger app and map exactly where you want that data in your action app. Make sure the data ends up where it’s needed and once you turn your zap on the automation begins. So every time the event in your trigger app is triggered, the one or more actions set up will automatically take place without any assistance needed.

    All right, so let’s dig into what we at Omeda have done with Zapier. I’ll dive into a demo in a bit, but first I’ll give you all a quick overview of what we’ve created. So first we’ve created a new trigger called New Forms Mission. And basically what this allows you to do is send the form data from a single Omeda form submission to one of the 5,000 apps SAP supports today. So how this works is you select a single Omeda form in the Zap builder. We created an A P I where Zapier actually pulls all of your form builder forms and gives you the ability to search and select a single form within the Zap builder. And once you select which form you want your trigger set up on, Zapier will pull the last transaction made on that form. So you can take that form data and map those fields to your action app. The best part, there is no interaction needed with our Form Builder app. So you can build this app trigger without needing to log into meta and add something to your form or turn a certain setting on in order for this to work. Everything can be done within the zapp user interface.

    Next up, we’ve added a single action to add a customer to your meta database. So based on whatever trigger you have set up in another app, once that event is triggered, the data from that event can be mapped and added as a new customer or possibly an existing customer record depending on matching criteria and how your input is set up, which I’ll go over in a bit. This will media action allows you to map and bring in most, if not all, your standard fields. So name, address, email, phone, et cetera, plus up to 10 demographics, 10 products, 10 deployment types, and 10 behaviors. This action allows you to pick and choose what data you want to bring in from your trigger app into Omeda and easily map those data fields into your Omeda fields.

    I just wanted to go over a few use cases we’ve seen or thought of on how our clients can use our Zapier trigger in action before jumping into a demo. Again, there are many ways these can be used, but a few that came to top of mind that we’ve heard of are creating a new contact record in Salesforce from an Omeda, a form of submission. We know Salesforce is widely used and we’re hoping this helps bridge the gap between Omeda and a Salesforce, at least a little. There’s obviously more we can build out here. So this is just kind of the start, but some examples we’ve seen are lead gen forms created within Omeda and wanting that seamless automation to create that new contact or a lead in Salesforce. Another example is, you know, kind of the same idea but updating a campaign in Salesforce with a new lead or contact from an Omeda forms mission. And lastly, if someone schedules a demo on Calendly, that contact information is automatically sent straight to Omeda’s database and created as a new customer. Again, the use cases could be endless, but these were just a few examples of what we’ve heard clients wanting to use Zapier with Omeda that I wanted to touch on.

    So what do you need to get started? Besides the obvious of having an Omeda and Zapier account, you will need to open an Omeda support ticket to obtain a few items in order to authenticate your Omeda account and Zapier, the ticket should be created as an API support ticket asking for the following authentication information to connect Zapier, that’s your client brand abbreviation your encrypted Omeda input id, a new API key. And if you are using the Omeda add customer action, you’ll need to provide a short description of the data you plan on bringing into Omeda from Zapier, including the type of contact information which will help us determine what customer matching type we should set up on input. Meaning if an incoming customer already exists in your database, how should we match the incoming record with the existing one? For example, if you’re only collecting email address in your trigger event, then we can use a match by email only.

    If there’s more information you are collecting around the customer, then we can use that additional information to do more detailed match against existing customers. So knowing what type of contact data you’re bringing in, the support rep will be able to create the right type of input for your zebra use. Another important item to provide in the ticket are products if you plan on bringing in to Omeda, if any. So if you plan on bringing in magazine subscription data for example, we’ll need to know if you’d like, you know, the specific processing rules or validation rules set up on the input. If you plan on bringing in multi mag multiple magazine products, there may be a chance we’ll need to create multiple inputs for each magazine product. If the processing rules or validation rules required are different, this means you’ll most likely need to set up different meet accounts in the Zapier action. So you know, one account for each input, which I can show you in the demo.

    I just wanted to quickly mention that we do have what I just went through, documented in our knowledge base, like what you’ll need to include in your sport ticket, how to create a Zap using Omeda’s trigger in action. I also just wanted to quickly mention this formatter by Zapier action at the bottom here. I don’t wanna dive too deep into it right now, but feel free to take a peek at the documentation or ask a question in the chat. Basically Omeda stores demographics deployment types and products responses in your database as defined IDs to keep the data clean so you don’t have these arbitrary values all over the place, right? So when bringing data in from another source like Zapier, it is important that the incoming data matches these designated value IDs. So that’s kind of where this formatter by Zapier actually comes into play. If these Omeda response IDs are not already set up in your trigger app to send, then this action is a really great way to transform demo deployment type and product response values from your trigger app into the designated Omeda response value IDs before sending to Omeda, keeping your data clean.

    Again, everything is documented here and if you have further questions after this, please feel free to reach out to the support team. All right, it is time for the demo. So I’m gonna take you through our new form submission trigger. First, let me move over there. Okay, so I’m in Zapier and I’m going to create a new Zap and my use case here is going to be I want to use an Omeda form as my lead gen form. I’m collecting some leads and I want to send that over to Salesforce. So let’s create our Omeda trigger.

    Our event is that new forms mission and here is where you’re going to use that information from that support ticket to authenticate your Omeda account into Zapier. Here you can have multiple, you can create multiple, but this is where you’re going to add your brand abbreviation, your input ID and your API key. We’ll select a form and this is the API that pulls all your form builder forms into this dropdown where you can search for easily continue. And I’m going to test this trigger and what this is gonna do is take that last transaction made on that form you just selected, making it super easy to grab all of the fields from your form and the data so you can easily map it into your action. And so you can see all these fields that are in my form and we made it easy to kind of, you know, to see what type of fields they are.

    So we have our Acme third party and that’s, you know, a deployment type. We have our Acme job function, that’s our demographic and we have a couple products here making it, making it a lot easier for you to know what the data is and how to map into the action. So that’s pretty much it for the form submission. Super easy, we’ll continue and now we’ll show you how this looks, sending it to Salesforce. So we’re gonna create our Salesforce action, which is going to be, we’re gonna create a new contact I have to authenticate with your Salesforce account as well. And here is kind of those standard fields that you have on your contact record in Salesforce. So these are all your Salesforce fields that you’ll see here on your contact record. And you can take, you can take those Omeda fields from your trigger and map them to your Salesforce. So I’m gonna search for my last name. So that’s my last name field from that form, Metaform coming into Salesforce.

    Now I’ll just select a couple fields here. We’re not gonna fill out everything and that’s the beauty of this. You can ignore the fields that you don’t need. We’ll do our email address. And I think that’s all we’ll do this time continue. And this kind of just shows you what information you are sending over to Salesforce from your trigger and you can test that action to make sure everything is okay and that, that the data sends and you’ll get a success message saying that contact was sent to Salesforce. And let’s just make sure that we see our, yep, our Katie OT record just came through to our communication account and we can see that the information that came through, which is the first name, last name, and email.

    So once you have a successful test, you can publish that Zap and now every time a user goes to that Omeda a form and submits it, that data will be sent directly to Salesforce exactly how you just mapped it. So that is just a quick overview of our form submission trigger. Super easy to set up. Now let’s take a look at our Omeda action. So we’re gonna create another app and this use case will be kind of be like reverse. So we’re gonna have a jot forms form submission sent to our Omeda database now. So our trigger will be that jot forms form. So we’re gonna search for drop forms. This is gonna look very similar to our media form submission. Select a new submission, new gonna have to authenticate and we select a form. And this also pulls, pulls your last transaction that was made and you can preview what data was within that last trans transaction and all the fields included on that form. We just have phone number, email, first name, last name, it’s going to continue. And now we’re gonna search for our Omeda app in our action.

    And this is the add customer event. Again, once you authenticate once, you won’t have to do it again. So you’re already authenticated do it again. And here, just like we saw in Salesforce action, it’s all your standard fields that you can map that jot forms that data to your OMI a. So let me do my first name, last name, and I think it was just email address. So we’ll add that. I believe there was a phone number too, so we’ll that in there as well. Okay. And this just has our, all our standard fields to create a contact record. And like I said, we have up to 10 demographics you can map up to. So if you have demographics on your trigger event, you can map that. And what this does is this pulls all your demographics in your database so you can select which one you want to map to.

    So let’s say our job function and then this is where you’re going to map the response from your user from that trigger event. So you get to pick your, you know, demographics, pick what your response is, and then if you have other write-in as well. A couple things to note about the demographic, the products and the deployment types. This is where that formatter by Zapier can come into play. If you don’t already have your Omeda values mapped in your trigger event that formatter by Zapier action would go before this action, before your Omeda action in between your trigger and Omeda. And what that’s gonna do is transform those values coming from your trigger and transform them into your Omeda values. It’s very easy to set up. Again, it’s in the documentation, you can take a look. But I don’t have a demographic on my form so I’m just gonna clear that out for now. But you’ll see there’s up to 10 demographics you can map up to.

    You have up to 10 products. So this will pull all of your products that you have in your database that you can choose search and select for. And then again, same idea. This is where you’re gonna map the receiving field. And if you want to do requested version as well, it’s optional. Here’s your deployment types. You have up to 10 deployment types you can map up to. Again, this pulls all your deployment types from your database and this is where you’re gonna map those values. And lastly, you have behaviors you can map. So this will pull all of your behaviors you have listed in your database along with the attribute types and attribute values as well. So we’re gonna continue we’ll see that we have a little overview of what we’re mapping from Jot forms to Omeda. And then these are just kind of a list of MD fields that we’ve decided to ignore for now. And now we’re going to test that action.

    And this was a success. A customer was sent to me about one second ago, so now I can go ahead and publish that Zap. So now every time I use your code to that Jo Forms form fills it out, that’s gonna send us a new customer into our Omeda database. So that kind of wraps up our demo. So I really that this was helpful and if you have any further questions, please feel free to drop them in the chat here or reach out to your CSM or support rep. Again, we have everything I just went over and more in our knowledge base that can help guide you if you become stuck. And if you have any other ideas on new Omeda triggers and actions that you feel you know many could benefit from, feel free to drop, drop them in our ideas board in the portal. I would love to hear about all your different use cases. And thank you all so much for joining. Can’t wait to hear about or see how you all are going to use Omeda Zaps in the future. Thanks all.