> For the complete documentation index, see [llms.txt](https://help.meetmadison.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.meetmadison.ai/social/social-posts.md).

# Social posts

When you want to post about something specific, create a campaign on demand. You describe what you want, **Madison writes the posts for you**, and you review and approve, then Madison publishes them across your channels.

{% hint style="info" %}
To keep posting on autopilot without writing anything, turn on [daily campaigns](/social/daily-campaigns.md) instead.
{% endhint %}

## Campaigns and posts

You start with a **campaign**, a theme or occasion, and Madison generates the individual **posts** from it, usually one tailored to each platform. You don't write posts from scratch; you approve and tweak what Madison drafts.

Madison can publish to **Facebook, Instagram, LinkedIn, X (Twitter), and Google**.

## Create a campaign

{% stepper %}
{% step %}

#### Describe what you want

Write a short prompt (for example, "promote our autumn menu"), pick an image from your [media library](/social/media-library.md), or both.
{% endstep %}

{% step %}

#### Choose placement and tone

Let Madison pick the best platforms and placements (**Auto**), or choose them yourself (**Manual**, Feed, Reels, or Story). Pick a **tone** such as Friendly, Witty, Educational, or Celebratory, and set an **impact date** for what the campaign is timed around.
{% endstep %}

{% step %}

#### Review and approve

Madison writes the copy for each platform as a starting point. Check it sounds like you, make any edits, then approve.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Nothing publishes until you approve a campaign: approval is what makes its posts eligible to go live. Posts then publish automatically at their scheduled time to the channels you've [connected](/settings/integrations.md).
{% endhint %}

## Your calendar

Open **Social** to see a calendar of your posts, which days have content and what's lined up. Posts fall into two groups: **ready for approval** and **scheduled & published**. To spot empty days, use [Post health](/social/post-health.md).

If you manage more than one location, filter the calendar by location to focus on one at a time.

## Editing a post

For any post that hasn't published yet, you can:

* Edit the **text** and change or remove the **image**
* Move the **date and time** (you can only reschedule to a future time)
* Choose which **channels** it publishes to
* Add a **call-to-action button** (on Facebook and Google), such as *Book now* or *Learn more*
* **Tag** another account by typing `@` and their name
* Switch a post **off** so it won't publish, without deleting it

{% hint style="info" %}
Once a post is published it's locked in Madison, so make your edits beforehand. If you do need to change a published post, edit it directly on the platform it was published to. A couple of platform limits to know: X captions are capped at 280 characters, and Google posts use a single image (no video).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.meetmadison.ai/social/social-posts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.