Systems talking to systems
API integration connects the systems an organization already runs: ERP, CRM, payment, mail, and messaging. Novatelia uses REST and webhooks as the usual contract, and GraphQL when the other system already speaks it. Microsoft, Google, WhatsApp, and SMS are connected through the customer’s own tenant or provider account. A connector is not a partnership, and a failed call is an error the design must show.
Definition
An integration is a documented exchange: which system owns the record, what is sent, what comes back, and what a person does when the call fails. It is not a logo wall.
Application
- ERP
- CRM
- Payments
- Messaging
An API map of neighboring systems. A line is not a live connection.
Contracts
- REST resources with explicit errors
- GraphQL only where the counterpart already provides it
- Webhooks for events, with a retry and a dead-letter path
- Idempotent writes where a retry must not duplicate an order or a ticket
Systems often in scope
- ERP and CRM records the customer is licensed to access
- Payment status from the merchant’s provider, not card data stored by Novatelia
- Email and transactional messages
- Microsoft 365 or Google Workspace where the tenant admin grants access
- WhatsApp or SMS through the customer’s messaging provider
- Other external systems named in the interface list
Questions
Are you a Microsoft or Google partner because you integrate them?
No. Integration uses the customer’s tenant. A partner title is not published on this page.
Do you store card numbers?
No. Payment integration reads status from the provider the merchant has approved. Card capture stays with that provider.
Is every integration GraphQL?
No. REST is the default. GraphQL is used when the other system already exposes it.
Related
Related reading
Describe the system
An RFQ saves a browser draft. It does not publish a price, a timeline, or a quotation reference.