Limited Release
This feature is available to selected accounts. Contact your Fountain team to find out whether it is available for your account.
You can set up an automation that collects a report from a tool your company has connected to Fountain, such as Workday or Dayforce, on a regular schedule. Each time the automation runs, Fountain fetches the report and imports its rows with one of your data pipelines. For example, you can import new job requisitions from Workday as openings every hour, without a file upload or a separate integration.
Before You Start
A connected tool: your Workday or Dayforce account is connected in Settings > Connectors and fully set up. Your company decides which reports Fountain can read when it sets up the user the connection signs in as.
A report that returns JSON: in Workday, a custom report shared with that user; in Dayforce, a report you can call through its Reports API.
An inbound data pipeline that accepts JSON and imports workers or openings. Set its data path to the part of the report that holds the rows; for Workday custom reports this is usually Report_Entry.
Permissions: manage automations and manage Connectors.
Set up the automation
Go to Settings > Automations and create an automation.
For the trigger, choose A recurring time and pick how often it runs: every hour or less often.
Add the action Run data pipeline import.
In the Fetch from section, pick the Connection, the API (Workday custom report or Dayforce V1), the Report path (Workday: the report's owner and name, such as /jsmith/Job_Link; Dayforce: /Reports/ followed by the report's code) and any Parameters (optional). For Workday, format = json is filled in; keep it.
Under Data Pipeline, pick the pipeline that imports the rows.
Save the automation and turn it on. The action card reads Run data pipeline: [pipeline] · from [connection].
What happens at each run
Fountain asks for the whole report once and passes it to your pipeline, which finds the rows at its data path and matches them to existing records with its matching key.
An empty report is a successful run with nothing imported. A missed run is caught up by the next one.
Limits
Runs every hour at most. The report must answer within 3 minutes, be under 50 MB and return all rows in one response.
10 automations that fetch from a connection per account, on or paused; two on the same connection must run at least 5 minutes apart.
Imports workers and openings only.
Check a run
Open the automation and select View logs. Each run shows whether it succeeded or failed, and a failed run says why. When a fetch fails, nothing is imported; fix the cause and the next scheduled run fetches the report again. If you subscribe to automation failure emails, you also get an email for each failed run. A Succeeded run means the import started; open the import in the data pipeline's logs to see each row's result.
Good to know
Fountain only reads the report and never changes data in Workday or Dayforce. It does not store your Workday or Dayforce password.
Each run imports the full report; there is no "only changes since the last run" option yet.
There is no Retry button for these runs and no preview before saving. To test, schedule the automation soon and check its log after the first run.
If the connection is removed or turned off, runs fail until you pick another connection in the action and save.
Troubleshooting
"The connection couldn't reach Workday" on a large report: the report may take longer than 3 minutes. Ask the report's owner to make it faster.
"The report had no rows at the data path": check the pipeline's data path (Workday: Report_Entry).
"The report answered, but not as a list of rows": keep format = json for Workday.
"The report has more than one page": ask the report's owner to return every row in one page.
An import fails on a missing required field on a single row: the pipeline has no data path, so the whole report was read as one row. Set the data path.