Override one connection

You have one published connector, but one customer needs it to behave a little differently. Instead of forking the spec, attach a connection override — a partial spec merged onto the pinned base at load time.

Example: a smaller page size for one customer

On the connection detail page, open the Spec overrides editor and enter only the delta:

resources:
  - key: deals
    fetch:
      pagination:
        pageSize: 25

Save. The editor merges this onto the base spec and re-validates the result; if it's valid, it's stored on the connection. The next run fetches 25-at-a-time for this customer only — every other connection on the same connector is untouched.

Example: an extra output column

resources:
  - key: deals
    output:
      fields:
        - { name: REGION, type: string }

output.fields merge by name, so this adds REGION to the connector's columns rather than replacing the list. (You'd also map REGION — which for a new value means overriding the transform expression, since JSONata is a single string.)

What you can override

Anything in the spec: defaults (rate limit, timeout, retry), a resource's fetch/pagination, enrich calls (added by id), output.fields (by name), the transform expression, sync policy. Keyed arrays merge by their natural key; scalars and plain arrays replace; null deletes. See the full merge semantics.

Verifying it

Trigger a sync and open the Run Inspector: the fetch:list calls in the call log will show the overridden PageSize, confirming the effective spec is what you expect.