New ERP connectors: QuickBooks, Xero, Dynamics 365, Odoo, and Defontana
Five ERP connectors in the bring your own account (BYO) model, mirroring SAP and NetSuite. You paste the credential in Settings, Integrations, turn it on, and SellioCRM starts sending customers and invoices to YOUR ERP. QuickBooks and Xero also receive change notifications by webhook. Credentials are encrypted, at no cost on our side.
These connectors work like SAP and NetSuite: you bring your own account (BYO). The data goes straight to YOUR ERP, with no cost or middleman on our side. Open Settings, Integrations, find the card, paste the credential (always encrypted) and enable it. Until it is configured and enabled, nothing happens.
Pushing a record (customer, invoice) uses the same path as the existing connectors. In QuickBooks and Xero the webhook tells you when something changes in the ERP: copy the webhook URL from the card, register it in the ERP dashboard and paste the verification secret. Each change becomes a trace record in the CRM, with no duplication.
QuickBooks Online
- Create an OAuth2 app in the Intuit developer platform and generate the refresh token.
- Paste the Client ID, Client Secret, refresh token and Company ID (realmId); choose the environment.
- To receive notifications, register a webhook for the card URL and paste the verifier token. Enable it.
Xero
- Create an OAuth2 app in the Xero developer platform and generate the refresh token.
- Paste the Client ID, Client Secret, refresh token and organisation (tenant) ID.
- To receive notifications, register a webhook for the card URL and paste the signing key. Enable it.
Dynamics 365 Business Central
- Register an app in Microsoft Entra ID with access to the Business Central API.
- Paste the Azure tenant ID, Client ID, Client Secret, environment name and company ID.
- Enable it and use the test record to prove the connection. This connector is outbound (no webhook).
Odoo
- In your Odoo account, generate an API key under Account security, API keys.
- Enter the instance URL, the database name, your user and the API key.
- Enable it and use the test record to prove the connection. This connector is outbound (no webhook).
Defontana
- Ask Defontana for an integration user and write down the client code and the company code.
- Enter both codes, the environment (production for real operation) and the user with the password.
- Turn it on and use the test record. In this connector the test is a READ: it proves the credential without creating anything in your records.
Defontana receives CUSTOMERS from accounts and contacts, and the account must have the tax identifier filled in, which is how the ERP recognizes the customer. This connector does not issue a sales document: in Chile that is an electronic tax document, it consumes a folio and goes to the SII, so it stays with whoever operates the ERP.
None of these costs anything from us: the account and credentials are yours. If a webhook is rejected, check the webhook secret (a value different from the one stored in the CRM is rejected).