[lolinder]

They already address that specifically:

> We found current workflow / automation tools like Zapier and n8n are good for simple tasks, but not for more advanced use cases.

This isn't intended to replace Zapier for your use case.

Speaking as a developer who's been asked to set up integrations before, I'm glad to see more competition in this space with a developer focus!

[robbiemitchell]

The first example on the homepage is "Create an email drip feed campaign in under 2 minutes"

This is not an advanced use case to be developed in house and owned by developers. This is bread and butter marketing or product engagement email flows using anything from Mailchimp to customer.io to HubSpot.

The developer side would involve capturing the identities and events from your system and sending them (typically via something like Segment) to the downstream tools, where business users will manage those campaigns: flows, templates, content, integration with other flows, and reporting.

The next example is "Sync GitHub issues to Linear". Again, this is a fairly simple Zapier use case, probably using built-in integrations, or falling back to Python if needed. Zapier would store the credentials to both security and use a trigger/action flow.

I can see trigger.dev being more useful for things like:

- Schedule-based tasks, or super high-volume tasks. (These are expensive on platforms)

- That are driven primarily by code, not pre-built integrations

- Using private data (such as authorization tokens) you don't want to expose in plain text

Given there is undoubtedly a market of developers who want to bring things back into their standard codebase and code release practices, I suggest targeting the examples to situations to those more typically owned by developers.

[mattaitken]

Thanks, this is great feedback. You're right that these examples don't highlight the real advantage of our platform vs no-code tools. We're going to add some new examples to our site based on what our customers are building.

The three categories of problems you identified that are best solved with a code tool are what we're seeing with our early customers. Plus a lot of notification use cases like when developers want to be notified in Slack when something important/bad happens.