Session

As explained in Workflow , Jobs are lined up in a sequence within a single session to accomplish a desired outcome. The whole process from start to finish is called a Session.

The Workflow is designed by you by sequencing Jobs until you get to your goal and end the Session.

Multi-Entity Execution

Coordinate jobs across large numbers of entities in a single session.

Why it matters

Some user accounts (e.g., utility logins) may contain hundreds or thousands of sub-accounts or entities. Deck allows you to operate across all of them efficiently under one authenticated session (i.e. during the same Session).

Real-world example
A Deck customer connects to 1,915+ utility accounts in one Session and runs time-sensitive, scheduled Jobs to fetch fresh billing data from each — ensuring timely reporting and downstream workflows.

Define expected entities

At scale, developers often include an explicit list of expected entities (e.g., account numbers) in the job payload. This allows Deck to:

• Report clearly on those that were inaccessible or not found
• Improve data completeness and overall operational reliability

You can also deselect entities that aren’t relevant to your workflow — reducing noise, avoiding unnecessary load, and speeding up execution.

Cross-Connection Jobs

You can chain jobs that span across multiple connections, whether tied to the same or different data sources.
(e.g. Read usage from Utility A, then submit payment to Utility B)

Jobs operate under separate sessions (one per connection) but maintain traceability through shared context at the workflow level.

Because each connection has its own Session, workflows must account for Session independence — Deck helps manage identifiers and context sharing across steps.