Introduction to Make.com and Bubble Integration
Make.com is a powerful integration tool and a great alternative to Zapier. In this bulk tutorial video, I'm going to show you how we can take data from Make.com. We've got other apps linked into it and we want to send that data into our Bubble app. Now remember that Bubble is incredibly powerful at just being able to receive data from other services but it may be appropriate to use something like Make.com or Zapier in the future particularly if they have an integration in with a service that doesn't have a public API. Let's dive into it.
Setting Up a Scenario in Make.com
If you want to watch more videos like this and you're learning Bubble then do click the link down in the description because we've got hundreds of Bubble tutorial videos just like this one on our website. So we're going to go into Make and set up a scenario. A scenario is a workflow or Zapier as APL would call it a Zap and I'm just going to jump straight to the key bit which is that you can basically have anything preceding this point and then you just need it to end in a HTTP request and we can say just make a request you know you can protect it otherwise but we just want to send data.
Creating a Backend Workflow in Bubble
So then we go into our Bubble app and we need to go into backend workflows. Because this is where Bubble is going to receive the data in so if we go new workflow and I'll call this make demo it needs to be public. You may find that you need to run without authentication and you need to run ignoring privacy rules it really depends on what you're doing with the inbound data.
Understanding Creator Fields and Privacy Rules
Just remember that when anyone as a current user in your app creates something they are automatically assigned the creator field on that data type and the entry in your database for that data type but remember if you trigger something to be created here as a result of the API data coming in from make.com there's no creator because there is no current user make.com has started off this workflow so there is going to be no creator field.
Setting Up the API Endpoint
So we can just say that we'll put this into detect data requests and say detect data and then I'm going to copy that I'll go through here and paste it in set as post and let's add in multi form and then let's add in our field so we'll say text and we'll say name value is Matt let's add in another item and we can say email I will say Matt at example.com.
Testing the API Endpoint
Now if I go back into Bubble I need in this mode here detecting request data notice that it's got initialize in there you only need that for this precise moment we need to remove initialize from make.com once we're done and also notice that you will work your backend workflows your API endpoints are specific to the version of the app that you're working with so let's go back into here and we'll say run once okay that looks like it was successful and go back into Bubble and not so successful there what is there an issue I look there we go something went wrong copying this across oh look at that's a bit buggy didn't select the whole thing there we go run save changes right no contains unsafe changes what's going on there it's been a while since I've used make make.com so what have I done here but yeah interestingly you can do it on intervals that's pretty cool ignore warnings module this module contains unsafe changes look there we go the data has arrived in.
Creating Data with Received Information
So what if I then want to create something with this data well I'd go data create a new thing and this is a demo app that I've used with loads of other projects video so we'll just go with contacts and we'll say first name and we go request data name that's it and email would be request data email.
Considerations for Privacy and Creator Fields
So few things to remember here remember that this contact that's created here does not have a creator field so you may want to consider adding in a manual creator field and doing a search for a matching it to the right user and then adjusting your privacy rules accordingly so that both if it's the Bubble creator field and the and the manual creator field the same rule applies remember if you do that you'll need to check the ignore privacy rules because you've likely got privacy rules stopping a search through all your users and making some sort of match like if you were trying to match the email address you'd need to have that field available to this workflow.
Finalizing the Workflow
The other thing to remember is that once we've initialized and we checked it so working we need to remove initialize because now it's actually in the state where this is just going to run when make sends any data to this API workflow this is what's going to happen it's going to create a new contact.
Conclusion
So there you go that's how you can take data from make and send it through to your Bubble app. If you've got any questions you've got any ideas or videos that you'd like us to create please do leave a comment and of course like and subscribe.