Great question! As of now, we handle those cases well since we have 14 integrations, and most words/phrases are easily resolvable to a sequence among them. One thing we're focusing on now that will be more important with a larger scale of integrations is making automation creation conversational, so when there's uncertainty we can clarify in chat with low latency to keep time to value minimal.

We think one of the big differences between Zapier and DryMerge is that we abstract a lot of the data flow/configuration away from the user, which lowers time to value and lets us do cool semantic filtering and other LLM-powered backend stuff.

Awesome resource! Thanks for pointing it out

Awesome! We're rolling out Microsoft 365 really soon, starting this week :). Would love to hear about what services and workflows are most important for you.

Great question! First off, we absolutely love the guys at all those companies, they're building awesome stuff.

DryMerge differentiates by focusing on plain english chat as an interface. The reason that's important is because it's accessible to more non-technical folks, lowers time to value (a lot easier to say what's on your mind than drag & dropping/building), and allows for cool semantic filtering like "Angry emails", "Investor", or "Potential customer" which we've found opens up a whole bunch of cool new possible automations. We also heavily focus on event-driven workflow automation (we have a lot of triggers).

Appreciate it, and glad to hear you like it :). That's a great point, we've experimented in the past and it's a tricky balance between making sure there's no false negatives (actual workflows that we can automate get denied), so we defaulted a little more permissive, but we're gonna take another crack at it!

Thanks! And 100%, this is something we'd love to do with upmarket businesses. We have primitives for integrating raw API calls into the workflow layer as well as ingesting documentation to create dynamic "blocks" per-business, so it's fully possible and a really cool use case. Definitely agree though -- it's hard to get right.

Great point! Multi-lingual is entirely possible and something that we want to implement; luckily all the chat stuff already works great because of LLMs, and we'll try to ship multi-lingual UI elements fast as well.

Appreciate it! We think the most important thing for a product like this is minimizing time to value, so glad to hear the sign-up is smooth :)

Thanks, and totally agree! We play around a lot with the idea of creating an action layer for LLMs that's abstract enough for sampling/inherent stochasticity not to cause too many intermittent failures. I think when that infrastructure's solid, it'll be really easy for integrators to deliver cool functionality (as you said :) )

Haha so originally we were in dev tools, and we liked the idea of merging APIs without hassle. So we thought a fitting name was something like DRYMerge (Don't repeat yourself, merge). We really liked the name and decided to keep it after our pivot.

I took it to mean safety (it doesn’t do anything to your data without showing you what it’ll do first, e.g. an initial dry run.)

Seems like a cool tool; I’m looking forward to playing with it.

I really like this interpretation actually, I'll stick with that when people ask what it means nowadays!

imo its not a good name for your new target customer, but names are less impt than quality of product