Docnify logo
ConnectorDocnify

Docnify integration for Claude and Codex

Connect Docnify once, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.

Use Docnify from Claude

Add the Docnify connection to a Space that runs Claude, then use it from every channel in that Space.

Use Docnify from Codex

Add the Docnify connection to a Space that runs Codex, then use it from every channel in that Space.

Use Docnify from Sidekick

Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.

Documents & Forms

What the Docnify connector can do

Getting a document through signing usually means adding the right recipients, placing the fields they need to fill in, and cleaning up afterward. Docnify handles that signing workflow, and once it's connected in type.com, an operations or legal Space can ask Claude to add a recipient, set up signing fields on a document, or remove a document that's no longer needed, without opening Docnify separately.

One connection, many Spaces

Connect Docnify once, then decide which Spaces can use it in threads, skills, automations, and coding work.

What teams do with Docnify in type.com

Add a recipient to a document

Add a new signer to a document and set their place in the signing order.

Try asking
Add legal@partner.com as a recipient on our Docnify vendor agreement, second in the signing order.

Set up fields before sending for signature

Add the signature and date fields a document needs before it goes out for signing.

Try asking
Add signature and date fields to our Docnify NDA template before we send it out.

Clean up a canceled document

Remove a document that's no longer needed once a deal or process is canceled.

Try asking
Delete the Docnify document for the Meridian contract, that deal fell through.

Representative actions

  • Add Document Recipient

    Adds a recipient to a document, with optional signing order and authentication settings.

  • Create Document Fields

    Adds one or more fields, such as signature or date, to a document before it's sent.

  • Delete Document

    Permanently removes a specific document by its ID.

  • Delete Document Field

    Removes a specific field from an existing document.

  • Delete document recipient

    Removes a recipient from a document, revoking their access to it.

Connection

API and auth details

Docnify is described publicly as a digital signing and document workspace product with integrations across productivity tools. Public API documentation is not readily discoverable, so customer connections should be validated against account-specific integration options or vendor support before promising direct API automation.

Source
type.com catalog metadata
Auth schemes
API key
FAQ

Questions people ask before connecting Docnify

Can Claude manage Docnify documents from type.com?

Yes. With Docnify connected to a Space, you can ask the agent to add a recipient, set up signing fields, or remove a document, and the change shows up in the thread for the team.

How does type.com authenticate with Docnify?

Docnify uses an API key. An admin adds it once when setting up the connection and controls which Spaces can use it.

Can Docnify cleanup run on a schedule?

Yes. A recurring task, such as removing canceled documents each week, can be set up as a type.com automation that posts a summary to a channel.

Is this the same as an MCP server for Docnify?

Not exactly. type.com uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.

More documents & forms connectors

All Documents & Forms integrations