# Connect eSignatures to Appwrite When **Contract Signed** fires in [eSignatures](https://apiant.ai/connections/esignatures), your agent runs **Add user** in [Appwrite](https://apiant.ai/connections/appwrite). Describe the whole flow and it is built, tested on every scenario and kept running. eSignatures **4** triggers eSignatures **11** actions Appwrite **4** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want eSignatures and Appwrite to do together? Give your AI client this address. `https://mcp.apiant.ai` Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser. ### Set it up in your client ### Claude Code Run this in the directory you want to work in. `claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### Claude, web and desktop Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Cursor Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Codex and the ChatGPT desktop app Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Any other MCP client Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) Example flows ## What eSignatures can start in Appwrite - When **Contract Signed** in eSignatures then **Add user** in Appwrite - When **Contract Withdrawn** in eSignatures then **Get user** in Appwrite Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships. Everything your agent can do with eSignatures and Appwrite ## Triggers and actions 4 triggers · 15 actions - Trigger **Contract Signed** Triggers when a contract is signed by all signers. - Trigger **Contract Withdrawn** Fires when a sent contract is withdrawn/cancelled before signing completes. Webhook event "Contract withdrawn". - Trigger **Signer Declined Signature** Fires when a signer declines to sign the contract. Webhook event "Signer declined the signature". - Trigger **Signer Viewed Contract** Fires when a signer opens/views the contract. Webhook event "Signer viewed the contract". - Action **Add Signer** Add a new signer to an existing contract. - Action **Add Template** Create a new reusable contract template. - Action **Create Contract** Creates a new contract. - Action **Delete Signer** Remove a signer from a contract that has not yet signed. - Action **Delete Template** Delete a contract template. - Action **Get Contract** Retrieve a contract's current status, signer states, and metadata. - Action **Get Template** Retrieve a contract template's details. - Action **List Templates** List all contract templates in the account. - Action **Send Contract Draft** Send a previously created draft contract to its signers. - Action **Update Template** Update an existing contract template's title or settings. - Action **Withdraw Contract** Withdraw (cancel) a contract that has been sent but not fully signed. - Action **Add user** Creates a new user in your Appwrite project's Auth service. - Action **Delete user** Deletes a user from the Appwrite project by user ID. - Action **Get user** Returns a user in your Appwrite project by its ID, including name, email, phone, status, labels and preferences. - Action **List users** Returns the users in your Appwrite project, optionally filtered by a search term or query. ## Each app on its own - [ **eSignatures** ESignatures.io is a tool used for signing mobile friendly contracts over the web.](https://apiant.ai/connections/esignatures) - [ **Appwrite** Open-source backend-as-a-service platform providing authentication, databases, file storage, serverless...](https://apiant.ai/connections/appwrite) Reviews ## What our customers say ## More from eSignatures - [ **eSignatures to Pexafy** Semantic image search across 9+ free stock photo sources with a unified JSON schema](https://apiant.ai/connect/esignatures-to-pexafy) - [ **eSignatures to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/esignatures-to-hubspot) - [ **eSignatures to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/esignatures-to-salesforce) - [ **eSignatures to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/esignatures-to-slack) - [ **eSignatures to Google Sheets** Google Sheets](https://apiant.ai/connect/esignatures-to-google-sheets) - [ **eSignatures to Google Calendar** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/esignatures-to-google-calendar) ## More into Appwrite - [ **HubSpot to Appwrite** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-appwrite) - [ **Salesforce to Appwrite** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-appwrite) - [ **Slack to Appwrite** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-appwrite) - [ **Google Sheets to Appwrite** Google Sheets](https://apiant.ai/connect/google-sheets-to-appwrite) - [ **Gmail to Appwrite** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-appwrite) - [ **Google Calendar to Appwrite** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-appwrite) Questions ## eSignatures and Appwrite, answered ### ### What can start an automation from eSignatures? Any of eSignatures's 4 triggers in the catalog, including Contract Signed, Contract Withdrawn, Signer Declined Signature and Signer Viewed Contract. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Appwrite when something happens in eSignatures? Any of Appwrite's 4 actions, including Add user, Get user, List users and Delete user. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Appwrite to eSignatures? Appwrite has no triggers in the catalog today, so automations start in eSignatures. If you need the other direction, ask: your agent reads Appwrite's API documentation and adds it. ### ### Do I have to build a connector for eSignatures or Appwrite? No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running. ### ### What happens when something fails? Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships. ### ### Is there a free plan? Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.