Signal LedgerSynthetic + captured data

Connect a source

Add another tool to the queue by mapping its field names onto the one shape everything downstream understands. This is the whole idea of the architecture: the rest of the app never sees a platform's own format.

What this form does - and doesn't

It runs against the built-in mock connector. The base URL below is never contacted and the token is never stored or sent anywhere - the mock serves platform-shaped sample records, and your mapping turns them into signals through the same normaliser a real connector would use. Nothing here is connected to a real system.

1 · Source

Not contacted - the mock connector ignores it.

Discarded in your browser. Don't enter a real credential.

2 · Start from a template
Each template pre-fills the mapping with that platform's typical field names. They're starting points - real instances add custom fields, so confirm against your own.
  • Uses the Table API's default (raw) values: numeric-string priority and state, timestamps in UTC.
  • Reference fields such as company return a sys_id, not a name, so partner name is left unmapped.

Sample record the mock serves

{
  "number": "1001",
  "short_description": "Agents seeing partner portal applications hang on submit",
  "description": "Support agents handling partner enquiries say applications submitted through the portal hang for minutes before completing, and some have to be resubmitted.",
  "category": "partner-portal",
  "priority": "2",
  "state": "1",
  "opened_at": "2026-10-18 11:15:06"
}
3 · Field mapping
Where each of our fields lives in the platform's record. The last column reads your path against the sample.
Our fieldTheir field (path)Value read from the sample

The record's id in your system

1001

Short summary line

Agents seeing partner portal applications hang on submit

Longer text - used for correlation

Support agents handling partner enquiries say applications submitted through the portal hang for minutes before completing, and some have to be resubmitted.

Internal, consumer or partner - or set a default below

- not mapped -

Optional - which partner raised it

- not mapped -

Optional - the third party behind it

- not mapped -

What it's about - or set a default below

partner-portal

Translated with the table below

2

Translated with the table below

1

When it was raised

2026-10-18 11:15:06

When it was resolved - needed for SLA scoring

2026-10-18 09:40:06(from #1003, not the sample shown above)
4 · Value translations and defaults
Platforms name severities and states their own way. Translate them, and set a default for anything the source has no field for.

Severity

Status

Audience

No translations - values are matched to our audience names directly.

5 · Preview
What your mapping produces from the sample records, before anything is added.
RefTitleAreaSignal
1001Agents seeing partner portal applications hang on submitpartner portal
InternalHighOpen
1002Printer on floor 3 jamming repeatedlyworkplace
InternalLowOpen
1003Password reset request for locked accountidentity
InternalLowResolved
Sources you've added
Kept in this browser only.

None yet. The three built-in sources are always present.