samuelbrashears

"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.

Definitely something we're looking at -- do you have more any details about your use case?

Before creating a workflow, we present you a plan that you can confirm, so we won't delete stuff without your approval.

We've opened everything up to free tier for the launch! And thanks for the suggestion :)

Interesting -- we've definitely been building only on top of APIs. We've looked at automated form filling in the past, so it's something we're thinking about.

Great idea -- we're looking at showing workflow history and this is a good addition.

We do a fixed number of retries, including redoing any AI arguments. We've thought about making it atomic/more durable -- it's tricky, given that most steps interact with external systems e.g. Google Sheets, and while not typically "destructive" (Google Sheets has version history), undo-ing is often difficult.

1. Yes! This is useful for parsing unstructured data or inferring an argument (sometimes we can simply define a static data transformation through jq).

2. Anything too complex (e.g. 5+ steps) tends to be unreliable. Also, any workflow where potential failure/unexpected behavior is too risky to leave up to an LLM.

3. The only actions we take are with our user's tools, so many workflows are simply organizing their information between their apps. However, e.g. gmails could be sent externally so we have guardrails/sanity checks to mitigate risk there.

Zapier is definitely trying, but they're not there yet. That feature unfortunately doesn't do much to configure the blocks for you (it just selects which to use) -- you're largely left to sift through the same menus to set it up.

Zapier is working on something very similar! We actually did our live launch at the same event as them for their new chat product -- https://central.zapier.com/. We think our UX is actually a lot simpler than there's is at the moment, since they're focusing on fine-grained control.

Also, the best way for them to do this would be pretty close to a ground-up rewrite -- both in terms of frontend/interface, but their model of integrations/connectors is not really compatible with allowing AI to take a bigger role in data transformations.

Zapier is already trying! We actually did our live launch at the same event as them for their new chat product -- https://central.zapier.com/. At the moment though, they're pretty focused on fine-grained control and GUI configurability, which makes a lot of sense for their existing technical user-base. We're focusing on a super simple UX for less technical users.

Really cool demo! Having it available right inside of Slack seems nice.