Next to Robaws, not instead of it.
Robaws stays your ERP. Crewy reads what the field needs and writes back only what the back office needs. The rest stays in Crewy.
Sending a short project note along can be switched on and is off by default. Photos never go along.
| Data | When |
|---|---|
| Projects and T&M jobs | every 10 min |
| Planning and teams | every 10 min |
| Employees | every 10 min |
| Job sheets and booked hours | every 10 min |
| Articles and purchase prices | for estimating |
| Data | To Robaws |
|---|---|
| Booked hours on the job sheet | yes |
| Material lines | later |
| Short project note | optional, off |
| Photos and attachments | never |
If your environment is set to read-only, everything keeps working and nothing leaves. The queue empties as soon as writing is on.
What stays in Crewy
The conversation per job, with the whole history
Photos, voice notes and attachments
Announcements and push notifications
Who read what and when
The translations, with the original underneath
That keeps Robaws clean and keeps the daily traffic searchable in the place where it belongs.
About the integration
What do I need to connect?
An API key and secret from Robaws. You enter those in Crewy once, after that the sync runs every ten minutes. Setting it up takes a morning, including checking the employees.
Do my people need a Robaws account?
No. They log in to Crewy. For the hours we link every user to an employee in Robaws. That is a personnel record, not a paid Robaws login.
What if Robaws is down for a while?
The app keeps working on what it has. Bookings wait in the queue and leave as soon as Robaws is back.
Can I use Crewy without Robaws?
Not now. Crewy is built as a layer next to Robaws. Without Robaws is a later step, only if there is real demand for it.
Want to see what does and does not sync for you?
A demo on a real job