Hacker News Reader

I’m curious how this is different from Zapier which has added a conversational layer (https://zapier.com/ai).

In my experience a lot of people don’t know how to write with a level of specificity needed to map to pre defined triggers.

For example: instead of saying spreadsheet they may say “roadmap” or instead of saying “Notion database” they may say “bug tracker”

This stuff fails in Zapier.

Any chance you handle those cases better?

View on HN

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.

"Roadmap" works sometimes, but there's definitely some guess-work. Clarifying with followup questions in chat is pretty valuable, and we're considering presenting the user with multiple plans to choose from when we're unsure.

Reply on news.ycombinator.com