Organize connected accounts with custom names and metadata

Postoria now supports custom names and metadata for connected social accounts.

This update is designed for teams that manage many pages, profiles, and channels. A name received from a social network is not always enough to identify the right account quickly. Several accounts may have similar names, a name may change, and a Facebook Page may be easiest to recognize by an internal client or location number.

You can now give each account a name that makes sense inside your organization and attach structured key/value data for integrations. Both options work across every social network supported by Postoria.

Give each account a recognizable name

A Custom Name replaces the social network name wherever that account is shown in the Postoria interface. It appears in account lists, selectors, previews, filters, and other places where your team chooses or reviews an account.

For example, accounts with similar public names can become:

• 113 — Downtown Store
• 279 — Airport Location
• Client A — YouTube Main

The custom name exists only in Postoria. It does not rename the page, profile, or channel on the social network, and Postoria continues to keep the original network name separately.

To set one:

1. Open the Accounts page.
2. Open the account’s options menu.
3. Select Edit.
4. Enter a Custom Name.
5. Click Save.

Custom names can contain up to 255 characters. Leave the field empty when you want Postoria to display the original name again.

Store internal identifiers as metadata

Custom names solve the visual problem. Metadata solves the integration problem.

Each connected account can now store an object of string keys and string values controlled by you. This gives an external system a stable way to associate its own record with a Postoria account without depending on a social network name.

Example metadata:

{
  "channel_number": "113",
  "owner_account": "acme-media",
  "region": "north-america"
}

You might use metadata for:

• An internal channel, client, or location ID
• The team or owner responsible for the account
• A region, brand, department, or campaign group
• A reference used by your CMS, CRM, DAM, or automation system

An account can contain up to 50 metadata entries. Keys can contain up to 64 characters, values can contain up to 1,024 characters, and key casing is preserved.

Metadata is intentionally flexible. Your workflow decides what the keys mean, so you do not need a new Postoria field every time your internal account model changes.

To manage metadata in the web app, open the same Edit dialog on the Accounts page and add or remove key/value rows there.

Manage the same data through the Public API

The social account list endpoint now returns custom_name and metadata together with the original account fields:

GET /v1/workspaces/{workspace_id}/social-accounts

That means one request can return the complete mapping needed by an integration.

You can update either or both fields for one connected account with:

PATCH /v1/workspaces/{workspace_id}/social-accounts/{social_account_id}

Example request:

{
  "custom_name": "113 — Downtown Store",
  "metadata": {
    "channel_number": "113",
    "owner_account": "acme-media"
  }
}

Omitted fields remain unchanged. When metadata is supplied, it replaces the complete metadata object rather than merging individual keys. Set it to null to clear it.

The original name remains available in API responses. This keeps the value received from the social network distinct from the custom name used by your team.

Keep the mapping when an account is reconnected

Custom names and metadata belong to the connected account in Postoria, not to its current authorization token. They remain in place when the account is reconnected or re-authorized.

This is especially useful for long-running integrations. A changed public name or a renewed authorization no longer forces your system to rebuild its account mapping.

Use custom names and metadata together

The two features are complementary:

• Custom Name gives people a clear label everywhere they work in Postoria.
• Metadata gives software a structured mapping it can read and update through the API.

A team can display 113 — Downtown Store in Postoria while its integration stores "channel_number": "113". People get a readable account selector, and the external system gets a stable identifier.

Available now

Custom names and metadata are available now for connected accounts in the Postoria web app. Public API access is available on Pro and Agency plans.

Open the Accounts page and select Edit on any connected account to get started. For complete instructions, read How to connect and customize an account in Postoria. Developers can find request examples and exact update behavior in the Postoria Public API guide.