Organization with Apps and Tags
Beyond a certain number of workflows, the clarity of organization does not happen in the editor but upstream: the choice of Apps, tags and names determines what you find, what you maintain and what the data exchange map shows. To create Apps and resources, see Resources.
How it fits together
Apps: group by system
Create an App for each external system you interact with:
Shopify(e-commerce)SAP(ERP)Mailchimp(marketing)
Each App groups the resources related to that system and feeds the data exchange map. Associate the App with the objects that touch the system:
| Element | Where to associate | Why |
|---|---|---|
| Triggers | "App" field | Identify the data source |
| HTTP nodes | "App" field | Identify the system called |
| Resources | "App" field | Group actions per system |
Tags: make search easier
Define a tag convention shared by the team, for example:
- By domain:
orders,stock,customers - By type:
api,batch,realtime - By priority:
critical,standard
When to use what
The naming below is a team recommendation, not a product rule: what matters is that it stays stable and shared so search and traces remain readable.
Triggers — [type]-[domain]-[action]:
api-orders-createfile-products-importcron-stock-sync-dailywebhook-payments-confirm
Workflows — [action]-[domain]-[detail]:
process-order-ecommercesync-stock-erpsend-customer-notification
Nodes — name the nodes of a workflow descriptively (Get order details, Validate amount, Send to ERP): a workflow with well-named nodes is much easier to maintain. Use Notes to document a complex part or visually group related nodes.
What to know before you start
Once created, the App name can no longer be modified and the App cannot be deleted. Choose your names carefully.
- An App is created for each system
- Tags are used consistently
- Workflow nodes are renamed
- Notes document the complex parts
Go further
See also: Resources