unified in twins and put this configuration under seed_config.unified.
Unified.to multi-provider API abstraction — creates integration connections that proxy to Slack, Gmail, Google Calendar, Dropbox, Box, Google Drive, or Notion.
Example seed
This is the complete Scenario request body for creating a Scenario. You can also import it witharga test-runner scenarios import --file scenario.json.
Parameters
The following fields belong directly insideseed_config.unified. Required nested fields are marked in their tables. Provider-native objects can contain service-specific fields beyond the representative record shapes below.
Seeding behavior
This seed creates integration connections. Seed messages, files, and other provider business data under the corresponding provider-specific twin keys.Resource fields
These tables describe the record shapes used by the example. Keep native field names and casing. Map keys such as property names, IDs, and metadata keys are supplied by your fixture.connections[]
API coverage and limitations
Twin name:unified
Supports
- Unified.to integration, auth, connection, webhook, and passthrough-style flows for apps that call Unified instead of a provider API directly.
- Seeded provider connections for Slack, Google Mail, Google Drive, Google Calendar, Box, Notion, and Dropbox.
- Unified calendar, messaging, HRIS, storage, KMS/page, comment, and event routes over deterministic in-memory provider state.
- Use provider-specific twins when your app talks directly to Slack, Dropbox, Google Drive, Google Calendar, Box, Notion, or another upstream provider.
- The Unified twin models generic Unified behavior and selected provider bridges; it is not a replacement for every provider-specific API edge case.
- Missing connections or provider records return structured
404or400errors.
get_twin_catalog, provision_twins, start_url_validation, get_validation_results.
See Scenario seeding for saving, provisioning, and resetting fixtures.
