Observability
Alerting an owner without creating an alert storm
Make workflow failure alerts actionable, group related records and escalate urgent work without flooding owners.
Archive
October 2026
Integration Platforms
APIs and webhooks in automated workflows
Understand how webhook deliveries and API calls work together, where each fits, and how to confirm the resulting workflow action.
Integration Platforms
Assigning an owner to orphaned integrations
Stabilise an ownerless integration, identify the teams that depend on it and complete an explicit operational handover.
Data Mapping
Batching records without losing individual failures
Use batches while tracking each record’s success, failure or unknown outcome and retrying only appropriate entries.
Observability
Building a workflow health dashboard
Lay out outcomes, backlog and execution signals with clear definitions, data freshness and routes to affected records.
Workflow Design
Building test cases for every decision branch
Turn workflow decisions into cases with expected routes and destination effects, including compound conditions, defaults and boundaries.
Integration Platforms
Checking connector limitations before selecting a platform
Check connector operations, fields, licensing, limits and network paths before committing a workflow to a platform.
Workflow Design
Choosing a workflow trigger from an actual system event
Select a workflow trigger by checking the business transition, event fields, filtering, replay behaviour and destination effect it permits.
![How to choose the right idempotency key for an event: Keep the same idempotency key for retries of one action; use a new key for a new action.; Write: one [effect] for each [identity], e.g. one standard invoice per approved order.; Check stability, uniqueness, scope and lifetime; include tenant ID for tenant-scoped IDs. Choosing an idempotency key for an event](/covers/choosing-an-idempotency-key-for-an-event-640.webp?v=39704930)
Error Handling
Choosing an idempotency key for an event
Choose a stable idempotency key that recognises retries without blocking a legitimate new event or action.
Workflow Design
Choosing when a workflow needs to remember state
Use an interruption test to decide whether a workflow needs durable state and which progress it should retain.
Integration Platforms
Comparing an iPaaS with point-to-point integrations
Compare direct integrations with an iPaaS using connection growth, ownership, change control and ongoing operating work.
Authentication
Comparing API keys with delegated and application access
Choose a workflow credential by asking whose authority the action should use and what it must be able to do.
Integration Platforms
Comparing batch schedules with event-driven execution costs
Compare scheduled checks, event starts and per-record work using the same workload and completion deadline.
Error Handling
Comparing workflow versions before release
Compare workflow triggers, decisions, data, actions and recovery settings, including configuration outside a platform's version view.
Integration Platforms
Deciding whether a workflow needs code or a connector
Decide between a prebuilt connector, custom connector, code or a mixed workflow by checking the exact operation, limits and recovery needs.
Workflow Design
Designing reliable workflows between business applications
Plan a cross-application workflow around a confirmed business outcome, clear data ownership, safe recovery and an operator who can resolve exceptions.
Error Handling
Distinguishing repeated events from legitimate new actions
Tell redelivered events from genuinely new actions using both event identity and the identity of the business effect.
Workflow Design
Documenting a workflow so another engineer can operate it
Create a workflow runbook that lets another engineer find an item, confirm its outcome and recover or escalate it safely.
Error Handling
Expiring an approval request that receives no response
Set a business deadline, close an unanswered approval through a controlled transition and prevent late responses from authorising an action.
Error Handling
Handling API throttling with controlled retries
Handle API throttling with provider retry timing, shared pacing, bounded attempts and a clear failure route.
Data Mapping
Handling changes to a record while approval is pending
Classify edits to a record under review, preserve the terms shown and prevent stale approval from authorising changed terms.
Error Handling
Handling deleted records during synchronisation
Set delete and restore rules for paired records, check actual deletion signals and prevent an unwanted record from reappearing.
Integration Platforms
Handling long-running approvals across systems
Design a durable approval request, callback and deadline so a delayed decision safely continues work across systems.
Data Mapping
Handling optional fields in an API payload
An optional field is a contract decision, not a field to fill with a convenient blank.
Workflow Design
Human approvals in technical workflows
Design an approval gate around a defined decision, authorised responder, reviewed terms, deadline and separately confirmed action.
Error Handling
Idempotency and duplicate prevention
Define idempotent workflow actions, stable keys and safe retry behaviour to prevent duplicate business effects.
Data Mapping
Identifying workflows that run without producing useful changes
Classify no-change workflow runs, find avoidable usage and protect useful checks before reducing execution.
Workflow Design
Integration platforms and workflow engines
Understand the roles of integration platforms and workflow engines, then assess the capabilities and operating model your processes need.
Authentication
Keeping secrets out of workflow logs
Workflow logs should explain what happened without exposing credentials.
![Restrict connector access to essential records: Grant API and record permissions only for required data types and operations.; Use HubSpot’s 'Their [Objects]' setting to limit contact access to owned records.; Verify token claims via jwt.ms to confirm restricted permissions in Microsoft Entra. Limiting a connector's access to required records](/covers/limiting-a-connector-s-access-to-required-records-640.webp?v=5f285ac7)
Authentication
Limiting a connector's access to required records
A connector should read or change the smallest useful set of records.
Data Mapping
Mapping different date and timezone formats
Date mapping fails when a workflow treats every date-like string as the same kind of value.
Data Mapping
Mapping inputs and outputs before building an integration
Create an input-to-output contract for an integration, including field meaning, missing values, destination results and rejection paths.
Observability
Measuring the delay between trigger and completed action
Measure workflow delay from source event to confirmed destination action, including queue and retry time.
Data Mapping
Normalising identifiers across connected applications
Two applications can refer to the same customer, order or case with different identifiers.
Integration Platforms
One-way versus two-way record synchronisation
Choose a record sync direction from valid edit paths, then check field support, matching and conflict settings in the intended connector.
Workflow Design
Pausing a workflow until a named person approves
Assign an approval to an identified account, bind the decision to one waiting request and handle reassignment and repeat replies.
Workflow Design
Planning queue capacity for a sudden event spike
Estimate backlog growth and drain time during an event spike, then check retention, worker capacity and deadlines.
Error Handling
Preventing duplicate invoices after a workflow retry
Protect invoice creation across workflow retries, lost responses and concurrent workers using a stable business identity.
Data Mapping
Reading an API response before mapping fields
Inspect an API response's status, headers, JSON shape and field meaning before mapping values into a workflow.
Observability
Rebuilding a sync after a prolonged outage
Check replay availability, inventory both systems when history is incomplete, reconcile differences and restart record syncing.
Error Handling
Recording enough context to diagnose a failed workflow
Capture the IDs, attempted action, known outcome and safe error context needed to investigate a failed workflow.
Data Mapping
Recording source-system dependencies
Build a source dependency register for a workflow, covering events, lookups, accounts, field contracts, owners and missed-work recovery.
Authentication
Recording who approved a sensitive action
Record the actual approval responder, the terms reviewed and the separately confirmed result of the sensitive action.
Error Handling
Resolving conflicting updates from two systems
Identify competing record edits, choose a field-level rule and apply the resolution without overwriting another change.
Error Handling
Resuming a workflow after a service interruption
Use the last confirmed outcome and destination records to resume an interrupted workflow without blindly repeating work.
Error Handling
Rolling back a workflow without replaying completed actions
Redirect new workflow starts, classify affected outcomes and recover unfinished items without repeating confirmed external actions.
Error Handling
Rotating credentials without breaking scheduled workflows
Credential rotation succeeds when the old secret is revoked and every dependent workflow still runs as intended.
Error Handling
Routing failed records to an exception queue
Keep failed workflow records diagnosable and owned, then check retention, destination state and replay safety before recovery.
Error Handling
Safely retiring a workflow that other systems still use
Find a workflow’s remaining consumers, plan a cutover, settle pending and unknown work, and decommission it with an owner.
Data Mapping
Separating orchestration state from business records
Define which system owns business facts and which progress an orchestrator stores, including references, versions and result IDs.
Error Handling
Separating retryable failures from invalid data
Decide whether a failed workflow record needs a bounded retry, data correction or reconciliation of an uncertain write.
Observability
Setting budget alerts for high-volume integrations
Choose usage and spending alerts for busy integrations, with plan limits, response owners and delayed-billing caveats.
Workflow Design
Stateful workflow orchestration
Learn when a workflow needs durable state, what it should remember, and how to handle waits, external actions and recovery.
Observability
Testing an inbound webhook with sample events
Plan sample webhook events, inspect sender and receiver records, and check downstream outcomes separately from receipt.
Error Handling
Testing duplicate prevention before production
Test duplicate prevention with lost responses, concurrent delivery, changed inputs and legitimate new actions.
Observability
Tracking successful outcomes rather than execution counts
Define eligible work, confirm destination results and calculate outcome and on-time rates without counting retries as extra successes.
Integration Platforms
Using a sandbox before connecting live business accounts
Map test and live connections, check what a sandbox isolates, and verify outbound effects before connecting production accounts.
Error Handling
Validating transformed data before sending it onward
A workflow can transform a payload successfully and still send the wrong business value.
Workflow Design
Webhooks versus scheduled API polling
Choose between a webhook and scheduled API polling by checking event coverage, scan behaviour, timing and recovery.
Authentication
Workflow authentication and secrets
A workflow should have only the access it needs, keep its credentials out of logs and survive planned rotation without silent failure.
Data Mapping
Workflow data mapping
Workflow data mapping defines how a value leaving one application becomes a value another application can safely use.
Workflow Design
Workflow data synchronisation
Plan record synchronisation across business applications by defining identity, field ownership, deletion rules and recovery checks.
Workflow Design
Workflow documentation and ownership
Build a discoverable workflow record, dependency map and operating runbook, with clear owners for changes, exceptions and retirement.
Error Handling
Workflow error handling
Classify workflow failures, limit safe retries, preserve unresolved records and confirm the destination outcome.
Observability
Workflow monitoring and observability
Monitor confirmed workflow outcomes, spot missing or overdue work and use execution signals to investigate the cause.
Workflow Design
Workflow operating costs
Estimate workflow operating costs using the right billing units, connected-service usage and confirmed business outcomes.
Workflow Design
Workflow rate limits and throughput
Plan workflow throughput around API limits, queues, batching, retries and the rate of completed actions.
Observability
Workflow testing and deployment
Plan workflow tests, verify live connections, compare versions and release with a recovery path for completed external actions.