# Can Codex draft an outage notice for your Facebook Page from incident notes?

> Source: https://tareno.co/agents/codex/facebook
> Language: en
> Last reviewed: 2026-10-24
> Use Codex with Tareno to turn incident notes and the affected code into an honest outage notice and a follow-up for your Facebook Page, approved by you before it goes out.

## Connection facts

| Field | Value |
| --- | --- |
| Product surface | Codex (codex) |
| Available connection | Published plugin |
| Connection evidence | documented |
| Methods | plugin, mcp |
| Authentication | oauth |
| Setup | [Setup guide](https://tareno.co/docs/mcp/openai) |
| Install or connect | [Open setup](https://chatgpt.com/plugins/plugin_asdk_app_6a54fa8fd95c81918e64891984183432) |
| Evidence observed | 2026-10-27 |
| Facts reviewed | 2026-10-27 |

Publication status and a working connection are separate facts. Evidence for one product surface does not establish installation or compatibility in another surface.

Agent: Codex · Network: Facebook · Hub: [Codex and Tareno](https://tareno.co/agents/codex)

## Short answer

**Can Codex write an outage notice for our Facebook Page from our incident notes?**

Yes. Codex reads the incident notes and the code of the affected service, then drafts a short notice and a follow-up in plain language and saves both for your Facebook Page through Tareno. It cannot know the cause or the fix time unless your engineers confirm them, and nothing goes out until you approve it in Tareno.

When a booking or payment service goes down, customers do not look at the status page. They look at the company's Facebook Page, and they leave comments. The notice that answers them has to be fast, specific and honest, which is hard when engineers are still fixing the problem. Codex helps in two places: it reads the incident notes and the code to pin down what is actually affected, and it drafts the words. Tareno carries the draft to the Page. This page follows a ticketing company through an outage, and is clear that the assistant states what is known and never guesses the rest.

## Example: a ticketing company reports a checkout outage

Imagine a ticketing company whose checkout fails for card payments while other payment methods work. The on-call engineer pastes the incident notes into Codex and points it at the payment module. Codex reads the notes and the failing code path, and confirms that only card payments are affected. It drafts a notice of 60 words that names the affected method, says what customers can do instead and promises a follow-up without a fixed time. It saves the notice with `create_drafts` for the Page and prepares a second draft for the resolution, left unscheduled. The engineer checks both against the incident channel and requests the first for immediate posting in the Tareno dashboard.

## Step by step

1. **Paste the incident notes.** Give Codex the notes as they stand, including what is confirmed and what is still a theory. Mark the theories, because Codex should not turn a guess into a statement.
2. **Let it read the affected code.** Point Codex at the module that fails. It can tell you which flows share the failing path, for example card payments but not invoices, so the notice names exactly what is affected.
3. **Draft the notice and the follow-up.** Ask for a short notice that says what is affected, what customers can do and when the next update will come, plus a second draft for the resolution that stays empty of facts until the fix is confirmed.
4. **Remove causes and times you cannot confirm.** Read the draft for any cause or fix time that is not in the confirmed notes. Delete it. A wrong promise is worse than no promise.
5. **Save both as Page drafts.** Codex confirms the Page with `list_accounts` and saves the drafts through `create_drafts`. Facebook publishes as the Page, so it speaks as the company.
6. **Approve the first one now.** Ask for a time a few minutes ahead. Meta's documentation says scheduled API posts need at least 10 minutes of lead, and the request waits as a pending action until you approve it in the dashboard.

## Prompts to copy

### Separate fact from theory

```text
Read the incident notes below and the module [payments/card]. List what is confirmed, what is only a theory and which customer flows are affected by the failing code path. Do not draft any notice until I have confirmed the list: [notes].
```

### Draft the notice

```text
Write a Facebook Page outage notice of about 60 words for customers, using only the confirmed facts. Name the affected payment method, what customers can do instead and that a follow-up will come, without any cause or fix time. Keep it free of technical terms.
```

### Prepare the resolution

```text
Write a second short post for when the problem is fixed, with a placeholder for the confirmed time and no cause until I supply one. Use Tareno to save both posts as drafts for our Facebook Page [name] and return the draft IDs.
```

### Request the notice

```text
Ask Tareno to schedule draft [notice draft ID] as soon as the platform allows and tell me which time it asked for. Return the pending action ID and remind me that the post only goes out after I approve it in the Tareno dashboard.
```

## Facebook in Tareno

- Meta's documentation allows scheduled API posts from 10 minutes ahead, so an urgent notice cannot appear instantly through a scheduled request; plan the lead time or publish through the approved flow.
- Facebook comments can be read through Tareno, so after the notice Codex can group what customers report, such as a second failing method, and pass it to the engineers.
- Facebook posts in Tareno can include a link with a preview card, which suits a link to the status page.
- Meta's documentation says the Pages API posts as the Page and that an app can edit only posts it created, so an outage notice published directly on Facebook has to be corrected there.

Official rules ([Meta: Pages API, posts](https://developers.facebook.com/docs/pages-api/posts), checked 2026-10-24):

- The Pages API posts as the Page. The person using it must be able to perform the Page tasks CREATE_CONTENT, MANAGE and MODERATE.
- A scheduled post needs a publish time between 10 minutes and 30 days after the API request.
- An app can update a Page post only if that app created it.

## Mistakes to avoid

- Naming a cause early. A theory that turns out wrong becomes the headline of the next complaint.
- Promising a fix time. Promise the next update instead, and keep that promise.
- Forgetting the lead time. A request cannot be earlier than the platform allows, so decide quickly and approve quickly.
- Leaving the resolution post unfinished. Keep the placeholder visible so nobody schedules it by accident.

## What does not work

- Codex cannot know a cause or a fix time that your engineers have not confirmed, so those parts are always written by a person.
- It cannot reply to the customers' comments, because Tareno reads Facebook comments but has no tool that publishes a reply.
- It cannot post the notice on its own, because a time request becomes a post only after you approve it in the Tareno dashboard.

## Frequently asked questions

### Can Codex write an outage notice from incident notes?

Yes. It separates what is confirmed from what is theory, reads the code to see which flows are affected and drafts a short notice. A person checks the facts and approves the post in Tareno before it appears.

### Can the notice go out immediately?

Meta's documentation says scheduled API posts need a time at least 10 minutes ahead. Ask Tareno for the earliest allowed time and approve it in the dashboard; plan for that lead rather than for instant posting.

### Should the notice name the cause?

Only when your engineers have confirmed it. Codex can tell you what the code shows, but a cause that is still a theory does not belong in a public post. Promise an update instead of a fix time.

### Can Codex see what customers say under the notice?

It can read and group the comments, since Tareno exposes comment reading for Facebook, and report patterns such as a second failing payment method. It cannot reply, so your support team does.

### Is it safe to give Codex the incident notes?

Paste only what the notice needs. Do not include secrets, customer data or internal access details in the notes, because anything in a prompt becomes part of the conversation history.

### Does Codex post to our Page by itself?

No. A scheduling request is a pending action in Tareno, and Facebook receives the post only after you approve it in the dashboard. `get_action_status` shows what happened afterwards.

## Tareno tools used

- `list_accounts`
- `create_drafts`
- `get_action_status`

Approval model: Tareno saves drafts directly. Scheduling, publishing, edits to scheduled posts and deletions become pending actions that a person approves in the Tareno dashboard; no agent can approve them.

## Related

- [Codex × Tareno overview](https://tareno.co/agents/codex)
- [Facebook with Tareno](https://tareno.co/channels/facebook)
- [Post scheduling](https://tareno.co/features/post-scheduling)
- [Approval workflows](https://tareno.co/features/approval-workflows)
- [Codex and ChatGPT setup](https://tareno.co/docs/mcp/openai)