Sanaf AI
Start free
Signatures

eSignatures, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your eSignatures account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Signatures
  • Connects with a key
  • 28 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What eSignatures is

eSignatures is an electronic signature platform for creating templates, sending contracts, managing signers, and tracking signing workflows.

You paste in a key from your own eSignatures account. It is kept encrypted, and you can withdraw it from inside eSignatures whenever you like.

How a run works

One message in, the work done in eSignatures.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in eSignatures. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own eSignatures account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

28 tools it already has

What it can do in eSignatures

These are the ready-made tools your AI employee already has in eSignatures. It is not limited to them, but it never has to be taught these.

  • Add Contract SignerAdd a signer to an editable contract without automatically sending a signature request.
  • Add Contract SignersAdd a non-empty list of signers to an editable contract by calling the provider's singular endpoint sequentially in request order. Execution is not atomic and stops on the first pr
  • Add Template CollaboratorCreate a name-only collaborator who can edit a template. This action does not send an invitation or perform any other external delivery.
  • Create and Send ContractCreate a contract from a template or from ad-hoc Markdown and immediately send signature requests to its signers. Supply exactly one of templateid or markdown. This causes external
  • Create Contract DraftCreate a test or production contract draft from a template or from ad-hoc Markdown, without sending signature requests or otherwise delivering it externally. Supply exactly one of
  • Create TemplateCreate a reusable Markdown contract template.
  • Delete Contract SignerPermanently remove a signer from an editable contract. Withdrawn contracts are locked and reject this operation.
  • Delete TemplatePermanently delete a template.
  • Duplicate TemplateDuplicate a template with a new title plus optional placeholder replacements.
  • Get ContractGet one contract's current status, details, signers, signer field values, and temporary signed-PDF URL when available. Do not poll this tool; use provider webhooks for lifecycle ch
  • Get Contract ContentReturn the Markdown content of one contract.
  • Get Contract Placeholder FieldsReturn the current placeholder replacements for one contract.
  • Get TemplateGet one template's metadata, placeholder keys, and signer-field IDs.
  • Get Template ContentReturn the Markdown content of one template.
  • Invite Template CollaboratorInvite a collaborator to edit a template. This action sends an external invitation to the required email address and requires explicit confirmation.
  • List Template CollaboratorsReturn all collaborators who can edit one template. The provider exposes no pagination controls.
  • List TemplatesReturn all templates available to the connected account. The provider exposes no pagination controls.
  • Preview Contract Content UpdatePreview the prospective Markdown from exact find-and-replace edits without mutating the contract.
  • Preview Template Content UpdatePreview the prospective Markdown from exact find-and-replace edits without mutating the template.
  • Remove Template CollaboratorRemove a collaborator's permission to edit a template.
  • Resend Sign RequestResend a signature request to one signer. This causes external delivery and may incur production usage charges, so explicit confirmation is required. The provider documents this op
  • Send Draft ContractSend an existing draft to its signers. This can cause external delivery and production contracts may incur usage charges; explicit confirmation is required.
  • Update Contract ContentApply exact Markdown find-and-replace edits to a contract. This always mutates the contract; use Preview Contract Content Update to inspect the result first.
  • Update Contract Placeholder FieldsUpdate selected placeholder replacements on an unsigned contract.
  • Update Contract SignerUpdate selected contact, delivery, authentication, or redirect details for a signer without resending the contract. At least one signer update field is required.
  • Update TemplateUpdate a template's title and/or labels without changing its Markdown content. At least one of title or labels is required.
  • Update Template ContentApply exact Markdown find-and-replace edits to a template. This always mutates the template; use Preview Template Content Update to inspect the result first.
  • Withdraw ContractIrreversibly withdraw an active unsigned contract so it can no longer be signed. The retained contract remains queryable.
Access, and who is in charge of it

You stay the boss of your eSignatures account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own eSignatures account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in eSignatures is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in eSignatures and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about eSignatures

Can an AI employee really work inside eSignatures?
Yes. It signs in to your own eSignatures account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of eSignatures?
No. Nothing moves and nothing is replaced. Your records stay in eSignatures, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my eSignatures account?
You paste in a key from your own eSignatures account. It is kept encrypted, and you can withdraw it from inside eSignatures whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in eSignatures?
It has 28 ready-made tools in eSignatures today, among them Add Contract Signer, Add Contract Signers and Add Template Collaborator. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use eSignatures and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in eSignatures and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in eSignatures?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in eSignatures is written down with what it did and when.