Launching today

ANKK

Launching today

Connect external AI workflows to verified social publishing

2 followers

Connect external AI workflows to verified social publishing

2 followers

Visit website

ANKK connects content from external AI tools or scripts to multi-channel social scheduling. It keeps accepted, queued, publishing, published, and failed separate, so operators can verify what actually went live. Start with three free channels.

Free Options

Launch tags:Social Media•Marketing automation•Social media marketing

Launch Team

Fin Startups get Fin free for a year + 93% off Intercom

Promoted

Maker

📌

Hi Product Hunt — I’m Minho, the maker of ANKK. I built it around a narrow operational problem: a successful scheduling request does not prove that a post actually appeared on the provider. ANKK keeps accepted, queued, publishing, published, and failed separate and retains the original post URL when the provider returns one. It does not include a built-in AI writer. The intended workflow is to prepare content in ChatGPT, Claude, Codex, another external AI tool, or your own script, then connect that output to multi-channel scheduling through the hosted app, CLI, API, or signed webhooks. The free plan supports three channels. I’d especially value feedback from people who already use social scheduling tools: where does your current workflow stop — at request acceptance, or at provider-confirmed publication?

Report

6d ago

Forum Threads

p/ankk

•

8h ago

One run, two Facebook posts: the retry question to ask first

A recent Make Community case reported one scenario run, one input bundle, and one returned Facebook post ID but two public Facebook posts.

The first recovery question is not should I rerun it? It is could the provider already have accepted a write that my execution log does not fully explain?

Before any replay:

1. freeze the scenario and export the execution;

p/ankk

•

15h ago

Launch-day lesson: accepted is not published

One launch-day reconciliation rule became very concrete today: a provider accepting a request or even marking it scheduled does not prove that the post is live.

For every channel, we keep three pieces of evidence separate:

1. the terminal publication state,

2. the provider-original post URL,

View all