Use Flexisign from Claude
Add the Flexisign connection to a Space that runs Claude, then use it from every channel in that Space.
Create a Flexisign connection, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.
Add the Flexisign connection to a Space that runs Claude, then use it from every channel in that Space.
Add the Flexisign 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.
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.
Connect Flexisign once, then decide which Spaces can use it in threads, skills, automations, and coding work.
Pull the list of saved FlexiSign templates so the right one is picked before starting a new signature request.
List our FlexiSign templates so I can pick the right NDA version to send.
Verify a specific onboarding template is already set up in FlexiSign before an HR workflow depends on it.
Check our FlexiSign templates and tell me if an offer letter template already exists.
Review the full FlexiSign template list as part of a periodic cleanup of unused or outdated documents.
Pull the full FlexiSign template list so we can review which ones are still in use.
Returns the document templates saved in your FlexiSign account.
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.
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.
FlexiSign uses an API key, added once by an admin when the connection is created, who then controls which Spaces can use it.
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.
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 Pdfless to Claude in type.com to confirm the workspace is active and list document templates before generating files.
Connect PDFMonkey to Claude in type.com to generate documents instantly, build new templates, and remove outdated ones from a thread.
Connect Refiner to Claude in type.com to pull contacts, forms, and survey responses, or check account usage, from a shared thread.
Connect Retently to Claude in type.com to tag feedback, update customer records, and review campaigns from a shared customer experience thread.