The full renewal pipeline

1. The full renewal pipeline

You've built every piece of a production-grade renewal pipeline - triggers, data actions, branching, approvals, error handling, and audit trails. This video assembles them into one flow and names what makes it production-ready.

2. The pipeline, end to end

Here's the whole flow on one slide. The Recurrence trigger fires every weekday morning. Get items pulls the contracts coming up for renewal from the SharePoint list. Apply to Each loops over them. Inside the loop, Get file metadata pulls the SharePoint document reference. Get user profile resolves the responsible partner's email from the owner field. The Condition on contract value splits high-value from standard. High-value routes into an Approval with custom responses; standard goes direct. Switch on status picks the matching template. Send an email fires, with a parallel run-after branch handling failures. And Update a row writes the audit trail back to the Excel workbook.

3. What makes it production-ready

Production-ready isn't a single quality, it's a checklist. Start with a real end-to-end test from the actual trigger, not just Test flow with a static payload. Make sure at least one other maker is a co-owner who can step in after a handover. Every action that talks to an external system should have a Failed run-after branch that logs what went wrong. The audit trail needs to be writing back to Excel so duplicate runs don't fire duplicate notifications. And before you walk away, confirm the trigger is on and the next scheduled run time is what you expect.

4. Test, then turn it on

The last steps before handover are mechanical but important. Trigger the flow manually one more time and watch every action turn green in run history. Open one of the runs and inspect the output of each step to confirm the email actually sent, the Excel audit row actually updated, the approval actually routed. Then turn the flow on and check the Next scheduled run timestamp. If it says tomorrow at eight, the Recurrence trigger plus the weekday condition is wired correctly. If it says something else, fix it before you walk away.

5. Common mistakes worth a second pass

Three things bite real makers more than anything else. The Outcome casing, capital A on 'Approve'. A lowercase comparison silently sends every approval to the wrong branch. Single ownership, where a flow with one owner dies the day that person leaves. And connection ownership, where every connection is tied to the user who created it, so when they're offboarded, the flow fails authentication. None of these are obscure. They're the bugs you'll write yourself in your first three production flows. Watch for them.

6. Let's practice

Now it's your turn. In the next exercise you'll assemble the full renewal pipeline from trigger to audit trail - every piece you've built across the course, wired together end-to-end. Let's see how it comes together.

Create Your Free Account

By continuing, you accept our Terms of Use, our Privacy Policy and that your data is stored in the USA.