[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Chase Sendible posts waiting for client approval

> Find Sendible posts stuck in client approval, send drafts to the right approver and spot tasks that already passed their publish time.

Source: https://cotlet.dev/integrations/sendible-api-mcp-server/chase-client-approvals

The client was meant to approve Friday's posts on Wednesday. It is Thursday night, the tasks sit unopened in their dashboard and the posts are about to miss their slot.

Cotlet does it in your own Sendible account with list\_tasks, list\_posts, list\_users and send\_for\_approval, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=sendible) [All Sendible tools](https://cotlet.dev/integrations/sendible-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can Sendible do this on its own?

Sendible sends one dashboard notification and one email per approval request (checked 20 Oct 2026), and nothing more if the task stays open. Its Zapier app can approve a draft post by ID. It has no action to list tasks, send a post for approval or reject one. Approval workflows are not on every plan.

## How you do it in Sendible today

1. Create and schedule the post on the client's dashboard, because clients see only posts made in their own dashboard.
2. Switch to your own dashboard from My dashboard in the top-left corner, open the post and click Send For Approval.
3. Choose the client who should approve it, add a comment and click Send For Approval. The client gets a dashboard notification and an email.
4. Follow the request in Publish > Tasks, using For Me, For Others or Done.
5. Sendible sends no reminder for a task left open, so you open For Others every day and look for old ones.

## How to chase Sendible posts waiting for client approval

Prompt

```
List every post I sent for approval that is still open, oldest first. Flag those already past their publish time, and send the unsent drafts for Harbor Dental to Mia Harbor for approval.
```

1. 01  
### List what is open  
list\_tasks with view set to for\_others returns the tasks you assigned, newest first. Each task carries the approver, the comment and Sendible's own label, "Scheduled for" or "Received on".
2. 02  
### Sort by the clock  
A "Scheduled for" task still has time. A "Received on" task is past its publish time, so the agent puts it at the top of the report and warns that approving it sends the post at once.
3. 03  
### Find drafts nobody sent  
list\_posts with status draft shows posts saved in Publish > Drafts. The agent compares them with the posts your prompt says should be approved and skips drafts without a scheduled time.
4. 04  
### Send for approval  
send\_for\_approval attaches the draft to the approver whose user\_id list\_users returned for the client, with a comment naming the deadline. Each call waits for your OK by default, because the approver gets an email.
5. 05  
### Report who is slow  
The agent lists open tasks per approver, with the age of each. It does not message anyone beyond the approval request itself.

### What you get back

Example data

```
Open approvals for Harbor Dental: 4
Sent now: 2 drafts to Mia Harbor, due Thursday 17:00
Waiting, still on time: 1 (Friday 09:00)
Past their publish time: 1 ("Received on" 19 Oct, approving sends it at once)
No scheduled time, skipped: 0
```

### Other ways to ask

- Every weekday at 16:00, list tasks that go out in the next 24 hours and have not been approved.
- Approve all tasks assigned to me for the Northside Bakery workspace, except any marked "Received on".
- Reject the three posts that mention the old price and add the comment "Price changed on 1 Nov".

## What Sendible allows, and what to know first

- A Sendible task past its post's scheduled time says "Received on", and approving it sends the post immediately, so reschedule it first if that is not wanted.
- Marking a task as done is not the same as approving it: the post goes out only after approval.
- Rejecting a post returns it to the sender's task list with the comment followed by "\[Rejected\]".
- A user can be set so that all their posts are sent for approval before publishing, and a workspace can have one Post approver for all posts.
- Sendible says approval workflows are not available on all plans.

send\_for\_approval asks for your OK by default. To run it daily without you, switch confirmation off for that tool in your dashboard.

Sources: [Sendible Help: Send messages for approval](https://support.sendible.com/hc/en-us/articles/208052076-Send-messages-for-approval) · [Sendible Help: Work with approval tasks and assigned messages](https://support.sendible.com/hc/en-us/articles/208052616-Work-with-approval-tasks-and-assigned-messages) · [Sendible Help: Overview of workspaces](https://support.sendible.com/hc/en-us/articles/37106656204317-Overview-of-workspaces) · [Sendible Help: Set up clients](https://support.sendible.com/hc/en-us/articles/360014576251-Set-up-clients)

## Call send\_for\_approval from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/sendible/posts/post_77a1/approvals \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"approver_id":"usr_88","comment":"Please approve by Thursday 17:00. It goes out Friday at 09:00."}'
```

Example response

```
{
"post_id": "post_77a1",
"task_id": "task_5502",
"status": "for_approval",
"approver": "Mia Harbor",
"send_at": "2026-10-23T09:00:00+01:00"
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is sendible\_write → send\_for\_approval. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/sendible-api-mcp-server.md#automations)

## Sendible tools this automation uses

__Cotlet Sendible tools used to chase Sendible posts waiting for client approval__
| Tool | Parameters |
| ------------------- | ------------------------------------------------------------------------ |
| list\_tasks | workspace\_id, view, from, to |
| list\_posts | workspace\_id, status, network, profile\_id, queue\_id, from, to, cursor |
| list\_users | workspace\_id, type |
| send\_for\_approval | post\_id, approver\_id, comment |

[All 14 Sendible tools with descriptions](https://cotlet.dev/integrations/sendible-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect Sendible to Cotlet?

Yes. You sign in to Sendible yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Sendible once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More Sendible automations

- [Triage the Sendible Priority Inbox with AI](https://cotlet.dev/integrations/sendible-api-mcp-server/triage-priority-inbox.md)
- [Weekly Sendible client report for every workspace](https://cotlet.dev/integrations/sendible-api-mcp-server/weekly-client-report.md)
- [Sendible API and MCP server: every tool](https://cotlet.dev/integrations/sendible-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Sendible.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Sendible.

[Sign up free](https://cotlet.dev/app/signup?app=sendible)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.