> ## Documentation Index
> Fetch the complete documentation index at: https://docs.argalabs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Unified

> Unified Scenario seeding parameters, nested fields, and examples

Use `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](https://docs.argalabs.com/api-reference/post-create-a-scenario.md). You can also import it with `arga test-runner scenarios import --file scenario.json`.

```json theme={null}
{
  "name": "Unified eval fixture",
  "twins": [
    "unified"
  ],
  "seed_config": {
    "unified": {
      "connections": [
        {
          "integration_type": "slack",
          "workspace_id": "workspace_demo",
          "external_xref": "connection-owner-1",
          "environment": "sandbox"
        }
      ]
    }
  }
}
```

## Parameters

The following fields belong directly inside `seed_config.unified`. Required nested fields are marked in their tables. Provider-native objects can contain service-specific fields beyond the representative record shapes below.

| Parameter | Type | Description |
| - | - | - |
| `connections` | `object[]` | Connections fixtures in provider-native format. |

## 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[]`

| Parameter | Type | Description |
| - | - | - |
| `integration_type` | `string` | Integration type. |
| `workspace_id` | `string` | Workspace id. |
| `external_xref` | `string` | External xref. |
| `environment` | `string` | Environment. |

## 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.

**Known limitations**

* 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 `404` or `400` errors.

**MCP tools:** `get_twin_catalog`, `provision_twins`, `start_url_validation`, `get_validation_results`.

See [Scenario seeding](https://docs.argalabs.com/twins/seeding.md) for saving, provisioning, and resetting fixtures.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.