Signal OS integration catalogue · Structured imports

Bring a customer-controlled source into an inspectable signal workflow.

CSV and structured imports are listed across every public Signal OS plan, including Proof of Signal. They provide a bounded route for customer-supplied account, building or signal context without consuming a mailbox or calendar identity.

Published catalogue position

CSV and structured imports has a defined role in the Signal OS stack.

A structured import is an input, not a conclusion. Signal OS keeps the source context, qualification and governed action distinct.

Included in the public catalogue for
Proof of Signal · Focus · Momentum · Command
Mailbox/calendar identity use
This connector does not consume mailbox or calendar identity capacity.
Third-party commercial terms
The customer remains responsible for the source data and permission to use it.

A bounded workflow

Use the connection to support qualification—not to bypass it.

External data remains untrusted until it is validated, connected to an account and preserved with its source context.

01 / Prepare

Use a bounded, documented source

Define the entities, fields and purpose before importing customer-controlled data.

02 / Validate

Treat every imported value as untrusted

Check format, required identifiers and provenance before using values in structured qualification.

03 / Qualify

Connect data to current evidence

Use the import as context for a human-inspectable commercial hypothesis and next step.

What the catalogue supports

  • CSV and structured imports are listed for Proof of Signal, Focus, Momentum and Command
  • Structured imports do not consume mailbox or calendar identity capacity
  • The customer remains responsible for the source, accuracy and lawful use of imported data

What this page does not claim

  • That arbitrary files or unsupported fields will be accepted
  • That imported values are independently verified by Signal OS
  • That an imported lead or status proves current buying intent

Rollout gate

Inspect scopes and behaviour before production use.

  • Verify the enabled connection in the target workspace
  • Approve the exact data path and permissions
  • Test failure, retry and audit visibility
Discuss integration controls