Tracking signatures
“Who has not signed the supplier contract yet?”
The person asks and Skyller queries CertSeal with their login and lists the pending envelopes and who still has to sign.
Pending items in the conversation
Integration · Electronic signature
Connect CertSeal to Skyller and the AI starts reading from and acting in it through the functions your company enables — with each person's own login, approval before sensitive actions and a record of every call. Below, the actions and events the vendor publishes, what it takes to start and where this fits into the work.
Actions and eventsCertSeal
CertSeal provides APIs for issuing and managing verifiable digital certificates, recipients, batches, designs, and webhook subscriptions.
21 ACTIONS
published by the vendor; the company enables only the necessary ones
0 EVENTS
triggers the system can send, when the vendor offers them
API KEY
each person signs in with their own credential, encrypted
APPROVAL BY RISK
sensitive actions show a card before running
Live proof
The scene shows the path of a request; the exact actions depend on the functions your company enables in CertSeal.
Input
A team member asks, in the conversation, for something that today requires opening CertSeal — inside their area's space, with their login.
What Skyller does
Result
CertSeal stops being an open tab and starts answering inside the conversation — through the functions your company enabled.
What this scene does not promise
Where this helps your work
Three common situations for people who use CertSeal every day. What Skyller does in each one depends on the functions your company turns on.
Tracking signatures
The person asks and Skyller queries CertSeal with their login and lists the pending envelopes and who still has to sign.
Pending items in the conversation
Sending
Sending for signature is a sensitive action: Skyller shows the card with document and signers and only sends it through CertSeal after Approve.
Sending with approval
Administering
The administrator turns on reading for the team and keeps cancellation restricted in CertSeal. Every call is recorded.
Only the enabled functions
Actions and events
Names as the vendor publishes them, in English, with the description summarized to its first sentence. In your company, the administrator turns on only the necessary actions; none of them runs without permission, and sensitive ones go through approval.
Create Batch
CERT_SEAL_CREATE_BATCH
Create a persistent certificate batch from an existing CertSeal design and optional email template.
Create Webhook Subscription
CERT_SEAL_CREATE_WEBHOOK_SUBSCRIPTION
Create a persistent webhook subscription for selected certificate events.
Delete Recipient
CERT_SEAL_DELETE_RECIPIENT
Permanently delete an issued recipient from an active batch. This cannot be undone, does not refund certificate quota, and permanently burns the certificate ID. Use only when permanent removal is intended.
Delete Webhook Subscription
CERT_SEAL_DELETE_WEBHOOK_SUBSCRIPTION
Permanently delete a webhook subscription and stop future deliveries. This cannot be undone; create a new subscription to resume events.
Get Batch
CERT_SEAL_GET_BATCH
Get one active or archived certificate batch by ID.
Get Certificate
CERT_SEAL_GET_CERTIFICATE
Look up an issued certificate using either its human-readable certificate ID or its public-viewer share token, and return its recipient, batch, design, and resolved variables. Provide exactly one lookup value.
Get Current Workspace
CERT_SEAL_GET_CURRENT_WORKSPACE
Verify the connected CertSeal API key and return the workspace ID and username it belongs to. Use this to confirm account context before creating or changing resources.
Get Recipient
CERT_SEAL_GET_RECIPIENT
Get one issued certificate recipient record by batch ID and recipient ID.
Get Webhook Subscription
CERT_SEAL_GET_WEBHOOK_SUBSCRIPTION
Get one webhook subscription by ID. This does not reveal the signing secret; it returns only the stored secret tail.
Issue and Send Certificates
CERT_SEAL_ISSUE_AND_SEND_CERTIFICATES
Atomically issue certificates for 1-100 recipients and queue email delivery for every created certificate.
Issue Certificates
CERT_SEAL_ISSUE_CERTIFICATES
Atomically issue certificates without sending email for 1-100 recipients in one active batch.
List Batches
CERT_SEAL_LIST_BATCHES
Return one newest-first page of certificate batches in the connected workspace, optionally filtered by archive state.
Before you start
Questions from the people who decide
Related integrations
Next step
Try it free with your team or book a demo: together we pick the CertSeal functions to enable and show the first approved action, with fictitious data.