Skip to main content
Question

Connection label appears twice in App Connections for a private CLI integration

  • August 28, 2026
  • 1 reply
  • 15 views

Hi Zapier Community,

I’m seeing unexpected behavior with a private Zapier Platform CLI integration.

In the App Connections page, each connection’s Name column displays two lines. I expected:

```text
My Integration
user@example.com on tenant.example.com
```

Instead, a newly created connection displays:

```text
user@example.com on tenant.example.com
user@example.com on tenant.example.com
```

The separate App column correctly displays the integration name and private version.

These are fresh connections that have never been manually renamed, so this does not appear to be legacy metadata.

I reproduced the behavior using both supported `connectionLabel` configurations.

Function mode:

```js
const getConnectionLabel = (_z, bundle) =>
  `${bundle.inputData.memberEmail} on ${bundle.inputData.instance_host}`;

module.exports = {
  // ...
  authentication: {
    // ...
    test: testAuthentication,
    connectionLabel: getConnectionLabel,
  },
};
```

String-template mode:

```js
module.exports = {
  // ...
  authentication: {
    // ...
    test: testAuthentication,
    connectionLabel: '{{memberEmail}} on {{instance_host}}',
  },
};
```

The authentication test returns values similar to:

```json
{
  "memberEmail": "user@example.com",
  "instance_host": "tenant.example.com"
}
```

Both modes produce the expected label text, but Zapier displays that same value on both lines.

From the documentation, it appears Zapier distinguishes between:

- `title`: the connection’s user-facing, renameable display name
- `label`: the integration-generated connection label

The Platform CLI authentication schema exposes `connectionLabel`, but I cannot find a supported `connectionTitle` or equivalent property.

The CLI’s authentication-list endpoint also reports the generated connection label as the connection’s `title`. This suggests Zapier may initialize a fresh connection’s title from `connectionLabel` and then render both the title and label in the current Connections UI.

Has anyone confirmed whether this is expected behavior?

Specifically:

1. Is a new connection’s title intentionally initialized from `connectionLabel`?
2. Is there a supported CLI property for setting the initial connection title independently?
3. Can integration code produce an app-name primary line and a custom secondary label?
4. Is this duplication specific to private CLI integrations or private versions?
5. If independent control is not supported, is manually renaming every connection the only workaround?

I would like to retain the useful email-and-instance label while avoiding the duplicated display. Removing `connectionLabel` would lose the information users need to distinguish multiple accounts.

Thanks for any guidance.

1 reply

SamB
Community Manager
Forum|alt.badge.img+11
  • Community Manager
  • September 1, 2026

Hi and welcome to the Community ​@cs-NET! 👋

I’ve seen this in my own app connections for public apps as well, but like you say it’s possible for folks to rename the app connection name to be called something else. I had a look at our CLI documentation for setting the connection label and I couldn’t see any mention of being able to set a different title for the connection, just looks like only the label can be defined.

I’m not certain if it’s by design that you’re unable to set a separate title or name for the connection, so I’d suggest reaching out to our Developer Platform Support team directly about this to have that confirmed. 

Keep us posted on what they say!