Flexisign logo
ConnectorFlexisign

Flexisign integration for Claude and Codex

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

Use Flexisign from Claude

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

Use Flexisign from Codex

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

Use Flexisign from Sidekick

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

Documents & Forms

What the Flexisign connector can do

FlexiSign handles document signing with a focus on privacy, letting teams upload, send, and track signature requests. The current FlexiSign connection in type.com is limited to reading the templates saved in your account, so a Claude thread can list what is available before a document goes out for signature.

One connection, many Spaces

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

What teams do with Flexisign in type.com

Check available templates before sending a document

Pull the list of saved FlexiSign templates so the right one is picked before starting a new signature request.

Try asking
List our FlexiSign templates so I can pick the right NDA version to send.

Confirm a template exists for a new hire packet

Verify a specific onboarding template is already set up in FlexiSign before an HR workflow depends on it.

Try asking
Check our FlexiSign templates and tell me if an offer letter template already exists.

Audit templates during a cleanup pass

Review the full FlexiSign template list as part of a periodic cleanup of unused or outdated documents.

Try asking
Pull the full FlexiSign template list so we can review which ones are still in use.

Representative actions

  • List Templates

    Returns the document templates saved in your FlexiSign account.

Connection

API and auth details

FlexiSign is a document-signing product for uploading documents, configuring recipients, and adding digital signatures to documents or images. Public endpoint-level API documentation is not readily discoverable, so integrations should validate programmatic signing, template, recipient, and document-management capabilities directly with FlexiSign.

Source
type.com catalog metadata
Auth schemes
API key
FAQ

Questions people ask before connecting Flexisign

Can Claude work with FlexiSign templates in type.com?

Yes, within the current connection. Claude can list the templates saved in your FlexiSign account from a thread, which helps teams confirm what is available before starting a signature workflow.

How does type.com authenticate to FlexiSign?

FlexiSign uses an API key, added once by an admin when the connection is created, who then controls which Spaces can use it.

Can checking FlexiSign templates be automated?

Yes. A recurring check of the FlexiSign template list can be set up as a type.com automation that posts any changes to a channel.

Is this the same as an MCP server for Flexisign?

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