← Cycles
design · c72activestarted Aug 15Auto draft — not yet reviewed

Integrations Create & Manage

Looks done — ready to closeThe setup modal, the 11 connector recipes, detail-page reuse and persistence were all built and checked in one day; nothing has been added since.· medium confidence

To close: Write the Outcome (recipes, modal, detail reuse, integration_configs persistence, message previews) · Check whether the c107 cutover kept the setup modal in the Fable app and say so · Move to HISTORY.md

last activity Aug 15

Why we did this

Adding an integration led to a disabled form that said "not wired". Operators had no way to set one up, and no help finding the keys and IDs.

What happened

A guided setup window for all 11 integrations, each with real fields and step-by-step instructions, reused for editing. Notification channels also preview the exact message they'll send.

Early → finalClicking add opens a step-by-step window: where to click in the other tool, what to copy back, then review and connect.

Documents

With file names, on their own page →
At a glance
4
changes
0
conversations
3
decisions
0
outside helpers
Who helped
MPMark ParsonQpoint team

What changed

The two changes that matter most, in plain words. Open any one to see it.

  1. 1

    Clicking add opens a step-by-step window: where to click in the other tool, what to copy back, then review and connect.

    A guided setup for every integration · came from Mark Parson

  2. 2

    Slack shows a channel post, PagerDuty an incident, email a digest; each changes as you turn the knobs.

    Messages in each tool's own language · came from Mark Parson

Also in this cycle
  • Every integration has its own fields; choosing Okta or Entra ID changes the steps that follow. New in this cycle
  • On an integration's own page, the setup fields become its settings, with a link back to the guide. New in this cycle

How we got here

Each change, traced back to the conversation it came from. A solid mark means the record names the source; a dashed one was matched by the draft and waits for review.

Someone said

From the record: no recorded conversation behind this one.

We decided

c72-D1 Setup happens first in a modal, and the same UI configures existing integrations. — Mark Parson

c72-D3 Each integration speaks its own familiar language rather than teaching ours. — Mark Parson

So now

Clicking add opens a step-by-step window: where to click in the other tool, what to copy back, then review and connect.

Someone said

From the record: no recorded conversation behind this one.

We decided

c72-D2 Message previews for all three notification channels, Slack, PagerDuty and email, with both pixel-pawn and initials avatars. — Mark Parson

c72-D3 Each integration speaks its own familiar language rather than teaching ours. — Mark Parson

So now

Slack shows a channel post, PagerDuty an incident, email a digest; each changes as you turn the knobs.

Thanks to

People outside Qpoint first. Every thank-you points at something they said or made.

MP
Mark Parson
Qpoint team

Asked for setup as a living tutorial, and messages in each tool's own language

Wanted every setup to teach the operator step by step and to be reused for editing; then asked for a tunable sample alert and set the principle of meeting operators in the tools they already know.

All images

Every picture from this cycle. Click any one to step through them all.

The pairs

A guided setup for every integrationEarly → final
→
Each asks for what it really needsNew in this cycle
The same form edits it laterNew in this cycle
Messages in each tool's own languageNew in this cycle

Everything captured · 6

The full record 3 decisions · 7 key-change entries · 618 words · 0 captures

The record stays as written, for agents and for audit: Key Changes, every decision, the artifacts and the visual record.

Open the record for c72 →

Qpoint Brand Style Guide