architect-data-integration

Design Cloud Data Ingestion sync patterns for external warehouse data into Braze.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/delta-and-beta/braze-agency --skill architect-data-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect-data-integration
Source: https://github.com/delta-and-beta/braze-agency/tree/main/skills/architect-data-integration
Command: npx skills add https://github.com/delta-and-beta/braze-agency --skill architect-data-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Designs architecture and operational patterns to reliably sync external warehouse data into Braze via Cloud Data Ingestion (CDI), reducing data freshness gaps, avoiding race conditions with user merges, and improving pipeline recoverability.

Core Features & Use Cases

  • Trigger and Orchestrate Syncs: Guidance for programmatically triggering CDI integration syncs and coordinating downstream workflows.
  • Status Polling & Recovery: Patterns for polling job status, interpreting terminal states, and implementing retry/backoff on failure.
  • Multi-integration Fan-out & Enumeration: Use List endpoints to discover integrations dynamically and fan-out triggers safely with permission scoping.
  • Merge Sequencing: Recommendations for sequencing user merge operations relative to CDI syncs to preserve data on canonical profiles.
  • Pagination & Permission Handling: Best practices for cursor-based pagination, API key permission separation, and audit-friendly status collection.

Quick Start

Trigger a CDI integration sync by integration_id, poll the job status until it reaches a terminal state, and report whether the sync succeeded or failed.

Frequently Asked Questions about architect-data-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trigger a Braze CDI sync and poll its job status?

To trigger a Braze CDI sync, you programmatically initiate the job by integration_id, then poll the job status until it reaches a terminal state to report whether the sync succeeded or failed.

What is the best way to handle retry and backoff for Cloud Data Ingestion failures?

Handling CDI failures requires polling job status for terminal states and implementing retry/backoff recovery strategies to improve pipeline recoverability and resolve data freshness gaps.

How do I sequence user merge operations with Braze CDI syncs?

Sequencing user merge operations relative to CDI syncs requires specific orchestration patterns to preserve data on canonical profiles and avoid race conditions during warehouse data ingestion.

How do I list and fan out triggers across multiple Braze CDI integrations?

You can use List endpoints to dynamically discover integrations and safely fan-out triggers across them, applying permission scoping and cursor-based pagination to collect audit-friendly statuses.

Does this CDI orchestration pattern support idempotent triggers and API key permission separation?

Yes, the CDI orchestration pattern supports idempotent triggers, API key permission separation, and cursor-based pagination handling to ensure safe multi-integration fan-out and audit-friendly status collection.