# Can Claude Cowork turn a week of customer messages into Facebook Page posts?

> Source: https://tareno.co/agents/claude-cowork/facebook
> Language: en
> Last reviewed: 2026-10-24
> Hand Claude Cowork a folder of customer messages and your brand rules; it finds the recurring questions, drafts Facebook Page posts that answer them and saves them in Tareno.

## Connection facts

| Field | Value |
| --- | --- |
| Product surface | Claude Cowork (claude-plugin:claude-cowork) |
| Available connection | Published plugin |
| Connection evidence | tested |
| Methods | plugin, mcp |
| Authentication | oauth |
| Setup | [Setup guide](https://tareno.co/docs/plugins/claude) |
| Install or connect | [Open setup](https://tareno.co/docs/plugins/claude) |
| Evidence observed | 2026-10-21 |
| Facts reviewed | 2026-10-25 |

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

Agent: Claude Cowork · Network: Facebook · Hub: [Claude Cowork and Tareno](https://tareno.co/agents/claude-cowork)

## Short answer

**Can Claude Cowork use our customer messages to draft Facebook posts through Tareno?**

Yes. Claude Cowork reads the exported customer messages you share, finds the questions that keep coming back, drafts Facebook Page posts that answer them in your voice and saves them as drafts through Tareno. You remove personal details and approve every request in Tareno. Cowork cannot reply to the comments.

Every small business answers the same five questions again and again, in email, in direct messages and in Facebook comments. A post that answers them once, clearly, saves hours, but nobody has time to count which questions come most. Claude Cowork works on a folder of files, so it can read a week of exported messages, count the recurring questions and write the posts. This page follows an online plant shop through that routine, with the privacy step that matters most, which is removing names and personal details before Cowork reads a single message.

## Example: a plant shop answers its most common questions in public

Imagine a plant shop that exports a week of customer emails and Messenger questions into a folder, after removing names and order numbers. Cowork reads the files and finds that twelve people asked how to water a newly arrived plant, nine asked about delivery in cold weather and four asked about pet safety. It writes three Facebook posts in the shop's voice using the care guide in the folder, and adds a source line for each fact. It saves the drafts through `create_drafts` for the Page, reads the comments under last week's post with `list_post_comments` to see whether the watering question came up there too, and lists the result for the owner.

## Step by step

1. **Remove personal details first.** Export the messages and delete names, addresses and order numbers before they reach the Cowork folder. This is the most important step, and it is yours, not the assistant's.
2. **Share the folder and the care guide.** Put the cleaned messages, your care guide and the brand rules in one Cowork task. A guide gives Cowork something to cite, so the posts do not rely on its own general knowledge about plants.
3. **Count the recurring questions.** Ask for the questions grouped by topic with the number of messages for each. The counts tell you which three posts are worth writing this week.
4. **Draft an answer post per topic.** Request about 90 words for each topic that cites the line of the care guide it relies on. A post that points back to a source is easier to check.
5. **Compare with the public comments.** Cowork reads the comments under recent Page posts with `list_post_comments` and notes which questions also appear in public. Facebook is one of the networks where Tareno reads comments.
6. **Save, review and approve.** Cowork confirms the Page with `list_accounts`, saves the drafts through `create_drafts`, and you approve each time request in the dashboard. Meta allows scheduled posts from 10 minutes to 30 days ahead.

## Prompts to copy

### Count the questions

```text
Read the cleaned messages in the shared folder. Group the questions by topic, give me the number of messages per topic and show one anonymous example sentence for each. Do not draft any post yet, and tell me if you find a name or address I forgot to remove.
```

### Answer from the guide

```text
For the three most common topics write a Facebook Page post of about 90 words each, using only the care guide in the folder. After each post name the guide section you relied on, and tell me if the guide does not cover a question.
```

### Check the public comments

```text
Use Tareno to read the comments under our last three Page posts and tell me which of the three topics also appears there. List the counts and do not quote any comment author by name.
```

### Save the drafts

```text
Use Tareno to confirm the Facebook Page [shop name] and save the three approved posts as drafts. Return the draft IDs and request no time, because I want to read each of them in the dashboard first.
```

## Facebook in Tareno

- Facebook is a network where Tareno reads comments, so Cowork can compare private messages with public questions and decide which topic deserves a public answer first.
- Facebook posts in Tareno take a link with a preview card, so a post about delivery in cold weather can point to the shipping page.
- Meta's documentation says the Pages API posts as the Page and that an app can edit only the posts it created, so a correction to a post written on Facebook is made there.
- A public post that answers a private question can reveal who asked, so write answers in general terms and never repeat a customer's wording.

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

- Skipping the privacy step. Messages with names and addresses should never be placed in a shared task folder.
- Letting the post rely on general plant knowledge. Tell Cowork to use the care guide only and to say when the guide is silent.
- Quoting a customer. Even an anonymous quote can be recognised by the person who wrote it, so paraphrase.
- Counting messages from one noisy day as a trend. Check that the dates in the folder cover a normal week.

## What does not work

- Claude Cowork cannot reply to Facebook comments, because Tareno reads them but has no tool that publishes a reply.
- It cannot judge whether a message contains personal data you missed, so the shop owner removes it before sharing.
- It cannot publish a post on its own, because a time request becomes a post only after you approve it in the Tareno dashboard.

## Frequently asked questions

### Can Cowork read our customer messages?

It can read files you put in the shared task folder. Remove names, addresses and order numbers first, because the privacy of the people who wrote to you is your responsibility and not something the assistant can add afterwards.

### How does it decide which questions to answer?

It groups the messages by topic and counts them. You choose which topics become posts, usually the three with the most messages, and you check each answer against your own care guide.

### Can Cowork also look at the public comments?

Yes. Tareno can read comments on Facebook, so Cowork can tell you which questions also appear in public. It cannot reply to them, so you answer on Facebook yourself.

### Will it invent care advice?

It should not, if you tell it to use only the guide in the folder and to report any question the guide does not cover. Read each post against the guide before you approve a time.

### How far ahead can I schedule these posts?

Meta's documentation says scheduled API posts need a time between 10 minutes and 30 days ahead, so spread the three posts over a couple of weeks and approve each request in the dashboard.

### Does anything go live without my approval?

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_post_comments`
- `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

- [Claude Cowork × Tareno overview](https://tareno.co/agents/claude-cowork)
- [Facebook with Tareno](https://tareno.co/channels/facebook)
- [Post scheduling](https://tareno.co/features/post-scheduling)
- [Approval workflows](https://tareno.co/features/approval-workflows)
- [Claude setup guide](https://tareno.co/docs/plugins/claude)
- Use case: [Turn a folder of files into a batch of posts](https://tareno.co/agents/use-cases/batches-from-files-and-folders)