Automation and AI integration, real-time events out of the CRM
Whatever has no dedicated connector is linked through events. The CRM sends a real-time event to Zapier or Make, and from there it reaches any application in their catalogue. AI assistants connect through the same interface, with your own keys.
From $2,900 excl. VATone-time payment, no monthly subscription
Automation and AI assistant integration. Real-time events to Zapier and Make, plus AI assistants connected with your own keys.
Works together with: Connectors and API, Lead management, Online store integration.
What happens when every new application needs development
Ordinary flows, at disproportionate cost.
- Every new application in the company needs a development job, or stays an island with a spreadsheet export.
- A simple flow — new enquiry, a note on a chat channel, a row in a spreadsheet, a welcome message — is either paid for or done by hand.
- Data moves between systems by copying, so it drifts out of step.
- Nobody knows which automations exist or who configured them.
- When a flow stops, it is discovered through complaints.
- Dependence on one supplier grows with every bespoke integration.
What the automation integration includes
Events, a programming interface and AI assistants.
Real-time events
Creation and change on enquiry, customer, order, quote, invoice and activity, sent at the moment they happen.
- Enquiry created
- Order paid
- Quote accepted
- Invoice overdue
Flows without programming
Conditions, filters and steps are configured in Zapier or Make, in their own interface.
- No code
- Conditions and filters
- Large app catalogue
- Step-by-step testing
Writing back into the CRM
The platform can add a note, change a stage or create an activity, through the programming interface.
- Notes added
- Stages changed
- Activities created
- With controlled rights
AI assistants with your own key
Classifying an email, drafting a description, summarising a thread — with your key and on your cost.
- Claude
- ChatGPT
- Gemini
- Your own key
Diagnostics on every transmission
You can see which event went out, when, and with what result.
- Transmission history
- Errors visible
- Manual replay
- No silent losses
Vendor independence
If you change automation platform or AI provider, you change the key and the destination, not the CRM.
- Keys in your install
- Configurable destination
- No rewrite
- No commercial lock-in
What changes in the first month
The first flows are configured in hours, not sprints.
Ordinary flows stop needing development
They are configured in the platform interface.
- No development cost
- Fast to implement
- You can change them
The team finds out immediately
Notices on the channels they already use.
- Useful alerts
- Faster reaction
- No manual checking
Data stops being copied between systems
The event carries it where it belongs.
- No drift
- Fewer errors
- One version of the truth
Repetitive work shrinks
Classifications and summaries happen automatically.
- Time recovered
- Consistent quality
- People on hard problems
Stopped flows become visible
Errors show in diagnostics, not in complaints.
- Visibility
- Correction in time
- Confidence in the system
You are not locked to one supplier
Destinations are configurable.
- Portability
- Free negotiation
- Reduced risk
How a flow is built, step by step
From the triggering event to the returned result.
Data sent to an AI assistant leaves your server and reaches that provider. Two things worth stating plainly before configuring a flow with AI.
- Choose explicitly what text you send
- The processing policy is the provider’s
- Cost is consumed on your key
- Set limits in the provider account
- The answer is a suggestion, not a fact
- Keep human confirmation where it matters
A flow that writes into the CRM on the basis of an AI answer should have a human confirmation step wherever the consequence matters.
- 1
The triggering event is chosen
Enquiry created, order paid, quote accepted.
- 2
The CRM sends the event
At the moment it happens, not on an interval.
- 3
The flow is drawn in the platform
Conditions and steps, without programming.
- 4
The steps execute
In the applications in the platform catalogue.
- 5
The result can come back
A note, a stage or an activity in the CRM.
- 6
The transmission stays in diagnostics
With its state and any errors.
What can be built without programming
Flows used in practice.
A notice on every new enquiry
On the team channel, with source and estimated value.
Orders into a shared spreadsheet
For ad-hoc reporting.
A welcome message
When a new customer is created.
Classifying incoming email
With an AI assistant, before routing.
A summary of a long thread
Attached as a note on the customer record.
Escalation above a value threshold
To another application or another person.
Access to data when external platforms are involved
Nothing goes to a service you have not configured.
- Keys are generated in your installation And can be revoked at any time.
- A key’s rights can be limited One key does not have to be able to do everything.
- Data goes only to configured destinations There is no implicit transmission.
- Every transmission is recorded With its time and result.
- AI keys remain yours The cost is consumed in your own account.
- Flows can be stopped instantly By revoking the key or disabling the destination.
What to prepare before the first flow
Decisions that prevent cost and leakage.
An account with the automation platform
Zapier or Make, on the plan that matches your volume.
An access key generated in the CRM
With rights limited to what the flow needs.
The list of events used
What triggers what, written down.
A decision on what data leaves
Especially for flows involving AI assistants.
Cost limits at the AI provider
So a misconfigured flow cannot run up a bill.
An owner for the flows
Who documents and reviews them.
The limits of the automation integration, stated plainly
What the module does not do.
- External subscriptions are not included. Zapier, Make and the AI providers are paid separately, to them, on your usage.
- Data sent leaves your installation. Any flow through an external platform means data with a third party, under their policy.
- AI cost is variable, on usage. A misconfigured flow can run up unexpected charges; we recommend limits in the provider account.
- An AI answer is not guaranteed correct. For consequential decisions, keep a human confirmation step.
- It depends on the external platform being available. If Zapier or Make has an outage, the flow runs late or fails; the event stays recorded in the CRM.
- Complex flows need maintenance. An automation with dozens of steps becomes a system in its own right, to be documented and reviewed.
When the automation integration makes sense and when it does not
Stated plainly.
A good fit if
The situations in which the module pays for itself quickly.
- You use applications that have no dedicated connector.
- You have repetitive flows done by hand today.
- You want to build and change flows without a developer.
- You care about not depending on a single supplier.
Not a fit if
The situations in which we recommend not buying it now.
- Every system you use already has a native connector.
- You have no repetitive flows to automate.
- You do not want data passing through external platforms.
- You prefer every integration written bespoke.
Which package the connectors and API module belongs to
The module is licensed together with external integrations.
Two licensable modules
The programming interface, keys and events are part of the API and integrations module. Connectors to external services and data feeds form the connectors module. They can be activated separately.
What the core includes
The mandatory core brings users and roles, clients and contacts, a lead and sales pipeline, custom fields and 15 interface languages.
Invoicing and payment connectors
They are used together with the invoicing module and the payments and collections module.
Pricing and configurations
Package composition and prices by edition are on the pricing page.
Companies that have trusted Zarina CRM





















Automation integration: what it costs and what you get
You pay once. Everything that follows is written here, not in hidden conditions.
The programming interface and real-time events are part of the API and integrations module, on top of the mandatory core. The package composition and the price per edition are on the pricing page.
Cheaper in a bundle. The tiers group several packages at a price lower than their sum:
- Start2 packages + core$2,900−19%
$3,570 - Pro5 packages + core$3,480−34%
$5,280 - Business8 packages + core$4,640−38%
$7,460 - Enterprise13 packages + core$6,970−31%
$10,080
List prices, excl. VAT, one-time payment, unlimited users. The struck-through price is the sum of the packages bought individually. Current offers apply on the pricing page.
What you pay over time for a subscription CRM
Over 3 years, the subscription costs $10,480; the Zarina Start licence costs $2,900, once.
An indicative comparison: enter the subscription price you pay now. The licence does not grow with the number of users.
What you get
- A lifetime licence, with no subscription and no per-user charge
- Unlimited users, on the same licence
- 6 months of warranty on correct operation: fixing errors and inconsistencies
- Implementation, configuration and team training, included in the price
- The licence is verified locally, on your own server: the application does not depend on our servers to work
How long it takes and what is needed
- 48 hours in the standard configuration; up to 14 working days with customisation around the company’s workflow
- Your own server or web hosting with cPanel, with an SSL certificate
- PHP 7.4 or newer (8.x recommended) and MySQL / MariaDB
- The PHP extensions mysqli, json, mbstring; curl, gd and zip for integrations, PDF and exports
- One cron task, for reminders and automations
Where data lives
- The data stays on your server and does not pass through ours
- Roles and rights per user, two-factor authentication
- An audit trail and limits on login attempts
- Consents and data subject requests, managed in the application
- Digitally signed updates and backups from the application
Questions about automation and AI assistants
What does a real-time event mean?
Do I have to pay for Zapier or Make separately?
Does my data reach third parties if I use Zapier?
Can I connect an AI assistant with my own key?
Is an AI answer written into the CRM automatically?
What happens if the external platform is unavailable?
Can I connect an application that is not in the connector catalogue?
Get the complete product sheet by email
A six-page document with everything you need to know before a sales conversation. No obligation and no sales call.
- The platform core and the 13 module packages, with what each one contains
- The features and modules of the edition you choose, plus available integrations
- Full pricing and what it includes: installation, training, data import, warranty
- The native integrations available and the situations where the platform is not a good fit
Take control of your operations, once
We install Zarina CRM on your hosting, configure it around your own workflow and train your team. From that moment on, the application is an asset of your company, not a recurring expense.

