Custom mapping
Their schema. Your integration.
Map each customer’s objects, fields, and rules to their schema. Your factory serves it from one endpoint you call inside your product.
Appnigma SDK
One endpoint for all systems.
Connect, read, and write any customer’s system inside your product. Your factory maps each call to that customer’s objects, fields, and rules.
const page = await appnigma.crm.contacts.list({ endCustomerId: "lawfirm-123", platform: "attio", limit: 50,}); for (const contact of page.records) console.log(contact.fullName, contact.emails[0]?.value); // Same shape for HubSpot, Salesforce, Pipedrive and Attio.page = client.crm.contacts.list( end_customer_id: "lawfirm-123", platform: "attio", limit: 50) page[:records].each do |contact| email = contact[:emails].first&.dig(:value) puts "#{contact[:full_name]} #{email}"end# Same shape for HubSpot, Salesforce, Pipedrive and Attio.page = client.crm.contacts.list( end_customer_id="lawfirm-123", platform="attio", limit=50,) for contact in page["records"]: email = contact["emails"][0]["value"] if contact["emails"] else None print(contact["full_name"], email)# Same shape for HubSpot, Salesforce, Pipedrive and Attio.- 1endpoint for every customer
- Eachcustomer’s schema mapped
- Your rulesrun for each customer
Beyond standard fields.
When a standard connector misses custom objects or fields, the mapping work lands back on your team. Your factory builds the mapping their workflow needs.
Their workflow. Their rules.
A custom field for deal stages. A different rule for matching contacts. Each customer gets their own logic, not the same sync for everyone.
Skip the connector sprawl.
Adding a customer’s system shouldn’t mean another connector inside your product. The SDK calls your factory; the factory handles the customer-specific mapping.
Your team sets the behavior.
Define which objects, fields, and rules each integration needs. Your factory builds and tests the mapping; you decide what goes live.
Integration Factory
Custom mapping plugs into the factory
Built and tested.
Your factory builds the integration around each customer’s schema and tests its behavior. Changes to your code arrive as pull requests, never direct edits.
Explore the Integration FactoryMaintained after launch.
Appnigma runs your factory, and the factory maintains each integration. Custom mapping is part of the integration, not a one-off build left with your team.
Explore integration maintenanceReviewed before it ships.
On Managed, your engineers review the work. On Embedded, we review it. Either way, you choose what ships.
Every mapping is yours.
Every mapping, test, and learned fix belongs to you.
Choose your deployment path
Run the factory with your own team, or have our engineers sit with yours. Both paths use the same Integration Factory, and every mapping, test, and learned fix is yours.
Managed
Your team owns the roadmap and reviews the work. We run the factory that builds, serves, and maintains each integration.
For product and platform teams
Embedded
We sit with your engineers from migration to go-live. We review the work; you decide what ships.
For teams moving off in-house or iPaaS integrations
Map your next customer’s schema.
Show us the objects, fields, and rules they need.