ANKK

Connect external AI workflows to verified social publishing

2 followers

Connect external AI workflows to verified social publishing

2 followers

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

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

2mo ago

Forum Threads

p/ankk

•

1mo ago

Which format would make social media results easier to share?

We are exploring a product direction for ANKK and would value feedback from people who regularly report social media work to clients, teammates, or partners.

The problem we keep seeing is not a lack of metrics. It is the work required to turn multiple dashboard screenshots into a result someone else can understand. The recipient still needs the date range, the content that was published, and an explanation of why a number matters.

We created five concept formats:

1. Big Number one result that represents the period.

p/ankk

•

2mo ago

Free local-only proof checker: retry, wait, or reconcile?

When a scheduled social post looks wrong, did the API return success? is usually the least useful recovery question.

Before retrying, I want five fields in one place:

1. the channel and exact account;

2. the scheduled time and timezone;

p/ankk

•

2mo 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;

View all