Skip to content
Recued
Menu
← Back to recipes

Create Segment tracking plan

by recued-core v1

Approval-gated Segment tracking-plan creation workflow. It reads existing tracking plans for context, then creates exactly one tracking plan with caller-supplied name, type, and optional description through recued-core.segment.tracking_plan.create. It does not attach sources, add rules, delete plans, mutate IAM, change write keys, or call arbitrary Segment routes.

How it works 5 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (5 steps)
name trim
Trim whitespace from setting name
has_name compare
Check if name has data
existing ?
created ?
skip: step.has_name not_equal true
card to_summary
Format results as a summary card
Settings 4 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

name setting =
type setting = LIVE
segment setting =
description setting =

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Where it runs

Device + server Runs on your device (browser) or your server.

Permissions it requires

Read your Segment connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

Data it touches

Warehousedata.trackingplan

About

Tags

segment segmenttracking-plangovernancecreateapprovalpack:segment

Details

5 steps 4 configurable settings recipe_id: create-segment-tracking-plan