In one sentence
The property that doing the same operation twice has the same effect as doing it once, so retries do not create duplicates.
An operation is idempotent if running it once or several times leaves the system in the same state. Setting a record's status to "paid" is idempotent. Adding a $50 charge is not, because each run adds another charge. The HTTP standard, RFC 9110, defines PUT and DELETE as idempotent methods and POST as not idempotent by default.
Why automations need it
Networks fail. A request can succeed on the server while the response is lost, so the automation retries. Webhooks get delivered twice. A person clicks "run" again. Without idempotency, each of these creates a duplicate invoice, a second text message to a patient or two copies of a lead in the CRM.
How it is usually done:
Idempotency keys
The caller sends a unique key with each request. The receiver stores the key with the result and returns the stored result if the same key arrives again. Stripe's API documents this pattern for its POST requests.
Natural keys
Use a business identifier, such as an order number or event ID, and check whether it was already processed before acting.
Upserts
Create a record if it does not exist, update it if it does, keyed on a stable ID.
State checks
Before sending a reminder, check whether it was already sent for that appointment.
Where it matters most
Payments, outbound messages, record creation and anything that triggers a charge from a vendor. Read-only steps are naturally safe to repeat.
In our builds
every step that writes data or sends a message is keyed on a stable ID, and retries are explicit: we decide which errors retry, how many times, and which ones go to a person. That is what lets a workflow recover from a failure without anyone cleaning up duplicates.
Keep following the system
Webhook
An HTTP message one system sends to another the moment an event happens, so the receiver does not have to keep asking.
API Integration
A connection that lets software systems exchange approved data and invoke supported operations.
Workflow Automation
Connecting business systems so repeatable tasks run according to defined rules and exceptions reach the right person.
API Key Rotation
Replacing or cycling the API keys an application uses, either on a schedule for security or across several keys for failover, without breaking the apps that depend on them.
Retrieval-Augmented Generation (RAG)
A method where an AI system first looks up relevant documents and then writes its answer using them.
Speed to Lead
The time between a new lead reaching a business and the business's first real response to that lead.
Prior Authorization Automation
Software that gathers, submits and tracks prior authorization requests between providers and health plans with less manual work.