Adobe Acrobat Sign
Send Adobe Acrobat Sign agreements straight from a Strkr deal. Agreement status syncs to the deal timeline; signed PDFs attach automatically. Fits teams already standardized on the Adobe document stack.
Everything Adobe Acrobat Sign does inside Strkr.
- Send agreements from a deal
- Agreement status synced to deal timeline
- Signed PDF stored on the deal
- Adobe Document Cloud compatible
Native code, not a shim.
OAuth where available
Adobe Acrobat Sign will ship with a native OAuth flow when it lands. No pasted credentials for admins to rotate manually.
KMS-encrypted tokens
Access and refresh tokens are envelope-encrypted at rest using a dedicated customer-managed KMS key. Decryption only happens in Lambda memory during an active API call; plaintext tokens never land in a log.
Shared by the workspace
A workspace admin connects Adobe Acrobat Sign once; every teammate uses the shared connection without re-authenticating.
Disconnect at any time
Admins or users can disconnect Adobe Acrobat Sign from inside Strkr. Stored tokens are deleted and the provider's revocation endpoint is called within 24 hours.
Adobe Acrobat Sign is on the roadmap.
We ship integrations as first-class native code, which takes a little longer than a Zapier shim. If Adobe Acrobat Sign is a dealbreaker for your evaluation, reply to the welcome email after you start a trial and we'll flag it to the roadmap.