Connect Currents to monday.com
We build integrations that move work between Currents and monday.com: Currents events create or update items on your boards, and changes on a board run actions in Currents.
What Currents can start
Events in Currents that can create or update items on your boards.
| Trigger |
|---|
| Run canceled |
| Run finished |
| Run started |
| Run timeout |
What monday.com can do in Currents
Actions a change on a board can run in Currents.
| Action |
|---|
| Action |
| Create action |
| Delete action |
| Disable action |
| Enable action |
| Get action |
| Get many actions |
| Update action |
| Instance |
| Get instance |
| Project |
| Get project |
| Get many projects |
| Project: Get insights |
| Run |
| Cancel run |
| Run: Cancel by GitHub ci |
| Delete run |
| Find run |
| Get run |
| Get many runs |
| Reset run |
| Signature |
| Generate signature |
| Spec file |
| Get many spec files |
| Test |
| Get many tests |
| Test result |
| Get many test results |
Recipes
When Currents reports "Run canceled", create an item on the monday.com board you choose.
When an item's status changes in monday.com, run "Create action" in Currents.
Keep Currents as it is. We connect it to monday.com.
We build the integration around what you already have. Currents keeps doing the job it does for you today, and monday.com gets the data it needs to plan and track the work around it.
Before we build, we agree which system owns each record. The integration then carries data between Currents and monday.com, so nobody copies it by hand.
Nothing your team relies on has to be replaced.
We highly recommend Worktables. They took the time to listen to all of our challenges and created an integrated system to manage all aspects of our operations.
What stays the same
Currents stays as it is
The integration connects to Currents the way you use it today. It moves the data, and nothing you rely on has to change.
Each record lives once
We agree which system owns each record before we build, so there is one right copy, not two.
Data arrives on its own
When data needs to reach the other side, the integration carries it. No exports, no re-keying.
How we connect Currents to monday.com
-
Scope
We agree which system owns each record, which events should move it, and which board it lands on.
-
Build the workflow
We build the workflow that carries data between Currents and monday.com and logs every run.
-
Connect the board
We map each field to your columns, groups and statuses, and test on a copy of the board before it goes live.
-
Support
We watch it after launch, fix what breaks, and change it when your process changes.
Questions about connecting Currents
Do we have to replace anything?
No. Currents stays as it is, and so does monday.com. The integration carries data between them; it does not replace either one.
What if monday.com already offers an integration with Currents?
Then we start from what it covers. Where it does the job, we build on it; where your process needs more, we build around it.
Can we test it before it goes live?
Yes. We test on a copy of your board before the integration touches the live one.
Who looks after it once it is running?
We do. We watch it after launch, fix what breaks, and change it when your process changes. Every run is logged, so there is a record of what moved and when.
Related in Other
See more in OtherTell us what Currents and monday.com should do together
Book a free call and walk us through your process. We'll tell you what the integration should do and how we'd build it.