--- title: "Anabix Integration" description: "Connect AI agents to Anabix, a Czech CRM for small and mid-sized businesses. Agents manage contacts, companies, deals, and tasks, log activities, and segment marketing lists against custom field definitions." url: https://flowrunner.ai/integrations/anabix date_modified: 2026-08-11T09:36:14-07:00 --- # Anabix [CRM](https://flowrunner.ai/integrations/category/crm-sales) Connect AI agents to Anabix, a Czech CRM for small and mid-sized businesses. Agents manage contacts, companies, deals, and tasks, log activities, and segment marketing lists against custom field definitions. 31 actions · Custom auth · available [Anabix website](https://anabix.cz/) · [Platform Documentation](https://www.anabix.cz/) · Capability data verified 2026-08-11 1. A form submission arrives from the website or a partner campaign 2. Search Contacts looks the person up by email before anything is written 3. Get Custom Fields resolves the numeric field IDs this account actually uses 4. Create Contact writes the lead with the resolved custom field values 5. Create Activity logs where the lead came from and what they asked for 6. Create Task schedules the first call for the assigned salesperson 7. Data owner confirms the GDPR legal basis before Manage Contact Lists adds them to a marketing segment ## What This Integration Enables Anabix is a Czech CRM built for small and mid-sized businesses, and its object model tells you what it expects you to care about. Contacts, companies, deals, and tasks are the frame, activities are how the relationship history gets written, and marketing lists are how a segment becomes an audience. Two things are account-defined rather than fixed: custom fields are addressed by numeric ID, and the GDPR legal basis on a contact is one of seven codes. That second one is not a formatting detail. It is Anabix asking, in a field, why you are entitled to hold and market to this person. FlowRunner agents work all of it: creating and progressing contacts, companies, deals, and tasks, spinning deals and tasks up from templates that already exist in Anabix, logging activities from other tools, and managing list membership. Anabix supports webhooks, but the subscription is created inside the Anabix application rather than through the API, so this connector ships no triggers. Agents run on a schedule and poll a Search action with a timestamp criterion, or a webhook configured in Anabix posts into a FlowRunner webhook flow. Either way the work is the same, and so is the discipline: agents move the data, and the decisions that carry consequence stay with a person. That is what [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) orchestration means in practice. ### Without FlowRunner **Leads retyped from the inbox**: Form notifications pile up and someone copies them into the CRM later **Marketing lists filled on instinct**: New contacts get added to a segment without a recorded reason for holding them **Custom fields left empty**: The account's own fields go unused because nobody remembers their numeric IDs ### With FlowRunner **Contacts created at arrival**: Every submission becomes a contact with its activity and follow-up task attached **List membership with a reason**: A person joins a marketing segment only after the legal basis is confirmed **The account's schema respected**: The agent reads field definitions first, so custom values land where they belong ## Use Case Scenarios ### Web leads that file themselves correctly A submission lands from the company website. The agent calls Search Contacts on the email address first, because Anabix allows several contacts to share one address and a blind create would add a fourth. Get Custom Fields resolves the numeric IDs and selectbox options for this account's own fields, so the campaign code and product interest land in real fields rather than in a notes blob. Create Contact writes the person, Create Activity records the submission as the first touch, and Create Task puts a call on the right salesperson's list for tomorrow. The marketing segment is the one thing the agent does not touch on its own. ### Deals and tasks built from templates the team already trusts A qualified opportunity comes out of a discovery call. Rather than assembling a deal from scratch, the agent calls Create Deal From Template to instantiate the standard sales case the team already uses, then Update Deal to set the value and the expected close. Create Task From Template lays down the standard follow-up sequence attached to it. Because templates can only be instantiated through the API and not created or edited by it, the shape of the process stays under the sales manager's control in Anabix while the agent handles the repetition. ### A pipeline digest that reads the record instead of an export On a schedule, the agent calls Search Deals with a date range criterion to pull deals won this week and Search Activities to pull the touches behind them. It appends each win to a revenue sheet in [Google Sheets](https://flowrunner.ai/integrations/google-sheets) and posts the weekly total to the sales channel in [Slack](https://flowrunner.ai/integrations/slack). Deals with no activity logged in the last fortnight are named separately. Because Anabix returns HTTP 200 even when a call fails, and signals failure in the response body instead, the connector inspects that body and raises a real error, so a silent write failure does not turn into a quietly wrong report. ## Human-in-Loop Highlight Anabix carries a GDPR Legal Basis field on the contact, mapped to the vendor's numeric codes one through seven. It exists because holding and marketing to a named European individual requires a reason, and the reason is a judgment about how that person's data was obtained. An agent reading a form payload cannot make that judgment. It can see an email address and a tick box; it cannot see whether the consent wording on that page covers the campaign the marketing team is about to run. So the intake agent creates the contact, logs the activity, schedules the call, and then stops at the one action that turns a record into an audience: Manage Contact Lists. It posts the case to the data owner in [Slack](https://flowrunner.ai/integrations/slack): "Eight new contacts from the partner webinar form. Consent wording on that page covers event follow-up only, not the product newsletter. Which legal basis applies, and do these go on the newsletter list or the event follow-up list?" Nothing is blocked in the meantime, the contacts and their history exist and the sales follow-up runs. Only the list membership waits, because that is the write that decides who receives the next email blast, and Delete Contact is the only way back. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via Slack Human decides Agent resumes with decision ## Agent Capabilities 31 actions ### Contacts 6 - **Create Contact** Creates a contact with standard fields, account-defined custom fields addressed by numeric ID, and the GDPR legal basis code. Used to turn form fills, imports, and inbound enquiries into real records. - **Update Contact** Updates an existing contact. Used to enrich or correct a record as better information arrives from other systems. - **Get Contact** Retrieves a single contact by ID. Used to load full context before a routing, enrichment, or merge decision. - **Delete Contact** Permanently deletes a contact. Cannot be undone, so agents propose deletions and people approve them. - **Search Contacts** Searches contacts by any field, with partial text matching, date and number ranges, and custom fields filtered by their numeric ID. Used as the duplicate check before a create, and as the polling mechanism for change detection. - **Manage Contact Lists** Adds a contact to marketing lists or removes them. Used to build segments, and treated as a gated action because list membership is what a campaign send reads. ### Companies 5 - **Create Company** Creates an organization record with registration number, VAT number, and address. Used when a new company enters the pipeline. - **Update Company** Updates an existing company record. Used to keep registration and address data current from an external source of truth. - **Get Company** Retrieves a single company by ID. Used before account-level decisions and writes. - **Delete Company** Permanently deletes a company. Cannot be undone. - **Search Companies** Searches companies by any field with the same criteria model as contacts. Used for account matching and data quality sweeps. ### Deals 6 - **Create Deal** Creates a business case with its value, owner, and account-defined custom fields. Used when an opportunity qualifies. - **Update Deal** Updates an existing deal. Used to progress the case and keep the value honest. - **Get Deal** Retrieves a single deal by ID. Used to confirm current state before a downstream write. - **Delete Deal** Permanently deletes a deal. Cannot be undone, so it stays behind human approval. - **Search Deals** Searches deals by any field, including date ranges. Used for pipeline reporting and stalled-deal detection on a schedule. - **Create Deal From Template** Instantiates a deal from a template that already exists in Anabix. Used so the sales process stays defined by the sales manager in the application while the agent handles the repetition. The API cannot create, edit, or delete templates. ### Tasks 6 - **Create Task** Creates a task with its owner and due date. Used to put follow-ups on a real list rather than in someone's head. - **Update Task** Updates an existing task, including completion and rescheduling. Used as work finishes or priorities move. - **Get Task** Retrieves a single task by ID. Used before reassignment or completion. - **Delete Task** Permanently deletes a task. Cannot be undone. - **Search Tasks** Searches tasks by any field. Used to audit open follow-ups by owner or by record. - **Create Task From Template** Instantiates a task from an existing Anabix template. Used to lay down a standard follow-up sequence in one call. ### Activities 4 - **Create Activity** Logs a call, meeting, email, or note against a contact. Used so outreach performed in other tools still lands in the Anabix relationship history. - **Update Activity** Updates an existing activity record. Used to correct or complete a logged touch. - **Get Activity** Retrieves a single activity by ID. Used to read the detail of a specific interaction. - **Search Activities** Searches activities by any field including date ranges. Used to measure engagement and to find relationships that have gone quiet. ### Lists 3 - **Create List** Creates a new marketing list. Used to stand up a segment before contacts are filed onto it. - **Get List** Retrieves a single list by ID. Used to confirm the target segment before a membership change. - **Search Lists** Searches the account's lists. Used to resolve the right list ID rather than hard-coding one. ### Custom Fields 1 - **Get Custom Fields** Returns the account's custom field definitions with their numeric IDs, titles, types, and selectbox options. Used before any write that touches custom data, because these fields are addressed by ID and defined per account. ## Frequently Asked Questions ### What can FlowRunner do with Anabix? FlowRunner agents can run Create Contact, Update Contact, and Get Contact in Anabix, plus 28 more actions. ### Does connecting Anabix to FlowRunner require OAuth? Anabix uses a custom authentication method to connect to FlowRunner. ### Can Anabix trigger a FlowRunner workflow automatically? Anabix doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Anabix?** This integration exposes Anabix to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/anabix. Site index: https://flowrunner.ai/llms.txt