marky

n8n nodes for the Marky REST API: list workspaces and connected accounts, create and schedule posts, upload media from a URL, and trigger on post.published.

Package Information

Released: this month
Downloads: 0 weekly / 0 monthly
Latest Version: 0.1.1

Documentation

n8n-nodes-marky

n8n community nodes for the Marky REST API.

Install in n8n: Settings > Community Nodes > Install, package
n8n-nodes-marky.

Credential: Marky API

  • API Key: from your organization's API settings (starts with mk_live_).
  • Base URL: defaults to https://api.mymarky.ai; change it only to point at another environment.

Marky (actions)

Resource Operation
Workspace Get, Get Many
Connected Account Get Many
Post Create (draft, or scheduled with "Schedule For"), Get, Delete (0.1.1+), Schedule, Get Many
Media Upload From URL

Create calls send an Idempotency-Key built from the execution, node, item and
a hash of the request body, so n8n's "Retry On Fail" never creates a duplicate
post, and a Loop Over Items batch with a new caption or URL never collides with
an earlier batch.

Example: draft post round trip

This workflow is our release smoke test, run headlessly (n8n execute) against
the live API: Manual Trigger → Marky (Post > Create) → Get → Delete.

Node Settings
Marky Resource Post, Operation Create, Workspace: yours, Caption: Hello from n8n. No "Schedule For", so the post is a draft (status NEW) and nothing is published.
Marky Resource Post, Operation Get, Post ID: {{ $('Marky').item.json.id }}
Marky Resource Post, Operation Delete, Post ID: same expression

On 0.1.0, which has no Post Get or Delete, use an HTTP Request node with
Authentication Predefined Credential Type > Marky API and the URL
https://api.mymarky.ai/api/businesses/{{ $('Marky').item.json.business_id }}/posts/{{ $('Marky').item.json.id }}
(method GET, then DELETE). It reuses the same credential.

Marky Trigger

Starts the workflow when a post is published (post.published). Activating the
workflow registers a webhook with the API and deactivating removes it. Each
delivery's signature and timestamp are verified before the workflow runs
(forged or replayed calls get a 401). Optionally limit it
to one workspace.

Workspaces (formerly "businesses")

The API now calls a business a workspace. The node already said
"Workspace" everywhere; it now calls the /api/workspaces routes and sends
workspace_id on uploads. Internal parameter names and resource/operation
values (such as businessId) are unchanged, so saved workflows keep working.

Development

npm install
npm test     # builds, then runs the tests against a local mock API
npm run build

Discussion