JAMS Automate integration
Run Automate RPA Workflows in Enterprise Schedules
JAMS Scheduler runs Automate Plus and Ultimate workflows through the Automate REST API, maps workflow variables to job parameters, and monitors each run.
Execution method
Automate
No installer step
Works without enabling it in the JAMS installer
REST API port
9708 by default
What JAMS Scheduler Runs in Automate
Pick the workflow by name or ID. Its input variables show up as job parameters you can override. Schedules, dependencies, and alerts work like any other job.
How JAMS Scheduler Connects to Automate
Turn on the Automate REST API and note its port (9708 by default). JAMS Scheduler signs in with a credential that holds the Automate username and password.
One thing to plan for: Automate variables overwrite the parameters on the JAMS job. Put any JAMS parameters you need at the folder level so the job inherits them.
Requirements
Automate edition
Plus or Ultimate
REST API
Enabled, port 9708 by default
Agent
A JAMS Agent for Windows if the scheduler won’t run the workflow
Credential
An Automate login with Inquire and Get Password permissions
Automate Workflows in a Cross-Platform Workflow
An Automate workflow can wait for a SQL Server job or a GoAnywhere MFT transfer, then start a PowerShell script when it’s done.
When a workflow fails, you get the same alert as any other job.
Automate FAQ
Which Automate editions does JAMS Scheduler work with?
Automate Plus and Automate Ultimate, through the Automate REST API.
Do Automate variables show up in JAMS?
Workflow-level (shared) variables appear as job parameters you can override. Variables on individual tasks inside the workflow don’t.
What do I need to turn on in Automate?
The Automate REST API. JAMS Scheduler connects on port 9708 unless you set another.
