Customer record from an approved sign-up
Starting pointBuilds on the shipped template “Stripe Payment Workflow” (6 nodes), which you can find in the template library.
Create a Stripe customer only after the account team confirms the details.
- A prepare step builds the customer from the sign-up fields.
- The list action checks for an existing customer with the same email address.
- A human-input step shows the details to finance operations.
- On approval, the create action adds the customer.
Where the approval sits. The shipped template creates its customer with no check. The duplicate check and the approval are the changes. Assign the gate to someone other than the person who made the request, because the platform does not check that for you.
Daily balance note for finance
DesignedGive finance a short note of the balance each morning.
- The get-balance action reads the balance.
- A code node formats the figure for a short note.
- If the balance is below a level your finance lead sets, a human-input step asks them to look.
- The note goes to the finance channel with the Slack post-message action.
Where the approval sits. The workflow only reads. The Slack channel should be limited to people who may see the balance.
Duplicate customer review
DesignedFind customers that look like the same person and let a human decide.
- List customers.
- A code node groups likely duplicates by email address and name.
- A human-input step shows each group to a finance owner.
- The decision is recorded, and merging is done in Stripe by a person.
Where the approval sits. Merging is not in the shipped data, so the workflow ends at the decision.
- Shipped template
- A governed template with its approval step already in it ships in the platform.
- Starting point
- A shipped template runs the same actions. It is an integration test with no approval step, so you add the gate.
- Designed
- Design intent. It uses the actions listed above plus generic nodes, and nothing has been built as a template.