5 exercises — master the vocabulary of workflow automation: triggers, connectors, conditions, human-in-the-loop approvals, error handling, and idempotency.
0 / 19 completed
1 / 19
A business analyst is designing a Power Automate flow. They ask: "What exactly is a trigger, and what are the main types I need to know?"
Triggers are the foundational concept in all workflow automation platforms — choosing the wrong trigger type is one of the most common design mistakes in flow development.
The four main trigger types:
Trigger type
When it fires
Power Automate example
Event
When a specific event occurs
"When a new item is added to SharePoint"
Scheduled
At a fixed time or interval
"Recurrence: every Monday at 8am"
Manual
When a user initiates it
"Manually trigger a flow" / button in Power Apps
Webhook / HTTP
When an HTTP POST arrives
"When an HTTP request is received"
Trigger selection implications:
• Event triggers run immediately on the event — best for real-time automation
• Scheduled triggers include a built-in delay; avoid for time-sensitive processes
• Webhook triggers enable external systems to start Power Automate flows — the most powerful integration pattern
• Manual triggers bypass automation entirely — useful for user-on-demand processes or testing
Key vocabulary:
• Trigger — the event that starts a workflow execution
• Webhook — an HTTP callback that allows external systems to push events to a workflow
• Recurrence trigger — a scheduled trigger that fires at a defined interval or specific time
• Polling trigger — a trigger that periodically checks for new events (e.g. checks for new emails every minute)
2 / 19
A developer joins a Power Automate project for the first time. They see the term "connector" used throughout the documentation. "What is a connector and how does it work?"
Connectors are the building blocks of Power Automate — understanding what they abstract away is fundamental to designing, troubleshooting, and governing low-code automation.
What a connector encapsulates:
① Authentication handling (OAuth 2.0, API keys, basic auth — the connector manages token refresh)
② API endpoint configuration (the base URL, API version, headers)
③ Typed triggers and actions with defined input/output schemas
④ Rate limiting and retry handling
⑤ Data type mapping between the external API format and the internal Power Automate schema
Connector tiers:
Tier
Examples
License
Standard
SharePoint, Outlook, Teams, Excel
Included in Power Automate plan
Premium
Salesforce, SAP, ServiceNow, SQL Server
Requires Power Automate Premium plan
Custom
Internal APIs, proprietary systems
Built by developers; requires Premium
Why connectors are a governance concern:
Each connector establishes a data flow between the organisation and an external service. Unapproved connectors can send sensitive data to services that haven't been reviewed for security compliance. The CoE (Center of Excellence) maintains an approved connector list and blocks non-approved connectors via Data Loss Prevention (DLP) policies.
Key vocabulary:
• Connector — a pre-built integration wrapper for a specific service, handling auth and API communication
• Standard connector — included in base Power Automate enterprise license
• Premium connector — requires Power Automate Premium license; for enterprise SaaS platforms
• Custom connector — developer-built connector wrapping an internal or third-party API
• DLP policy — Data Loss Prevention policy that controls which connectors can be used together
3 / 19
A workflow is described as: "When a form is submitted → check if budget > $10,000 → if yes, send approval email to VP → wait for response → if approved, create PO in SAP." What workflow automation concepts are illustrated in this description?
Identifying the individual workflow components in a business process description is an essential skill for discussing automation design with mixed technical and business audiences.
Component breakdown:
Step
Concept
Power Automate control
Form submitted
Trigger (event)
Microsoft Forms / SharePoint trigger
Check budget > $10k
Condition
Condition control (if/else)
If yes, email VP
Branching + Action
True branch + Send email action
Wait for response
Human-in-the-loop approval
Start and wait for an approval action
Create PO in SAP
Action (integration)
SAP connector action
The human-in-the-loop approval pattern:
This is the most important enterprise workflow pattern. The workflow pauses indefinitely and stores state until a human responds. This creates an "approval inbox" where the VP can approve or reject from email or Teams. The pattern enables human governance of high-value automated transactions without slowing down the workflow for routine approvals.
Key vocabulary:
• Condition — a branching control that checks a boolean expression and routes to yes/no paths
• Human-in-the-loop — a workflow pattern that pauses for human decision before proceeding
• Approval step — a flow control that sends an approval request and waits for a response
• Branching — forking the workflow into different paths based on a condition result
4 / 19
A workflow keeps silently failing in production. A developer investigates and realises there is no error handling in the flow. What is an error handler in workflow automation, and why is it a best practice?
Lack of error handling is the most common production failure mode in citizen-developed flows — understanding error handling vocabulary is essential for building reliable automations.
What happens without error handling:
① External API call fails (service down, authentication expired, invalid data)
② Power Automate marks the action as failed
③ Subsequent dependent actions are skipped (default behaviour)
④ The flow run shows as "Failed" in the run history
⑤ Nobody is notified — no email, no Teams message, no alert
⑥ Business data is lost or not processed; stakeholders assume automation is working
Error handling patterns in Power Automate:
Pattern
How to implement
Catch block
Scope action + "Configure run after" set to "has failed"
Failure notification
Send email / Teams message in the error scope with error details
Retry policy
Set retry count and interval on connectors (default: 4 retries, 20s intervals)
Dead letter logging
Write failed records to a SharePoint list or Azure Table for manual reprocessing
Error handling vocabulary in daily use:
"We wrapped the SAP integration in an error scope — if the connector times out, an adaptive card is sent to the operations Teams channel with the error message and a link to rerun the flow."
Key vocabulary:
• Error handler — a conditional branch that executes when a workflow step fails
• Configure run after — Power Automate setting controlling which previous action state (succeeded, failed, skipped, timed out) triggers the next action
• Dead letter queue — a storage location for failed messages requiring manual reprocessing
• Retry policy — automatically reattempting a failed action a defined number of times
5 / 19
A senior architect reviews a flow and says: "This flow isn't idempotent — if it's triggered twice for the same event, it will create duplicate records." What does idempotency mean in workflow automation, and why does it matter?
Idempotency is a computer science concept with critical practical implications for any automation that creates, updates, or sends data — especially in enterprise workflow systems where retries and duplicate events are common.
Why duplicate triggers happen:
• User double-clicks a "Submit" button before the form prevents it
• A network timeout causes the HTTP request to be retried by the calling system
• Scheduled flows overlap if the previous run was delayed
• Power Automate's own retry mechanism re-sends a webhook event
• A developer manually re-runs a failed flow run
Idempotency implementation patterns:
Pattern
How it works
Existence check
Before creating a record, check if one already exists for this event ID; skip if found
Idempotency key
Store a unique event ID after first processing; reject duplicate event IDs on subsequent runs
Upsert instead of insert
Update the record if it exists, create it only if it doesn't — no duplicates possible
Status flag check
Check a "processed" flag on the source record; skip if already marked processed
Idempotency in professional conversation:
"Before we add the retry logic, we need to make the flow idempotent — otherwise a retry will create a second SAP purchase order for the same form submission, which will fail the three-way match in the ERP."
Key vocabulary:
• Idempotent — producing the same result regardless of how many times the operation is performed with the same input
• Idempotency key — a unique identifier stored to detect and reject duplicate requests
• Upsert — a database operation that updates an existing record or inserts a new one if it does not exist (update + insert)
• Duplicate trigger — a workflow being started a second time for the same event due to retry, network error, or user action
6 / 19
Liam, a junior developer, is explaining a new automated process to the team. He says: 'We're using a 'transformation' in our flow. What does that typically refer to within the context of workflow automation?',
A. transformRequest (a specific HTTP method)
B. Converting data from one format to another (like JSON to XML)
C. Increasing the number of parallel executions
D. Automatically deploying code changes
A 'transformation' in workflow automation usually refers to converting data between different formats – for example, changing a JSON payload into an XML structure or vice versa. This is essential when integrating with systems that expect different data types. Option A describes a specific API method; options C and D relate to parallel processing and deployment, respectively, and are not the core meaning of transformation.
7 / 19
Sarah, a product manager, asks you: 'Our team is building a flow that sends notifications when a new user signs up. We're using a 'webhook'. What does this term mean in the context of our automation?',
A. A type of database table
B. An HTTP endpoint that receives data from another system
C. The name of a debugging tool
D. A command to restart the flow
A 'webhook' is essentially an HTTP endpoint – a URL – that a system can send data to when something happens. In this case, it's where the workflow automation platform sends notifications whenever a new user signs up. Options A and C are incorrect; option D describes a flow action, not a webhook.
8 / 19
David, the lead developer, is reviewing a PR for an automated approval process. He comments: 'I'm seeing that this flow doesn't handle situations where the user cancels the approval request. We need to implement error handling.' What does 'error handling' refer to in workflow automation?',
A. Adding decorative elements to the flow diagram
B. Implementing logic to manage and recover from unexpected events or failures within the flow
C. Setting a maximum execution time for the flow
D. Automatically scaling the flow based on demand
'Error handling' in workflow automation involves designing mechanisms to gracefully deal with potential issues – like user cancellations or system errors. This could include retrying operations, logging details for investigation, or diverting the flow to a different path. Options A and C are irrelevant; option D relates to scaling, not error management.
9 / 19
Liam, a junior developer, is explaining a new automated process to the team. He says: 'We're using a 'transformation' in our flow. What does that typically refer to within the context of workflow automation?',
A. transformRequest (a specific HTTP method)
B. Converting data from one format to another (like JSON to XML)
C. Increasing the number of parallel executions
D. Automatically deploying code changes
A 'transformation' in workflow automation usually refers to converting data between different formats – for example, changing a JSON payload into an XML structure or vice versa. This is essential when integrating with systems that expect different data types. Option A describes a specific API method; options C and D relate to parallel processing and deployment, respectively, and are not the core meaning of transformation.
10 / 19
Sarah, a product manager, asks you: 'Our team is building a flow that sends notifications when a new user signs up. We're using a 'webhook'. What does this term mean in the context of our automation?',
A. A type of database table
B. An HTTP endpoint that receives data from another system
C. The name of a debugging tool
D. A command to restart the flow
A 'webhook' is essentially an HTTP endpoint – a URL – that a system can send data to when something happens. In this case, it's where the workflow automation platform sends notifications whenever a new user signs up. Options A and C are incorrect; option D describes a flow action, not a webhook.
11 / 19
David, the lead developer, is reviewing a PR for an automated approval process. He comments: 'I'm seeing that this flow doesn't handle situations where the user cancels the approval request. We need to implement error handling.' What does 'error handling' refer to in workflow automation?',
A. Adding decorative elements to the flow diagram
B. Implementing logic to manage and recover from unexpected events or failures within the flow
C. Setting a maximum execution time for the flow
D. Automatically scaling the flow based on demand
'Error handling' in workflow automation involves designing mechanisms to gracefully deal with potential issues – like user cancellations or system errors. This could include retrying operations, logging details for investigation, or diverting the flow to a different path. Options A and C are irrelevant; option D relates to scaling, not error management.
12 / 19
Liam, a junior developer, is explaining a new automated process to the team. He says: 'We're using a 'transformation' in our flow. What does that typically refer to within the context of workflow automation?',
A. transformRequest (a specific HTTP method)
B. Converting data from one format to another (like JSON to XML)
C. Increasing the number of parallel executions
D. Automatically deploying code changes
A 'transformation' in workflow automation usually refers to converting data between different formats – for example, changing a JSON payload into an XML structure or vice versa. This is essential when integrating with systems that expect different data types. Option A describes a specific API method; options C and D relate to parallel processing and deployment, respectively, and are not the core meaning of transformation.
13 / 19
Sarah, a product manager, asks you: 'Our team is building a flow that sends notifications when a new user signs up. We're using a 'webhook'. What does this term mean in the context of our automation?',
A. A type of database table
B. An HTTP endpoint that receives data from another system
C. The name of a debugging tool
D. A command to restart the flow
A 'webhook' is essentially an HTTP endpoint – a URL – that a system can send data to when something happens. In this case, it's where the workflow automation platform sends notifications whenever a new user signs up. Options A and C are incorrect; option D describes a flow action, not a webhook.
14 / 19
David, the lead developer, is reviewing a PR for an automated approval process. He comments: 'I'm seeing that this flow doesn't handle situations where the user cancels the approval request. We need to implement error handling.' What does 'error handling' refer to in workflow automation?',
A. Adding decorative elements to the flow diagram
B. Implementing logic to manage and recover from unexpected events or failures within the flow
C. Setting a maximum execution time for the flow
D. Automatically scaling the flow based on demand
'Error handling' in workflow automation involves designing mechanisms to gracefully deal with potential issues – like user cancellations or system errors. This could include retrying operations, logging details for investigation, or diverting the flow to a different path. Options A and C are irrelevant; option D relates to scaling, not error management.
15 / 19
During a standup meeting, Maria, the automation engineer, explains that her team is using a 'delay' function within their flow. John, a developer new to the project, asks: 'What exactly does a delay do in this context?'
A. It immediately executes the next action in the flow.
B. It pauses execution for a specified duration before proceeding.
C. It automatically logs all actions performed by the flow.
D. It sends an alert notification to the system administrator.
A 'delay' function in workflow automation introduces a pause within the flow's execution path. This allows for various purposes like waiting for external events, throttling API calls, or simply adding a buffer before subsequent steps. Option A is incorrect – delays don't bypass actions; options C and D are unrelated functions.
16 / 19
As part of reviewing a PR for an automated invoice approval process, David, the lead developer, comments: 'I'm seeing that this flow doesn't handle scenarios where the vendor changes their payment terms. We need to implement robust error handling – specifically, what happens if the API call fails?' What does David mean by 'error handling' in this context?
A. A system for automatically generating invoices.
B. Mechanisms for detecting and responding to unexpected events or failures within the flow's execution.
C. The process of manually reviewing and approving invoices.
D. The steps involved in calculating the total invoice amount.
'Error handling' refers to the proactive measures taken within a workflow automation system to manage potential problems – such as API call failures or unexpected data inconsistencies. It's not simply about stopping the flow; it's about detecting the issue and taking appropriate action (e.g., retrying, logging an error, sending a notification). Options A, C, and D are related to invoice management but don't address the core concept of handling failures.
17 / 19
Sarah, a product manager, is discussing a new flow with the team. She mentions 'data mapping'. 'What does data mapping typically refer to when we're talking about automating workflows?'
A. The process of encrypting sensitive data within the flow.
B. The transformation of data from one format to another within the flow's logic.
C. The creation of a visual representation of the workflow's steps.
D. The selection of the most efficient database for storing workflow data.
'Data mapping' in workflow automation describes the process of converting data from one structure or format to another – for example, transforming a JSON response from an API into a format suitable for updating a database record. This is a crucial step in many automated flows and distinguishes it from encryption (A), visualization (C) and database selection (D).
18 / 19
Liam, a junior developer, is documenting a flow that sends an email notification when a new lead is created. He writes: 'We're using a 'webhook' to trigger this action.' What does the term 'webhook' mean in this context?
A. A type of database connection used for storing lead information.
B. An HTTP callback mechanism triggered by an event, allowing external systems to notify the flow.
C. A visual diagram representing the flow's data pipeline.
D. A code snippet that automatically generates email content.
A 'webhook' in workflow automation is essentially an HTTP callback – when a specific event occurs (in this case, a new lead being created), the external system sends data to the flow via a pre-defined URL. This allows for real-time triggering of actions without constant polling, making it more efficient. Options A, C and D are related concepts but not the definition of a webhook.
19 / 19
During code review, Alex states: 'This flow isn't 'time-out tolerant'. If the SAP system is unavailable for even a few seconds, it will hang indefinitely.' What does 'time-out tolerance' mean in the context of workflow automation?
A. The ability of the flow to automatically restart after failure.
B. The system's capacity to handle concurrent requests without performance degradation.
C. The maximum duration a step within the flow is allowed to execute before triggering a timeout error.
D. The frequency with which the flow updates its status in the monitoring dashboard.
'Time-out tolerance' refers to how long a workflow automation system can wait for a response from an external service (like SAP) without timing out and failing. It's crucial because external systems are not always available or responsive, so the flow needs to be able to handle these delays gracefully, usually by setting maximum execution times.
What will I practise in "Workflow Automation Vocabulary — Low-Code & No-Code Exercises"?
Practice English vocabulary for workflow automation: triggers, connectors, conditions, error handling, idempotency in Power Automate, Zapier, and n8n. 5 exercises.
How many exercises are in this module?
This module has 19 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
Do I need to create an account to do these exercises?
No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.
What happens if I choose the wrong answer?
You'll immediately see which answer was correct, plus a full explanation covering the vocabulary and reasoning behind it — mistakes are where most of the learning happens.
Can I retry the exercises if I want a higher score?
Yes — use the "Try again" button on the results screen to reset and go through all the questions again.
Is my progress saved if I close the page?
No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.
Where can I find more Low-Code & No-Code exercises?
Browse the full Low-Code & No-Code hub for related drills, or check the "Next up" link below to continue with a connected topic.
How is this different from reading an article on the same topic?
Articles explain vocabulary and concepts in prose; this exercise tests and reinforces that vocabulary through active recall with immediate feedback — the two work best together.
Who writes these exercises?
Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.