ApivomApivom
Get Demo

Apivom Staff — workflow orchestration that keeps going

Staff is the workflow orchestration and browser automation layer behind the Apivom products. Long-running jobs survive restarts, failed steps are retried, and portals without an API are automated. Staff is included with the products and is not sold separately.

Infrastructure layer

Staff in numbers

5
Dedicated execution pools, one per product area
30days
Days of run history
3
Human-in-the-loop signals: captcha, 2FA code, one-time code

Background work that does not get lost

Syncs, renewals, scheduled jobs and portal tasks run durably, with every step recorded and a person brought in only when one is needed.

Durable workflows

Long-running work picks up where it stopped after a restart or a deploy, instead of starting over or disappearing.

Schedules

Run work every minute, hourly, daily or weekly. Some schedules skip a run when the previous one is still going, so jobs do not pile up.

Portal automation

Partner portals that have no API are automated in a real browser, with the session and each step handled for you.

Human-in-the-loop

When a portal asks for a captcha, a 2FA code or a one-time code, the workflow waits for a person and then resumes.

Retries and run history

Failed steps are retried, and every run is kept for 30 days so you can read what happened instead of guessing.

Encrypted payloads

Workflow payloads are encrypted before they leave the process, and operators decode them only after signing in.

Included with the products

How the Apivom products use Staff

You do not set Staff up on its own. It is the engine the products lean on for work that takes time, repeats on a schedule or has to wait for someone. Here is where it runs today.

  • Iris. Vendor and CRM syncs, subscription renewals and reminders, support SLA sweeps and mailbox sync, plus portal automation for Autodesk Partner Center, Penta’s Bayinet and Dassault Systèmes orders.
  • Mars. Weekly content planning, blog production and publishing, social posts on a schedule, and WhatsApp campaign dispatch.
  • Pivot and Orbit. Pivot’s views are refreshed hourly by a scheduled workflow. Orbit analytics syncs also run through Staff.
  • Halo and Abu. Halo archives sessions, sends follow-ups and handles data export and erasure. Abu builds embeddings daily and runs hourly alert and digest sweeps.
Portals without an API

Portal automation that waits for a person when it has to

Some partner portals can only be used through a browser, and they ask for things a script cannot answer. Staff automates the steps it can and hands the rest to a person, then carries on.

  • A real browser session. Logins and sessions are managed, and each workflow checks its work by reading the result back.
  • Captcha, 2FA and one-time codes. A person supplies the code to the waiting workflow, which then resumes from that step.
  • A time limit on waiting. A step waits for a person for a set time, so a forgotten request does not block work forever.

Frequently asked questions

What is Apivom Staff?

Staff is workflow orchestration and browser automation. It runs long-running jobs that survive restarts, retries failed steps, keeps a run history, runs work on a schedule and automates partner portals that have no API. The Apivom products use it for syncs, renewals, content and portal tasks.

Is Staff sold separately?

No. Staff is an infrastructure layer that is included with the Apivom products. You do not buy or set it up on its own. If you want to know what it does for your use of Iris, Mars or the other products, talk to us.

How does portal automation handle logins and 2FA?

Staff drives a browser through the portal. When the portal asks for a captcha, a 2FA code or a one-time code, the workflow pauses and waits for a person to provide it, for a limited time. It then resumes from the same step. There are three such human-in-the-loop signals.

What happens when a step fails?

Failed steps are retried, and the workflow keeps its state while it does. Each run is recorded, and the run history is kept for 30 days, so you can see which step failed and why. Work that was already done is not repeated from scratch.

Which Apivom products rely on Staff?

Iris uses it for vendor and CRM syncs, renewals, support SLAs and portal automation. Mars uses it for content planning, publishing and WhatsApp campaigns. Pivot views are refreshed hourly through it, and Halo and Abu use it for their scheduled and background work.

Do I see Staff directly?

Mostly you see its results inside the products: data that is up to date, renewal reminders sent, content published. Apivom operators follow runs in a branded console behind sign-in. Where a workflow needs a person, such as a portal code, the request reaches you through the product.

Background work you can rely on

Staff comes with the Apivom products. Talk to us about the work you want to stop doing by hand.