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

# Publish a test post

> Send a real post to a connected account from the dashboard, without writing any code.

Select **Test** in the sidebar. This page publishes a real post to one connected profile, so you can prove a connection works end to end before your own code is involved.

<Warning>
  This is not a sandbox. The post goes to the real social account and real people can see it. Use an account you are happy to post to.
</Warning>

## Publish one

<Steps>
  <Step title="Choose a connected profile">
    The **Connected profile** dropdown lists everything you have connected, by name and handle.
  </Step>

  <Step title="Write the post">
    Up to 2,000 characters in **Post text**. Optionally add a public image or video URL in **Media URL** — it has to be reachable by Nylon, so a local file path or a link behind a login will not work.
  </Step>

  <Step title="Publish">
    Nylon publishes immediately and reports the result, with a link to the post where the network returns one.
  </Step>
</Steps>

If you have nothing connected, the page says so and offers **Manage connections** to get you to the right place.

## The publishing support list

Alongside the form is a list of networks with a **Publishing** or **Soon** badge. It tells you which networks the test form itself can reach.

<Note>
  This list is narrower than what the API supports. Nylon's publishing API covers seventeen networks; the badges here have not caught up with the most recently added ones. Treat [Supported networks](/help/supported-networks) as the authority, and the API's own network capabilities endpoint as the authority for code.
</Note>

## Inbox and analytics testing

Both tabs on this page exist and both say **Coming soon**. Neither capability is callable yet — see [Inbox](/inbox) and [Analytics](/analytics) for what is planned.

## What to use it for

* **Proving a fresh connection works** before you schedule anything against it.
* **Confirming a reconnection took**, after clearing a *Reconnect* status.
* **Checking a network's behaviour** — how it renders a link, whether it keeps your line breaks — without a deploy.

Requests made from this page appear in your [request logs](/help/request-logs) like any other, so you can inspect exactly what was sent.

## Related

<Columns cols={2}>
  <Card title="Connect an account" icon="plug" href="/help/connect-an-account">
    You need at least one connection before this page does anything.
  </Card>

  <Card title="Quickstart" icon="rocket" href="/quickstart">
    The same thing from your own backend, in a few requests.
  </Card>
</Columns>