Skip to main content
Custom source is the DRE integration for a system that has no card of its own: an in-house uptime checker, a cron job, a script, or a vendor CloudThinker does not list yet. If it can send an HTTP POST with a JSON body, it can raise a Signal.
A Custom source is not the workspace webhook under Settings → Integrations → Webhooks. That one starts a conversation. A Custom source enters Pulse, so its events can be suppressed, clustered, and routed into an Incident.

​
Add a Custom source

Open DRE → Integrations and select the Custom source card. One card holds every custom source you create.
1

Name the source

Type the name your team will recognize, for example Acme uptime. CloudThinker creates the endpoint and shows its URL.
2

Send one real event

Copy the URL into your system and let it fire once. The page waits for the first delivery, then shows the JSON it received.Send a representative event, not an empty test body. The fields you can map are the fields this event contained.
3

Map the fields

Every field in the captured JSON is listed with its value. Pick the one that carries the incident title, then the ones for severity, service, resource, and description. Save.
The source is live after you save. The next event arrives in Pulse as a Signal with a real title.

​
What the mapping accepts

A mapped field is a dotted path into your JSON. event.data.title reads title inside data inside event. A list index is [0], as in alerts[0].labels.severity. There is no $. prefix. Paths that begin with $. are JSONPath and CloudThinker does not read them. You do not type these paths. You click them in the captured payload, so a mapping you can save is a mapping that resolves. Only Title is required. Map the rest when your payload carries them. A path holds at most eight segments. If your payload nests the value deeper than that, send a flatter body.

​
Authenticate the endpoint

A Custom source uses bearer authentication. Send the token in the Authorization header:

​
Verify the complete path

A 200 response proves delivery only. Open Pulse and confirm the Signal, its title, and its severity. If automatic RCA is enabled and the severity clears the threshold, confirm that the Incident enters AI is handling.
An event that arrives before you save a mapping still becomes a Signal. CloudThinker falls back to a title key in the payload, and then to Webhook signal. Nothing is dropped, but the Signal is harder to read. Map first.

​
Change the mapping later

Open the Custom source card, select the source under Signals, and edit its webhook. Incident settings, including automatic RCA and its minimum severity, live there too. A new source uses the same defaults as every other DRE webhook.
The payload shown in the picker is the last event CloudThinker stored. Stored bodies are removed after the retention period, so a source that has not fired recently has nothing to map. Fire it once more, then map.

Webhook Signals

Map events from a platform CloudThinker already supports.

Connect CloudWatch

Send CloudWatch alarm events through EventBridge.

Understand Pulse

Follow Signals through suppression, correlation, and routing.

Manage integrations

Review each platform’s connections, Signals, and outcomes.