I ask because this is in their documentation: Boost. space has its own OEM instance and uses the Make.com engine to create integrations/connections. We have also implemented a fair usage policy for scenarios within Boost. space in cooperation with Make.com.
Since PickAxe doesn’t have an API then we can connect our custom PickAxe Apps that are integrated in the Boost.Space software via the Make.com actions? It will use the outside app to create the results for our users then send the completed data/request back to our custom PickAxe App?
Hey @rainmaker it could be feasible to use Boost. space for actions similar to Make.com, given their shared technology and comparable features.
However, I can’t give you a direct answer without seeing a workflow chart of what you intend to do. Send it my way via DM and I’ll take a look at it with my team.
I’m not familiar with Boost. If Boost is an automation tool similar to Make and uses a simple webhook, then you can set it up via our generic webhook action. Under the hood it’s the same as the Zapier/Make actions.
Cool, when you use Boost.Space with your PickAxe Studios you use the Basic Make Webhook instead of the Basic Generic Webhook? Is one easier than the other or do they basically operate the same way?
Basically the use is the same, all actions that say “webhook” send an http request and wait for a response. It doesn’t matter what action you choose as long as it says “webhook” you can connect it to make, zapier, n8n, boost.space etc. the use is the same
Yes, @ab2308 I figured it out already and what you are saying is the best route. I am using a Generic Webhook in my P.A. then in Boost Space I just added a custom webhook and router connected to the Apps I need
I wish I could answer that, but I’ve never used Make. I have only used Albato and now Boost Space. The only other one I tried was API-X Drive for workflows. I kept Albato and Boost Space because they have more integrations, but I hear good things bout Make. I can’t do a comparison yet until I utilize Make. Boost Space is partnered with Make, and you can use Make in the workflows. - Make Visual Workflow Automation Platform | Boost.space.
Boost is a ton Cheaper and its the exact interface that Make has. It is make. And they sold it as a lifetime deal. So, in my case I have 300,000 operations each month and no monthly fee.
Are you using a single boost account for all of your actions? You would need separate Boost accounts to connect appropriate modules if you function as an agency. Am I wrong about this? Still trying to get my feet wet with Boost.space.
How many LTDs of Boost did you purchase if you don’t mind me asking? 10 for 10 clients? or do you use 1 account for 10 clients so 10 would equal 100? There is no LTD running currently I am aware of but it could always come back on platforms.