eWay-CRM
CRMConnect AI agents to eWay-CRM, a Czech CRM that runs inside Outlook. Agents manage companies, contacts, deals, projects, and tasks, and write journal entries against any of them.
What This Integration Enables
eWay-CRM's defining choice is that it lives inside Outlook. That is not a packaging detail, it is the reason the product exists: the CRM sits where salespeople already are, rather than asking them to go somewhere else after every call. The cost of that choice shows up in the API. Change propagation runs through the Outlook synchronization channel, so there is no public webhook subscription surface and this connector ships no triggers. An agent cannot be told that a deal moved. It has to go and look, which in practice means a Search action with a column filter on a schedule. That is worth saying plainly rather than dressing up, because a flow designed on the assumption of events will quietly never fire.
What you get in exchange is an unusually uniform surface. Every module follows the same four verbs, and the write verb is Save, which is an upsert: omit ItemGUID and eWay-CRM creates a record, supply an existing ItemGUID along with its current ItemVersion and it updates one, returning the saved identifier in Guid. Deletes are soft, moving the record to the eWay-CRM recycle bin where a person can restore it from inside the application, so deletion is genuinely not the dangerous operation here. Field and enum names are the underlying database columns and they are case sensitive, so writes use names like CompanyName, FileAs, FirstName, LastName, and Email1Address. Dropdown style fields are configurable per database and store an enum value identifier rather than a fixed code, which is why Search Enum Types, Search Enum Values, and Get Additional Fields are first class actions rather than an afterthought. One naming quirk is worth internalising: the module the application labels Deals is the Leads folder underneath, so the API methods are GetLeads and SaveLead while the FlowRunner actions keep the name the user sees. The API also returns HTTP 200 even on failure, wrapping every response in an envelope with a ReturnCode, and this connector raises anything other than rcSuccess as an error carrying the server description, so automation exceptions surface as exceptions instead of passing as quiet successes. Sessions are handled for you: when the server reports rcBadSession the connector logs in again once and retries, so long running flows do not have to manage it. It works against both eWay-CRM cloud accounts and self hosted servers.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Inbound leads that arrive as a complete, connected record
Leads collect in Google Sheets from a website form and a partner list. The agent first calls Search Enum Values to resolve the company type and deal status identifiers this database actually uses, and Get Additional Fields to discover the custom columns the team added. For each row it calls Search Companies filtered on the company name, and Search Contacts on the email address. Rows matching nothing get Save Company with no ItemGUID, which creates the account and returns its Guid, then Save Contact linked to it, then Save Deal for the opportunity. Rows matching exactly one company get Save Contact against the existing account instead. Rows matching several are not written. They go to a person, because that is where duplicates are actually made.
A closing note that reaches the record and the room at the same time
When a deal is marked won in a quoting tool, the agent calls Search Deals to find the record by name and reads its current ItemGUID and ItemVersion. Save Deal updates the status using the enum value identifier resolved from Search Enum Values rather than a hardcoded number, and Save Journal writes the closing note against the deal so the reasoning survives past the person who wrote it. Save Task then creates the handover task assigned to the delivery owner resolved through Search Users. Finally the win is announced to the sales team in Slack with the customer, the amount, and the owner. The journal entry is the part that matters six months later, when somebody asks why the discount was given.
A project view assembled from the modules that hold it
On a schedule, the agent uses Search Projects with a column filter to pull active projects, then Search Tasks and Search Journals for each one to build a picture of what has actually moved. Search Goods resolves the catalog items attached to the work. Because the Get actions have no server side paging or text filter and return every record the signed in user can see, the flow deliberately uses the Search actions with column filters instead, which keeps the response sized to the question rather than to the database. The result is a weekly status summary for each project owner, delivered by Brevo, naming open tasks, the last logged activity, and any project with no journal entry at all in the period.
Human-in-Loop Highlight
In most CRMs the operation you gate is the delete. In eWay-CRM it is not, because deletes are soft: Delete Company, Delete Contact, and Delete Deal move the record to the recycle bin and a person can restore it from inside the application. The genuinely unrecoverable mistake here is the Save. Save is an upsert whose behaviour is decided entirely by whether ItemGUID is present, so the same call creates a brand new company when the identifier is missing and updates an existing one when it is there. Neither outcome errors. An import that cannot confidently resolve a match therefore does not fail loudly, it silently manufactures a duplicate account, and every contact, deal, journal entry, and task the flow writes afterwards attaches itself to that duplicate rather than to the real customer. Nobody discovers it until a rep opens Outlook and finds two versions of an account with half the history each, and merging them back is manual work the API does not offer any help with. So the agent draws the line at ambiguity. It runs Search Companies and Search Contacts, writes every unambiguous case straight through, and stops on the rest, posting to the CRM owner: "Import of 180 rows. 141 matched exactly one company and were updated. 27 matched nothing and will be created as new accounts. 12 matched more than one: 7 are the same company name at different addresses, 4 differ only by a legal suffix, and 1 matches three records where two already carry open deals. Create the 27, and tell me which record to save against for the 12?" The owner answers once. The agent then calls Save Company with the confirmed ItemGUID and its current ItemVersion for the resolved records, which also satisfies the optimistic locking eWay-CRM applies on update, and creates only the accounts a person agreed should exist.
Agent Capabilities
28 actionsCompanies
4- Get Companies Returns companies. eWay-CRM's Get methods have no server side paging or text filter, so this returns every record the signed in user can see, which is worth remembering on a large database.
- Search Companies Searches companies using a data object keyed by case sensitive eWay-CRM column names such as `CompanyName` and `FileAs`. This is the targeted read, and the one used for duplicate checking before any create.
- Save Company Creates a company when `ItemGUID` is omitted and updates one when an existing `ItemGUID` and its current `ItemVersion` are supplied, returning the saved identifier in `Guid`. Because the same call does both, ambiguous matches are approved by a person first.
- Delete Company Moves a company to the eWay-CRM recycle bin, from which it can be restored inside the application. A soft delete rather than a permanent one.
Contacts
4- Get Contacts Returns contacts. Like the other Get actions it returns the full collection visible to the signed in user, with no server side filter.
- Search Contacts Searches contacts by column values such as `FirstName`, `LastName`, and `Email1Address`. Used to deduplicate before creating and to resolve the person on a deal.
- Save Contact Creates or updates a contact through the same upsert behaviour as Save Company, linking it to a company and returning the saved `Guid`.
- Delete Contact Moves a contact to the recycle bin, recoverable from inside eWay-CRM.
Deals
4- Get Deals Returns deals. In the eWay-CRM application this module is labelled Deals; the underlying API is the Leads folder, which matters when reading vendor documentation.
- Search Deals Searches deals by column values. Used to find an opportunity by name before updating its status or logging against it.
- Save Deal Creates or updates a deal, including its status, where status is an enum value identifier configured per database rather than a fixed code. Resolve it through Search Enum Values rather than hardcoding.
- Delete Deal Moves a deal to the recycle bin, recoverable inside the application.
Projects
3- Get Projects Returns projects visible to the signed in user.
- Search Projects Searches projects by column values. Used to pull the active set for status reporting without fetching the whole module.
- Save Project Creates or updates a project through the standard upsert behaviour. Used to open delivery work as a deal closes.
Tasks
3- Get Tasks Returns tasks visible to the signed in user.
- Search Tasks Searches tasks by column values, including assignment and state. Used to find open follow ups and overdue work.
- Save Task Creates or updates a task and assigns it to a user resolved through Search Users. Used to make a handover concrete rather than verbal.
Journals
3- Get Journals Returns journal entries visible to the signed in user.
- Search Journals Searches journal entries by column values. Used to find the last logged activity on a record and to detect silence.
- Save Journal Writes a journal entry against a company, contact, deal, or project. This is how calls, meetings, and notes become an auditable activity trail that outlives the person who created it.
Goods
2- Get Goods Returns the goods catalog visible to the signed in user.
- Search Goods Searches the goods catalog by column values. Used to resolve catalog items attached to a deal or a project.
Users
2- Get Users Returns the users on the account.
- Search Users Searches users by column values. Used to resolve the correct owner or assignee before a Save Task or a Save Deal writes one.
Reference
3- Get Additional Fields Returns the custom columns configured on this database. Used to discover fields the team added before writing to them by name.
- Search Enum Types Returns the configurable dropdown field types on this database. Used to find which fields carry enum values at all.
- Search Enum Values Returns the available values and their identifiers for a dropdown field, with localized labels returned exactly as configured in the account. Used to write a real status identifier instead of a number copied from another database.
Frequently Asked Questions
What can FlowRunner do with eWay-CRM?
FlowRunner agents can run Get Companies, Search Companies, and Save Company in eWay-CRM, plus 25 more actions.
Does connecting eWay-CRM to FlowRunner require OAuth?
No. eWay-CRM connects to FlowRunner with session-based authentication, no OAuth flow required.
Can eWay-CRM trigger a FlowRunner workflow automatically?
eWay-CRM doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with eWay-CRM
$100 in credits. No card required. Connect in minutes.