Albato Reviews

At first it seemed like a great alternative to Make. I was told there would be a team functionality coming "soon"... that was almost a year ago! It's the only reason I moved over from Make. Albato started development on Team feature 4 years ago!!! Every time I ask about it, all they will say is "our team is actively working on it", first it was "we expect the release at the beginning of next year [2026]" then in May 2026 it was "Teams functionality is already in the final stage of testing... and we hope that it will be available to everyone soon." Soon...? mkay! So let's not hold our breath. The other reason why I thought Albato can compete against Make, is because, though they don't have as many native connections, they boast about their custom app builder. And you will need to use it because even the native apps are missing a lot of API connections. For example; all my clients use Google Shared Drive but Albato native Google Connection only uses My Drive. Absolutely useless for any real business use case. I am pretty good with tech. I work for a Saas company. BUT you will need a developer/engineer degree to use their custom app builder. Support will just point you to their documentation because they are not trained in how their app builder work or they tell you to email the "App Integrator support team"... except they have not once returned my emails. So in the end if you cannot figure it out with the help of AI, you just give up. Knowing what I know now, I would not have invested in Tier 4. Unfortunately I cannot get a refund.

I was really excited about Albato at first—its interface is clean, the automation possibilities look great, and the idea of streamlining my workflow sounded perfect. Unfortunately, the reality falls short because it just doesn’t integrate with the tools I actually use.

One of my go-to apps is has no native integration. I saw a feature request it posted over nine months ago on their request‑feature page, and there’s still no update or response. The only workaround is to use an HTTP, which is clunky, confusing, and ultimately didn't work at all.

When I reached out to Albato support to explain the issue, the reply was simply to point me to Hiro's documentation - when I told them that my assistant and worked on this for 6 hours yesterday (don't ask why) and that it still didn't work even with the documentation they provided from their site the response was: “I’m sorry for your frustration.” No apology for the poor instructions, lack of support despite this being a common thing users have to do, no acknowledgment that following the API docs from both Hiro.fm and Albato’s automation doesn’t actually work despite following instructions, and no indication that they’re planning to add Hiro.fm support.

They even told me they don’t offer support for this "custom" automation at all. I'm sure this isn't the only app that they don't support that you have to use this workaround for, so to give zero support is kind of ridiculous.

Albato looks great on paper, but the functionality isn’t ready for real‑world use. Unless someone can help me get a pretty basic automation that works flawlessly in Zapier working - or they add it soon, this app is pretty much useless for me and for any apps that don't have API integration, it's a pain.

----

UPDATE: After this review Albato Support responded and it was a REAL issue with the set up of HTTP (for apps that don't have API Integration) They were able to resolve my issue. Dropping my additional feedback here. TL:DR - gorgeous interface, automations work pretty flawlessly with API, but HTTP is not intuitive...and there are a few sticky issues with choosing products, with Thrivecart, specifically.

---
The platform does work. The AppSumo deal is real — 45,000 ops/month and unlimited automations for a one-time fee is legitimately strong. Once the automation was correctly configured, it ran cleanly and consistently. The core architecture (trigger → filter → action) makes sense and the ops tracking is accurate.

What I found:
The documentation does not match the actual UI. Albato's own wiki on the incoming data filter showed instructions that, when followed exactly, caused the filter to fail every single time. The documentation described placing a dynamic field chip into the comparison value — but Albato's filter silently rejects any run where the value field contains a chip rather than plain text. Following the official docs broke the automation. The correct behavior had to be discovered through trial, error, and platform inspection.

Filter failures are logged as "Success." When the incoming data filter blocks an automation run, Albato marks it as Success in the history log. The message buried in the detail is: "The automation executed, but the data didn't meet the filter conditions." This is misleading at best. A filtered run is not a success — it is a non-execution. Labeling it "Filtered" or "Skipped" would tell users immediately what happened. Calling it Success caused repeated confusion about whether the automation was working or not.

The HTTP Request step requires API knowledge that is not disclosed upfront. When you need to connect to an app that doesn't have a native Albato connector, you use the HTTP Request (Outgoing Webhook) step. Albato does not tell you that this step requires you to know:

The correct API endpoint
The correct request method
The exact field names the API expects
The correct Content-Type header (application/json vs. application/x-www-form-urlencoded — using the wrong one produces a 400 error with no explanation)
That the Authorization header must be manually added — the connection does not handle authentication automatically
None of this is explained anywhere. If you don't already know how REST APIs work, this step is not functional for you without outside help.

The platform works, and the AppSumo deal is worth it if you are migrating standard app-to-app automations. The ops allowance alone MORE than justifies the lifetime price. The platform works, and the AppSumo deal is worth it if you are migrating standard app-to-app automations. The ops allowance alone justifies the lifetime price. But if your workflows require HTTP Request steps — connecting to APIs without native Albato connectors for a steep learning curve that they technically don't support. What should have been a quick setup took 10 hrs , required 41 test purchases, and was ultimately solved by using AI to figure out what the documentation should have said.

I really wanted this to work for my automation needs, but unfortunately, it just wasn't the right fit for me.

My experience with the platform was disappointing, and the customer service didn't help resolve the issues I was facing. Because it didn't meet my expectations or needs, I had to request a refund immediately.

Good luck to the team with the continued development of the product, but this definitely wasn't for me.

I've found Albato to be a powerful and reliable alternative to Zapier. Support is good and most importantly it is being actively developed - feature requests are actually delivered. Unlike another automation tool I bought here on Appsumo, Albato are keeping their promises and not re-mapping Summolings to lower value plans. Trust goes a long way.

I've been using Albato for my automation needs and I'm genuinely impressed by both the platform and the team behind it.
As someone managing multiple client projects with complex integrations, I needed a reliable and flexible solution. Albato delivers exactly that – intuitive, powerful, and dependable.
What truly sets Albato apart is their customer support. I ran into some issues while connecting third-party applications, and the team went above and beyond to help.
A special thanks to Pedro – his patience and expertise were exceptional. He took the time to understand my setup and walked me through the solutions. This level of dedication is rare and makes all the difference under tight deadlines.
Highly recommended!
Walter