Welcome to the NZRT Wiki Podcast. Today we’re looking at 🔌 Integrations Overview.

So, if you’ve ever wondered how Dolibarr, our core ERP platform, actually talks to the rest of the world, this episode is for you. The short answer is that Dolibarr connects to external systems in three main ways: through a REST API, through webhooks, and through purpose-built connectors designed for specific platforms. Each of these gives you a different kind of bridge between Dolibarr and the tools you use every day.

Let’s walk through the full integration inventory, because there are eight systems worth knowing about here.

The first is WordPress. This is set up as a CMS and portal publishing integration. What that means for you is that Dolibarr can push content and data out to the NZRT WordPress site, so your ERP and your public-facing web presence can stay in sync rather than living in separate silos.

Second is the REST API itself. This is the programmatic access layer, and it’s arguably the most flexible integration of all. If you’re a developer or you’re working with automation scripts, the REST API is how you talk to Dolibarr directly from code. You can create records, query data, update statuses, and much more, all through standard HTTP requests.

Third, you have payment platforms. NZRT has connectors set up for Stripe, PayPal, and Paybox. So when money moves, Dolibarr knows about it. Whether you’re processing client invoices or handling online transactions, these integrations mean payment events can flow back into your ERP records automatically.

Fourth is LDAP, which stands for Lightweight Directory Access Protocol. This one is about directory and single sign-on synchronisation. In plain terms, it means you can connect Dolibarr to a centralised user directory so that staff accounts and permissions can be managed in one place and reflected across systems, rather than having to maintain separate user lists everywhere.

Fifth is Google Analytics. This is a web analytics integration, and it gives you the ability to connect Dolibarr’s web-facing activity to your Analytics reporting. So if you’re tracking portal traffic or user behaviour on pages that tie back to Dolibarr, this connector closes that loop.

Sixth is ClickToDial. This is a VoIP calling integration that works from within the CRM. What that means practically is that you can initiate phone calls directly from a contact or customer record in Dolibarr, which saves time and keeps your call activity tied to the right records without switching between applications.

Seventh is Gmail SMTP. This covers outbound email. When Dolibarr sends emails, whether that’s invoice notifications, automated messages, or system alerts, the Gmail SMTP connector is what routes those messages out through your Google mail infrastructure. It’s the plumbing behind every email Dolibarr sends.

And eighth is the Email Collector. This one works in the opposite direction to Gmail SMTP. Instead of sending email out, the Email Collector pulls inbound email in and converts it into Dolibarr records. So if a client replies to a message, or an email arrives at a monitored inbox, Dolibarr can pick that up and attach it to the right project, ticket, or contact automatically.

Now, one more thing to know about the way NZRT categorises all of this. There’s a service code used internally called 000INT, which stands for the Integration type. Whenever you’re documenting, ticketing, or tracking work that relates to any of these connectors or external system links, that’s the code you’ll see applied. It maps to a broader set of NZRT Service Codes that help keep everything organised across the business.

To summarise what you’ve just heard: Dolibarr sits at the centre of NZRT’s system architecture and reaches outward through eight key integrations. You’ve got WordPress for publishing, the REST API for developer access, three payment platforms covering Stripe, PayPal, and Paybox, LDAP for directory sync and single sign-on, Google Analytics for web reporting, ClickToDial for VoIP from the CRM, Gmail SMTP for outbound email, and the Email Collector for pulling inbound mail into records. All of this integration work falls under the 000INT service code.

That’s it for this episode of the NZRT Wiki Podcast. Thanks for listening.