Your customer onboarding team connects each customer's Salesforce org once. Askel handles auth, package install, and schema discovery, then maps opportunities, contacts, and custom objects to your product's data model.
Opportunities, Accounts, Contacts, Tasks, Cases, plus anything ending in __c. Askel handles required-field discovery and external-id upserts.
Askel pulls the customer's object and field metadata, marks confident mappings, and flags the rest for your team to review.
Either personal OAuth (the customer connects their own user) or a packaged Connected App with a service user, your call per customer.
Askel respects the connecting user's permission set. If a field is not visible to the user, it is not written.
If your customer renames a field or changes a picklist, Askel notices and pauses the affected workflow before bad data lands.
Every record Askel touches is logged with the input payload, the resolved mapping, the response, and the user who triggered it.
You sell B2B billing software. A new customer, Northwind Logistics, signs a contract. Their finance team lives in Salesforce. Every closed-won opportunity in Northwind's Salesforce needs to create a customer record in your product, and every invoice your product issues needs to write back to a custom object on the opportunity.
Northwind's admin clicks Connect Salesforce in your product. OAuth flow runs in Askel; the access token never touches your servers.
Askel reads Northwind's Opportunity, Account, and custom Invoice__c objects. Your customer-success team sees a mapping draft within minutes.
Three custom fields do not auto-map. Your CS rep clicks through the suggestions Askel surfaces and approves the mapping with Northwind on a call.
Askel pulls the last 50 closed-won opportunities, runs the full mapping in read-only mode, and shows what would have been created.
Flip the workflow on. New closed-won opportunities create customers in your product; invoices write back to Invoice__c on the originating opportunity.
Northwind's Salesforce admin clicks one button in your product. Askel installs a managed package (the AppExchange listing is published under our Connected App), the admin approves the scope, and Askel stores the refresh token. No tokens, secrets, or client IDs touch your codebase.
© 2025 Askel.ai. All rights reserved.