WorkflowMax2 Python API Docs | dltHub

Build a WorkflowMax2-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

WorkflowMax2 REST API is an API for accessing the WorkflowMax job management tool, allowing interaction with entities such as jobs, clients, quotes, invoices, and timesheets. The REST API base URL is https://api.workflowmax.com/v2 and all requests require a Bearer token for authentication and an Account ID in the header.

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading WorkflowMax2 data in under 10 minutes.


What data can I load from WorkflowMax2?

Here are some of the endpoints you can load from WorkflowMax2:

ResourceEndpointMethodData selectorDescription
clientsclientsGETClientsRetrieve a list of clients
jobsjobsGETJobsRetrieve a list of jobs
invoicesinvoicesGETInvoicesRetrieve a list of invoices
quotesquotesGETQuotesRetrieve a list of quotes
staffstaffGETStaffRetrieve a list of staff members
timesheetstimesheetsGETTimesheetsRetrieve a list of timesheets

How do I authenticate with the WorkflowMax2 API?

All requests require a Bearer token in the Authorization header and an Account ID in the header for authentication.

1. Get your credentials

WorkflowMax2 uses OAuth 2.0 Authorization Code flow, not static API keys. 1. Go to the developer portal at https://developer.workflowmax2.com/apps. 2. Register your application to receive a Client ID and Client Secret. 3. Configure your Redirect URI in the portal (ensure it is HTTPS). 4. Use the Authorization Code flow by directing users to https://oauth.workflowmax2.com/oauth/authorize with your client_id, redirect_uri, and requested scopes. 5. Exchange the authorization code at https://oauth.workflowmax2.com/oauth/token for an access token and refresh token. 6. Use the access token in the Authorization header as 'Bearer <access_token>' for all API requests.

2. Add them to .dlt/secrets.toml

[sources.workflowmax2_source] client_id = "your_client_id_here" client_secret = "your_client_secret_here" account_id = "your_organisation_id_here" redirect_uri = "your_redirect_uri_here"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

uv run dlthub ai toolkit install rest-api-pipeline

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the WorkflowMax2 API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

uv run python workflowmax2_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline workflowmax2_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset workflowmax2_data The duckdb destination used duckdb:/workflowmax2.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

uv run dlthub show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads /authentication/obtain-tokens and /authentication/refresh-tokens from the WorkflowMax2 API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def workflowmax2_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.workflowmax.com/v2", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "clients", "endpoint": {"path": "clients", "data_selector": "Clients"}}, {"name": "jobs", "endpoint": {"path": "jobs", "data_selector": "Jobs"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="workflowmax2_pipeline", destination="duckdb", dataset_name="workflowmax2_data", ) load_info = pipeline.run(workflowmax2_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("workflowmax2_pipeline").dataset() sessions_df = data.clients.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM workflowmax2_data.clients LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("workflowmax2_pipeline").dataset() data.clients.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load WorkflowMax2 data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI harness:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for WorkflowMax2?

Request dlt skills, commands, AGENT.md files, and AI-native context.