Why integrations matter
Integrations are what let workflows interact with the rest of your tool stack. They are how Workflow Machine moves beyond internal logic and becomes useful in day-to-day operations. Integrations make it possible to receive input from apps, send actions into apps, and coordinate work across several systems.Two main roles: triggers and actions
Integrations usually participate in workflows in one or both of these ways:- Triggers start a workflow when an app event happens
- Actions let a workflow do something inside an app
How to choose the right integration
Start from the workflow outcome, then choose the app that best matches that job. Ask:- where does the event begin
- where should the result go
- which app owns the source of truth
Connections come first
Before an integration can be used in a workflow, you usually need a connection for that app. That means:- authenticating the account
- choosing the correct workspace or environment
- making sure the account has the permissions the workflow needs
Use integrations intentionally
The best workflows do not use many apps just because they can. They use the fewest apps needed to get the right result. That keeps workflows:- easier to test
- easier to maintain
- easier to troubleshoot
How to use the integration pages
Each integration page in this section helps you answer:- what the integration is good for
- what kinds of workflows it supports well
- what connection setup is required
- what common problems to watch for