Definition
Full definition of idempotency
In automation platforms, idempotency matters because workflows retry. If your 'create HubSpot contact' action retries after a network glitch, you don't want two contacts. Idempotent actions use a deterministic key (e.g., the trigger's event ID) so the second call detects the first and is a no-op. Tiny Command's actions are idempotent by default where the destination API supports it.
In practice
Idempotency examples
Idempotent action
HubSpot → Create or Update Contact. Re-running with the same email produces one contact, not two.
Used by
Apps that exemplify idempotency
See idempotency in action across real integrations.
FAQ
Common questions about idempotency
What if an action isn't idempotent?
Tiny Command's run log shows you when an action was retried; you can add a Lookup node to dedupe manually.
