Quick Answer
Keragon does not currently support native two-way syncing between apps. Here is what that means and how to think through your options.
How Keragon Workflows Work
Each workflow is built around two core concepts. A trigger is the event that starts everything — something that happens in an app like a new record being created, a form being submitted, or a status being updated. Once that event fires, actions are what you do with that data, whether that is sending it to another app, transforming it, creating a record somewhere else, or triggering a notification. Data always flows in one direction, which keeps things predictable, traceable, and reliable.
Can You Simulate Two-Way Sync?
Technically, there are some workarounds, but they are exactly that: workarounds. They require careful planning and only work in specific scenarios.
One example is calendar syncing for new events. You could build two workflows that each listen for new events in their respective apps and use a flagging mechanism to determine where the data originated. If a new event was created by a Keragon workflow, the flag signals that it should not continue, avoiding an infinite loop. If the event came directly from the source, it is genuinely new data and should be pushed to the other app. This pattern can work, but it requires your apps to support custom field flagging and it only holds up for new record creation.
Unfortunately, the same approach does not work for updates. Most platforms do not tell you what specifically changed on a record — they simply notify you that something was updated. Because of this, there is no reliable way to attach a flag that distinguishes a Keragon update from a user update, making it impossible to prevent an infinite loop. Two-way syncing for updates is not achievable without significant risk.
Why Two-Way Sync Creates Problems
When both workflows are active, you risk creating a data loop. Here is what that looks like in practice:
- Workflow 1 fires and updates App B
- App B detects a change and triggers Workflow 2
- Workflow 2 fires and updates App A
- App A detects a change and triggers Workflow 1 again
This loop can spin indefinitely, which means duplicate records, inconsistent data across your systems, and your workflow run limits getting burned through fast. Even when a loop does not fully spiral, two-way syncing introduces a harder question: if a record exists in both apps and they conflict, which one is correct? Without a clear answer, data integrity becomes a real risk.
What We Recommend Instead
Before building any workflows, take the time to evaluate your data transfer needs. Ask yourself: what is my source of truth, and how should data flow between my systems? Having a clear answer to that before you start will save a lot of complexity down the line.
The cleanest and most reliable pattern is to define a Single Source of Truth, meaning one app owns the data and all workflows flow in one direction from there. This typically looks like one of two patterns:
- Push outward: Always push from your source of truth to external apps when a record is created or updated.
- Pull inward: Always pull from an external source into your source of truth, keeping your core system up to date.
Either way, data flows in one direction, ownership stays clear, and you avoid the risks that come with syncing in both directions.
If a true two-way sync is a hard requirement for your use case, Keragon may not be the best fit as a solution.
Frequently Asked Questions
Does Keragon support two-way syncing?
Not natively. Keragon workflows are built around one-way data flow: a trigger in one app kicks off actions in another. This keeps data movement predictable and reliable.
Why does Keragon not support two-way sync?
Two-way sync introduces the risk of infinite loops, where two workflows trigger each other endlessly, causing duplicate data and burning through run limits. One-way workflows are intentional by design to prevent this.
What is a one-way workflow exactly?
A one-way workflow starts with a trigger — an event that happens in an app such as a new record being created or a form being submitted — and then performs actions with that data such as sending it to another app, creating a record, or triggering a notification.
Can I still move data between two apps?
Yes, absolutely. You can move data between any two apps using Keragon. The key is that data flows in one direction per workflow, from a source to a destination.
Is there any way to simulate two-way sync?
In limited scenarios, yes. You can create two separate workflows that mirror each other and use a flagging mechanism to determine whether data came from Keragon or directly from a user. If it came from Keragon, the workflow stops. If it is fresh user data, it gets pushed through. This only works reliably for new record creation, not updates.
Can you give me an example of when the workaround works?
Calendar event syncing is a good example. If a new event is created directly in App A, Workflow 1 pushes it to App B. If that same event was already created by Keragon, the flag prevents Workflow 2 from firing it back to App A. This avoids the loop, but only when your apps support custom field flagging.
Why does the workaround not work for updates?
Most platforms do not tell you what specifically changed when a record is updated. They only notify you that an update occurred. Without knowing the origin of the change, there is no reliable way to apply a flag and stop the loop from happening.
What happens if I try to set up two-way sync without a flagging mechanism?
You risk creating an infinite loop. Workflow 1 updates App B, which triggers Workflow 2, which updates App A, which triggers Workflow 1 again. This repeats indefinitely until your run limits are exhausted or data becomes inconsistent across both systems.
Can I use a Continue If step to prevent the loop?
Yes, a Continue If step can help control flow in some scenarios. For example, you could set a condition that only allows the workflow to proceed if a specific flag value is present. However, this still depends on your apps being able to stamp data with a recognizable origin field.
What is a Source of Truth?
A Source of Truth is the one app that owns and controls your data. All workflows should flow from that app outward to other systems, or from external systems into it. This keeps data consistent and eliminates conflicts.
How do I decide which app is my Source of Truth?
Ask yourself where data is primarily created and managed. Whichever app your team relies on most for accurate, up-to-date records is typically your Source of Truth.
What if my team uses both apps equally and I cannot pick one?
This is a common challenge and usually a sign that the workflow architecture needs to be evaluated more carefully. In this case, it is best to connect with our team to assess your setup before building any workflows.
Is Keragon the right tool if I need true two-way sync?
If two-way sync is a hard, non-negotiable requirement, Keragon may not be the best fit for that specific use case. We would rather help you find the right solution than push a workaround that creates more problems than it solves.
Who should I talk to if I am unsure how to structure my data flow?
Reach out to our support via support@keragon.com or try out our new AI Editor within the app.
Will Keragon add native two-way sync support in the future?
We are always evaluating our product roadmap based on customer needs and could release a new product down the road.