Docs

Inputs & connections

Every input type explained, and how connections are granted and revoked.

Inputs are the few things a job needs from you. They are typed, validated and shown on the listing page before you install. Connections are a special kind of input: a grant to one of your apps, scoped to this job.

Input types

Type	What you provide	Example
`text`	Free text. Used for preferences, focus areas, rules.	“Pricing, hiring, partnerships”
`list`	One item per line. Builders can set a maximum.	50 company domains
`url`	A single valid URL.	https://example.com/pricing
`file`	An uploaded file. Allowed types are declared by the job.	CSV of invoices
`connection`	A grant to an app, scoped to the job. Granted at Dot connection time.	Slack #competitive-intel
`schedule`	A cron expression or preset, if the job lets you override the default.	Weekdays 07:00

Required inputs are marked on the job page. A job is Ready when every required non-connection input is filled.

How connections work

A job declares the apps it uses in connects, and the specific accounts, channels or documents it needs as connection<app> inputs. When your Dot is connected, it asks you to grant each one.

Scoped. A grant is for one job. Two jobs that both need Slack ask separately and can be revoked separately.
Minimal. The job can only read or write the destinations it declared. Writing anywhere else fails the run.
Revocable. Revoke any grant in Connections. The job pauses until the grant is restored.

Example

This is how the Weekly Competitive Report declares its inputs:

dotjob.yaml (excerpt)

connects: [web, linkedin, x, slack, notion]

inputs:
  competitors:
    type: list<url>
    min: 3
    max: 15
    description: Competitor domains, one per line
  themes:
    type: text
    optional: true
    description: Pricing, product, hiring, partnerships…
  deliver_to:
    type: connection<slack | notion | email>
    description: Where the Monday briefing is posted

Wallets and on-chain inputs

Crypto jobs take wallet addresses, ENS names, token tickers or contract addresses as list inputs. They are read-only: no job in the catalogue holds keys or signs transactions. Addresses you provide are used only by the job you gave them to. See Trust & safety.