Public-key cryptography
Public-key encryption, also called asymmetric encryption, is a branch of cryptography in which the encryption key differs from the decryption key. Each user generates a pair of keys: a public key, which is available to anyone and used for encryption, and a corresponding private key, which is kept secret and used for decryption.
On this page
Source content checked . English translation published 2026-10-27.
In business automation
Public-key encryption uses a pair of keys: a public one for sending or verification, and a private one that is kept secret. In automation, it appears in webhook authentication, JWTs, and signatures between services.
Examples
These examples illustrate a possible workflow. Adapt the connections and rules to your own systems.
Authenticating a supplier webhook
A supplier sends an order event. Before creating a task, the process checks the signature using the supplier’s public key. A request without a valid signature is rejected, even if the message body looks correct.
Relevant tools
- Supabase
- Tokens and authentication rely on keys; rotate secrets and do not store a private key in a public client.
What to check
- Publishing the private key in a workflow or code repository defeats the protection provided by the pair.