Integration
Connect Xodo Sign to Salesforce
When something happens in Xodo Sign, your agent does the next thing in Salesforce. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Xodo Sign and Salesforce to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Xodo Sign and Salesforce
Triggers and actions 3 triggers · 19 actions
Trigger
Document CompletedTriggers when a new document is completed. Note: This trigger only checks for new documents being completed every 15 minutes.
Action
Add documentCreate and send a new document for signature. POST https://api.eversign.com/document — builds a document from raw files/fields/signers, optionally sends immediately.
Action
Add templateCreate a new reusable document template. POST https://api.eversign.com/document with is_template set — defines fields/signer roles for later use via "Use Template".
Action
Cancel documentCancel an in-progress document's signature process (stops further signing without deleting it). DELETE https://api.eversign.com/document with document_hash and cancel=1.
Action
Delete documentPermanently delete a document or template. DELETE https://api.eversign.com/document with document_hash param.
Action
List businessesList the businesses (sub-accounts) available on this account. GET https://api.eversign.com/business.
Action
List documentsList the account's documents. GET https://api.eversign.com/document — supports limit param, returns document summaries (not templates).
Action
List templatesList the account's saved templates. GET https://api.eversign.com/document?type=template.
Action
Reassign signerReassign a document's pending signature to a different signer email. POST https://api.eversign.com/reassign.
Action
Send reminderSend a signature reminder to a pending signer on a document. POST https://api.eversign.com/send_reminder with document_hash and signer_id.
Action
Use TemplateSends a document created from a template in your eversign account.
Trigger
New object recordPolling trigger: fires for each new record created in the specified SObject type. Polls SOQL ordered by CreatedDate descending.
Trigger
New or updated object recordPolling trigger: fires for each record created or modified in the specified SObject type. Polls SOQL ordered by SystemModstamp descending.
Action
Create object recordCreates a new record of the specified SObject type (standard or custom, e.g. Account, Contact, Lead, Opportunity, Case, or MyObject__c) with the supplied field values.
Action
Delete object recordDeletes an existing SObject record by object type and record ID.
Action
Describe objectReturns the full field and metadata description (describe) for an SObject type — useful for discovering available fields and their API names.
Action
Find most recent created or updated recordReturns the single most recently created or last-modified record for the specified SObject type (ordered by SystemModstamp DESC, LIMIT 1).
Action
Find object recordsFinds matching records for an SObject type by a field/value equality match via SOQL. Returns Id and the requested fields for all matches.
Action
Get object recordRetrieves a single SObject record by object type and record ID. Optionally restrict returned fields with a comma-separated 'fields' list.
Action
List objectsLists all available SObject types (standard and custom) on the org.
Action
SOQL queryExecutes a SOQL query against the org and returns matching records. Example: SELECT Id, Name FROM Account WHERE CreatedDate = TODAY.
Action
Update object recordUpdates an existing SObject record by object type and record ID with the supplied field values. Salesforce returns no body on success (HTTP 204).
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.