ceven

Docnify

Automates the preparation, sending, and tracking of digital contracts, mapping signature events to your CRM and managing recipient lists without manual entry.

Try Docnify in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Docnify integration

    • Describe the outcome and Ceven picks the right Docnify calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Docnify data, across all 13 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Docnify access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Docnify, when, and on whose behalf.
    • The agent pauses and asks when Docnify is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Docnify.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Docnify action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Docnify, and when to use it.

Add Document Recipient
Use this to add a signer to a document. Specify the signing order and authentication options after you have the document ID.
Create Document Fields
Use this to place signature or text fields on a document. Run this after fetching the document but before sending it to recipients.
Delete Document
Permanently remove a document by its ID. Use this only after confirming the file is no longer needed for compliance.
Delete Document Field
Remove a specific field from a document when it is no longer required for the signing process.
Delete document recipient
Revoke access for a specific recipient. Use this after verifying the document and recipient IDs.
Get Document
Pull a specific document by ID to view its current state, metadata, and signature status.
Get Template
Pull a specific template by ID to review its structure and metadata before using it to create a new document.
List Documents
Pull a list of all documents in the account to monitor volume or find specific files.
List Templates
Pull all available templates to identify the correct ID for a specific contract type.
Resend Document
Re trigger signing notifications for a document. Use this when a recipient has not responded within a set timeframe.
Send Document
Dispatch a document for signing. Ensure recipients are added and content is uploaded before calling this tool.
Update Document Fields
Modify the labels or requirements of existing fields on a document before it is sent.
Update Document Recipient
Change the name, email, or role of a recipient on a document using their unique ID.

13 actions · scroll to see them all

Frequently asked questions

Ceven interacts with Docnify through secure API calls that respect the permission model of your account. We do not store the actual contents of your signed PDFs on our own servers. Instead, we store the document metadata and the status of the signing process. When a workflow needs to access a file, Ceven requests a temporary access link from Docnify. This ensures that your sensitive legal documents remain encrypted within the Docnify vault while still allowing the agent to trigger actions based on whether a document is signed or declined.
Yes. When using the Add Document Recipient tool, you can specify a numerical signing order. Ceven can be programmed to follow a specific logic, such as requiring the client to sign first and the executive to sign last. The agent monitors the status of each recipient in real time. Once the first person signs, the agent can trigger a notification to the next person in line or update your internal project management tool to show that the document has progressed to the next stage.
If a document bounces or a recipient cannot be reached, the agent can detect this state via the Get Document tool. You can build a workflow that automatically flags the record in your CRM and notifies the account manager. Using the Update Document Recipient tool, the agent can then swap out the incorrect email address for a new one without having to delete the entire document and start the process over, which preserves the audit trail for the other signers.
Yes. Docnify imposes a rate limit on the number of API requests per minute depending on your subscription tier. If a workflow attempts to batch process hundreds of documents at once, you may encounter a 429 error. Ceven manages this by implementing an automatic retry logic with exponential backoff. This means the agent will pause for a few seconds and try again until the request succeeds, ensuring that your bulk sending tasks complete without crashing the workflow or losing data.
Absolutely. The agent first uses List Templates to find the correct ID for the agreement you need. It then pulls the template details and uses the Create Document Fields tool to map specific data from your CRM into the document. Once the fields are populated and the recipients are added via the Add Document Recipient tool, the agent calls the Send Document action. This entire sequence happens in seconds, moving a lead from a verbal yes to a sent contract without human intervention.
Ceven can be configured to poll the Get Document endpoint at regular intervals or react to a webhook event if your Docnify tier supports it. The agent looks for the completed status in the metadata. Once the status changes to signed, the agent can trigger a series of downstream events, such as moving a Trello card to the done column, sending a welcome email to the customer, and notifying the finance team to generate the first invoice in your billing system.
Yes, as long as the document has not been fully executed. The agent uses the Delete document recipient tool to remove the specific user by their ID. This is useful when a stakeholder is removed from a deal or an incorrect person was added to the loop. After the removal, the agent can verify the remaining recipient list to ensure the signing order is still logical before the document continues its path through the remaining signers.
Yes. The Update Document Fields tool allows the agent to modify the labels or requirements of a field. For example, if a client requests a change to a payment term, the agent can update the text field in the document. However, keep in mind that changing fields on a document that has already been partially signed may invalidate the current state depending on your Docnify account settings. The agent can be told to alert a human if a field change is requested after the first signature.

Alternatives to Docnify

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

DocuSign logoDocuSignHelloSign logoHelloSignPandaDoc logoPandaDoc

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Docnify and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free