Connect Rev.io and choose what syncs

Rev.io is the fifth PSA Current connects to, beside Autotask, ConnectWise, HaloPSA and Syncro. Rev.io stays the source of truth for time, billing and invoicing; Current owns scheduling and the views your team works in. Customers, contacts, notes, users, tickets, ticket time, projects, agreements, invoices, opportunities and quotes flow in, and the writes you allow flow back.

• ＋A Rev.io PSA administrator login, so you can create a user and an API key.
• ＋Tenant Admin role in Current. Integrations are an admin-only action.
• ＋Optional: the web address you sign in to Rev.io at, so Current can link straight to a record. Leave it blank if you're not sure.
• ＋"Prepare your Rev.io before onboarding: the setup checklist" walks the whole list if you want the smoothest first sync.

1. 1
   Create a user named Current

   A Rev.io API key carries the role of the user who creates it, and the changes Current makes are attributed to that user. A dedicated user keeps your technicians' names off records Current wrote, and keeps what the sync can see and change in one role you can read at a glance.
2. 2
   Give that user a role that reaches the areas below

   Current can only see and change what this role can. Give it read access to every area in the table, and edit access to the areas you want Current to write to. Rev.io lets a system administrator create API keys; whether a narrower role can create one is still being confirmed, so the simplest path is an administrator role on the Current user.
3. 3
   Sign in as Current and create the key

   In Rev.io PSA, open Admin, API Management and create a key while signed in as the Current user. Copy it straight into a password manager.

1. 1
   Open Settings, Integrations, Rev.io

   Only Tenant Admins see this page.
2. 2
   Paste the API key

   Add the web address too if you want "open in Rev.io" links. The key is a secret: once stored it stays server-side and is never sent back to the browser. Current exchanges it for a short-lived token on each run and never stores the token.
3. 3
   Run Test and save

   Current proves the key is real and names any area the role cannot read before anything is stored.
4. 4
   Nothing has synced yet

   Connecting stores the connection only. No data moves until the first sync runs, so you can connect, review the sync switches, and pull when you are ready.
5. 5
   Start the first sync

   Customers, contacts, notes, users, tickets, ticket time, projects, agreements, invoices, opportunities and quotes come across. A large account takes a while, because Current paces itself against Rev.io and resumes where it stopped.

Rev.io has real projects, so a Rev.io project becomes a Rev.io-synced project in Current, with its phases, milestones and work items as tasks. Building a Current project into Rev.io creates the project there. Time you log in Current goes to Rev.io as a ticket time log. On a project task it reaches Rev.io only when that task's work item is a ticket; a calendar task in Rev.io can't take time through Rev.io's API, so Current keeps the entry and says why on it. Current sends a time entry once; a correction afterwards is made in Rev.io.

Rev.io's PSA API is newer than the others Current connects to, and a few things it doesn't offer change how the sync behaves. The short version:

• ＋No "changed since" filter. Current reads newest first and stops at records it already has. If Rev.io ignores that order, Current re-reads tickets in full at most every 6 hours and saves only what changed, so a ticket edit can take up to about 6 hours to appear. Sync now pulls sooner.
• ＋No webhooks. Current checks Rev.io projects, tasks and project time every 5 minutes, customers, contacts, notes, tickets, ticket time, opportunities and quotes about every hour, and users, time log reasons, boards, agreements and invoices about every 6 hours. Nothing reaches Current the instant it changes in Rev.io.
• ＋No published rate limit. Current holds itself to 120 requests a minute while a person waits and 90 in the background, and backs off when Rev.io asks it to. A large first sync can take longer than on other PSAs.
• ＋Writes are sent once. When Rev.io doesn't answer clearly, Current reads back to check instead of sending twice. If it still can't find the time log, the entry is flagged for a person to check Rev.io, and Current does not send it again on its own, so time is never logged twice.
• ＋A time entry is sent once and not changed in Rev.io afterwards, a Rev.io task keeps one owner, and the entry's contract isn't sent, because Rev.io's time log has no field for it.
• ＋Creating a customer in Rev.io needs a street address, city, postal code, a recognised country and a default customer type set in Rev.io.
• ＋A few fields Rev.io's lists don't carry are not brought across yet: a ticket's request details and quote totals. SLA due times are filled in only for an SLA that runs around the clock.
• ＋Opportunities and quotes are read-only, and attachments, leads, surveys, holidays and time off, and the service desk's PSA ticket sync are not available for Rev.io yet.

The full list, with what you'll see and what Current does for each one, is in "Rev.io sync: the complete field-mapping reference".

Current never overwrites a Rev.io-owned field on push, and a Rev.io pull never overwrites a Current-owned field. Where a field exists on both sides and both may edit it, the most recent edit wins.

• ＋Disconnect lives in the Manage drawer's danger zone and asks you to type DISCONNECT. It stops all syncing and deletes nothing already pulled.
• ＋Projects that were syncing to Rev.io freeze rather than break: they keep their data, show a synced-to-a-disconnected-PSA state, and make no Rev.io calls until you reconnect.
• ＋Switching to Autotask, ConnectWise, HaloPSA or Syncro is disconnect then connect, from the other provider's own card.
• ＋Switching is free on a fresh workspace. Once you have synced a real book from Rev.io, connecting Autotask, ConnectWise, HaloPSA or Syncro is blocked at connect time so the two providers' records cannot collide on their ids, and the same holds in the other direction. Email support@current.day and we will run a guided migration first.