Integration
Connect Salesforce to Cryptlex
When something happens in Salesforce, your agent does the next thing in Cryptlex. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Salesforce and Cryptlex 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 Salesforce and Cryptlex
Triggers and actions 5 triggers · 19 actions
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).
Trigger
New ActivationTriggers when a new activation is created.
Trigger
New LicenseTriggers when a new license is created.
Trigger
New Trial ActivationTriggers when a new trial activation is created.
Action
Create OrganizationCreates a new organization in Cryptlex with a notification email and a cap on how many users it may create. Returns the created organization, including its id and login alias.
Action
Create UserCreates a new user in Cryptlex, optionally placing them in an organization and granting customer portal access. Returns the created user, including its id.
Action
Delete UserPermanently deletes a user in Cryptlex. This cannot be undone.
Action
Find Licenses by keyReturns the licenses in Cryptlex that match the license key given, with optional extra filters such as product, user or expiry.
Action
Get UserReturns a single user in Cryptlex, including their name, email, role, company, tags and metadata.
Action
List ActivationsReturns the license activations in Cryptlex, optionally narrowed to a licence, product, user, operating system or date range.
Action
List LicensesReturns the licenses in a Cryptlex account, optionally narrowed by product, user, organization, status or date range.
Action
List ProductsReturns the products in a Cryptlex account, with their names, license templates and license counts.
Action
List UsersReturns the users in a Cryptlex account, optionally narrowed by organization, company, role, tags or last-seen date.
Action
Update UserUpdates a user in Cryptlex. Only the values supplied are changed; anything left blank is untouched. Returns the updated user.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.