Workflow guides

These guides turn common customer journeys into complete workflow designs. Each matching draft lives in App User Guides (service 20) and opens at 100% with the trigger visible. Every guide starts from a blank workflow, adds and configures its trigger, then adds each action in execution order with an annotated crop of the real configuration drawer.

The examples are deliberately unpublished. Some require a local form, DataHub source, document template, recipient, calendar, workspace, or managed credential. Complete those highlighted selections, test with synthetic data, and review side effects before publishing.

Choose an example

1. Triage a customer request — declare manual inputs, classify text, branch by category, and notify a team.
2. Send a scheduled DataHub health digest — query, aggregate, format, and email on weekdays.
3. Review and approve a form submission — pause for a decision, generate a record, and send the result.
4. Acknowledge a signed order webhook — verify, normalise, validate, and respond.
5. Synchronise a DataHub customer record — watch meaningful changes, reshape data, and update an item.
6. Kick off a new project task — create a calendar event, notify the team, and update the task.
7. Hand off a creative asset — export a design, link the asset, and notify content owners.
8. Send a booking reminder and collect details — calculate time, wait durably, notify, and request data.
9. Build a resilient API synchronisation — poll, call, recover, back off, and log.
10. Create a parallel feedback digest — run two AI analyses, join them, and return a stable result.

How to use a guide

Duplicate the matching workflow inside service 20 when you want to experiment without changing the documentation fixture. Work through Before you start, Build the workflow from start to finish, Test the workflow, and Production checklist in order. Select Save in every trigger or action drawer before returning to the canvas; the workflow structure autosaves, but an open configuration form still needs its own Save action.

The example IDs are 583–592. IDs are useful for locating these local fixtures, but expressions should refer to stable node labels selected through the expression picker.

Shared release standard

A guide is ready for production only when:

• the trigger is scoped to the intended service event;
• every environment-specific resource is selected;
• test data contains no real customer information or secrets;
• dry runs prove transformation and routing;
• a deliberate live test proves customer-visible side effects;
• Problems is empty;
• run history shows expected resolved inputs and outputs;
• a second service owner has reviewed the workflow.