Hüseyin Yücel
TürkçeContact

Example flows

Each example comes with a working model. Run it and see how it works.

  1. Approval flow for purchase requestssample project

    Purchase approvals that used to be chased over e-mail move to Teams. They reach the right people based on the amount, and the result is logged in the list and the ERP on its own.

    2026, Power Automate, Microsoft Teams, SharePoint

    Run the model
    Working modelHow does a purchase request get approved?Sample data. The model shows how the project works.
    What does Ayşe want to buy?

    Requests over 50,000 TL go to the finance director after the line manager.

    1. Request opened
    2. Manager decision
    3. Finance decision (over 50,000 TL)
    4. Logged and sent to ERP
    5. Requester e-mailed

  2. Automatic processing of incoming invoicessample project

    Invoices arriving by e-mail are read and checked against the order. Matching ones are posted to the ERP on their own, differences go to accounting for approval, and duplicates are caught.

    2026, Power Automate, Outlook, AI Builder

    Run the model
    Working modelHow is an incoming invoice processed?Sample data. The model shows how the project works.
    Which invoice arrives?

    If the invoice differs from the order it goes to accounting for approval. The same invoice is never posted twice.

    1. Invoice arrived by e-mail
    2. PDF read
    3. Checked against the order
    4. Accounting approval (if different)
    5. Posted to ERP or returned

  3. Payment reminders and receivables follow-upsample project

    Open receivables are scanned every morning. Upcoming due dates get a gentle WhatsApp reminder and overdue ones a payment reminder. When payment arrives the account closes, otherwise finance gets a call task.

    2026, Power Automate, WhatsApp Business API, Bank integration

    Run the model
    Working modelHow are receivables followed up on their own?Sample data. The model shows how the project works.
    What will the late customer do?

    Accounts due in 3 days get a gentle reminder, overdue ones get a payment reminder. Nothing goes to accounts not yet due.

    1. 09:00 morning check
    2. Reminder for upcoming due date
    3. Reminder for overdue
    4. Payment or follow-up task
    5. Account updated

  4. Leave requests and team calendarsample project

    Leave is requested from a form. Balance and team calendar are checked on their own, and the manager approves in Teams. Calendar, balance and HR records update.

    2026, Power Apps, Power Automate, Teams

    Run the model
    Working modelHow does a leave request move?Sample data. The model shows how the project works.
    When does Emre want time off?

    Requests over the balance never reach the manager. If a teammate is off on the same days, the manager sees a warning.

    1. Request form filled
    2. Balance and calendar check
    3. Manager approval
    4. Calendar, balance and HR updated
    5. Employee notified

Thinking about something similar?

Tell me about it →
esc