IFTTT, Zapier, and the Cowpin API: Automation Without Lock-In

If you save links for research, you eventually want automation: RSS items into a library, form submissions turned into bookmarks, or a notification when something important is archived. The trap is picking a bookmark app that only automates well inside one vendor’s walled garden.

Cowpin is deliberately boring here: your library is exportable, and automation rides on open surfaces — Pinboard-style REST, API tokens, MCP for agents — with Zapier and IFTTT as optional no-code layers on top.

What works today (no waiting on a marketplace)

Pinboard-compatible REST at https://www.cowpin.com/api/v1/ is the dependable path. Create a token under Settings → API, then call posts/add, posts/get, and posts/recent from shell scripts, cron, CI, or any platform that can HTTP GET with query parameters.

That is the same contract Pinboard users have relied on for years — so existing “save this URL” recipes often need only a host and token change. See Automate your bookmarks with the Cowpin API for copy-paste examples.

IFTTT Webhooks (and similar) can hit the API with a token today without an official “Cowpin” tile on IFTTT. It is more manual than a first-class service, but it avoids lock-in while you evaluate no-code tools.

Zapier: built, not yet a public directory app

We ship a Zapier Platform app in the Cowpin repo: triggers for new bookmarks (and new bookmarks with a tag), actions to save and find by URL, and rate-limit handling so Zaps retry cleanly on 429s.

The integration is not listed in Zapier’s public marketplace yet — that path goes through Zapier’s partner/review process, not a missing feature in the app itself. Until the listing is live, treat API + export as production and Zapier as “ready to connect once published.”

Planned use cases match what bookmark power users expect: save from forms, calendar-adjacent workflows, task tools, and team notifications when a tagged link lands in the library.

IFTTT: Service API in production, Platform review still ahead

IFTTT requires a dedicated Service API and OAuth2 (API keys in trigger fields are not approved for user data). Cowpin now exposes:

• GET /api/ifttt/v1/status — health check for IFTTT’s endpoint tests
• OAuth at /api/oauth/ifttt/authorize and /api/oauth/ifttt/token
• Triggers such as new bookmark and new bookmark with tag
• Action save bookmark (with Realtime notification when configured)

That code can run on www.cowpin.com once operator env vars and database tables are in place. It does not mean Cowpin appears on IFTTT’s public catalog yet — IFTTT still reviews the service, expects polished copy and logos, and asks for published Applets before launch.

We are not using “Works with IFTTT” marketing until that review completes. If you are evaluating IFTTT, use the API or Webhooks now; watch for the official service when we announce it.

How to think about Zapier vs IFTTT vs API

The product rule is simple: one canonical library in Cowpin, deliberate outputs everywhere else — not five silos pretending to stay in sync.

Multi-tool setup (same as our integration guide)

A healthy stack might look like:

• Cowpin — save, tag, full-text archive, highlights, export
• Notion or Obsidian — project notes and long-form writing (one-way export)
• Zapier or IFTTT — repetitive “when X, save link Y” once listings are live
• MCP — agents that recall sources with citations

More context: How to use Cowpin with Notion, Obsidian, Zapier, and more.

Start with import, then automate

Most automations fail when the underlying library is empty or trapped in a closed app. Import first (Pocket, Raindrop, Pinboard, HTML, and others in Settings → Import), then wire one small script or Applet that saves a single test URL.

Start a free trial and build the library you actually want to automate.