Skip to main content
Connect One-Time Secret with your account email and an API key, and the agent delivers sensitive values as single-use links instead of cleartext in a ticket note, email thread or chat log. The recipient opens the link once, and One-Time Secret destroys the value. The agent generates the link on its own during a password reset or recovery-code handoff, so your technicians don’t have to.

Connect One-Time Secret

You need a One-Time Secret account and an API key.
1

Generate an API key in One-Time Secret

Go to onetimesecret.com and sign in or sign up. The free plan supports the API. Paid plans raise the rate limits and add custom branding.From the top-right menu open Account, scroll to the API section, and click Generate Key (or Reset Key if you already have one). Copy the key.
2

Paste the credentials into Rallied

In Rallied, go to Settings → Integrations, find the One-Time Secret card, and click Connect. Fill in:Click Save. The card shows Connected once the credentials check out.
There’s no per-tenant or per-client setup, and no webhook to register.

What happens when the agent needs to share a credential

When a workflow or the agent’s own reasoning calls for delivering something sensitive to a user, the agent generates a one-time link through your One-Time Secret account. Examples are a temporary password after a reset, a recovery code or a first-login token. The agent posts the link as a customer-visible reply on the PSA ticket, so the user gets it in the same email thread. The cleartext value never lands in the ticket or the chat log. By default, the link expires 24 hours after it’s created. The agent can shorten that for urgent resets, or extend it up to 14 days for users who might not open it right away. For high-sensitivity credentials such as domain admin or banking portals, a workflow can ask for extra protection. The agent then attaches a passphrase to the link and delivers the passphrase through a different channel. For example, the link goes in the ticket and the passphrase goes by SMS or email.
One-Time Secret is the default link provider. If Traceless is also connected, the agent uses Traceless for a credential only when the requester or dispatcher asks for Traceless or SMS delivery, or when a workflow or your Custom Instructions say to.

Approval settings

onetimesecret-share-secret defaults to Auto, so the agent can generate a link without stopping. To have a technician review each link before it goes out, set it to Approval needed on the Policies tab of Settings → Integrations → One-Time Secret. See Approval settings.

If something goes wrong

One-Time Secret can return an error when the agent tries to generate a link, such as a rate limit, an expired API key or a service outage. The agent doesn’t fall back to pasting the cleartext value on the ticket. It stops, posts an internal note asking a technician to deliver the credential manually, and moves on.

See also