Use Docnify from Claude
Add the Docnify connection to a Space that runs Claude, then use it from every channel in that Space.
Create a Docnify connection, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.
Add the Docnify connection to a Space that runs Claude, then use it from every channel in that Space.
Add the Docnify connection to a Space that runs Codex, then use it from every channel in that Space.
Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.
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.
Connect Docnify once, then decide which Spaces can use it in threads, skills, automations, and coding work.
Add a new signer to a document and set their place in the signing order.
Add legal@partner.com as a recipient on our Docnify vendor agreement, second in the signing order.
Add the signature and date fields a document needs before it goes out for signing.
Add signature and date fields to our Docnify NDA template before we send it out.
Remove a document that's no longer needed once a deal or process is canceled.
Delete the Docnify document for the Meridian contract, that deal fell through.
Adds a recipient to a document, with optional signing order and authentication settings.
Adds one or more fields, such as signature or date, to a document before it's sent.
Permanently removes a specific document by its ID.
Removes a specific field from an existing document.
Removes a recipient from a document, revoking their access to it.
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.
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.
Docnify uses an API key. An admin adds it once when setting up the connection and controls which Spaces can use it.
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.
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.
Connect Getform to Claude in type.com to look up a form submission's details or post new form data from a shared team thread.
Connect Google Slides to Claude in type.com to build decks from markdown, copy templates, and update slides from a thread.
Connect Heyzine to Claude in type.com to convert documents into flipbooks, check large conversions, and manage API limits from a thread.
IgnisignConnect Ignisign to Claude in type.com to initialize documents, create signers, and cancel signature requests from a team thread.