schedchie

Schedchie for n8n: schedule, review and measure social posts from a workflow with the Schedchie API.

Package Information

Released: this month
Downloads: 0 weekly / 0 monthly
Latest Version: 0.1.0
Author: Schedchie

Documentation

n8n-nodes-schedchie

The Schedchie node for n8n. Schedule posts to your connected social accounts, approve or reject held posts, bring in media, keep notes and read analytics from any workflow, through the Schedchie API v1.

Schedchie is a flat-price social media scheduler.

Requirements

  • A Schedchie workspace on Ultra or Ultra+. The API is part of those plans, and keys become available after the workspace's first paid invoice.
  • A self-hosted n8n. Community nodes that n8n has not verified install on self-hosted instances only.

On Pro there is no API key. Connect n8n to the Schedchie MCP server instead, which Pro includes: schedchie.com/ai/n8n.

Install

In n8n, open Settings > Community nodes > Install, enter n8n-nodes-schedchie and confirm. Only an owner or admin can install community nodes.

Without the GUI: run npm install n8n-nodes-schedchie inside ~/.n8n/nodes and restart n8n.

Credentials

  1. In the Schedchie dashboard, open AI assistants and create an API key. Give it the permission groups the workflow needs (posts, media, analytics, team, library), each read and write or read only. The key is shown once.
  2. In n8n, create a Schedchie API credential and paste the key. The node sends it only to https://api.schedchie.com/v1.
  3. Save. n8n checks the key with GET /me.

A key acts only in its own workspace. A read-only key is refused on every write. A workspace holds up to 5 active keys (Ultra+: 10).

Operations

Resource Operation API route
Post Schedule POST /posts
Post Get GET /posts/{id}
Post Get Many GET /posts (all pages with Return All)
Post Update PATCH /posts/{id}
Post Reschedule POST /posts/{id}/reschedule
Post Retry POST /posts/{id}/retry
Post Delete DELETE /posts/{id}
Approval Get Many GET /approvals
Approval Approve POST /posts/{id}/approve
Approval Reject POST /posts/{id}/reject
Media Import From URL POST /media
Media Create Upload Link POST /media/uploads
Media Get Upload Status GET /media/uploads/{slotId}
Media Confirm Upload POST /media/uploads/{slotId}/confirm
Note Create POST /notes
Note Get Many GET /notes
Note Update PATCH /notes/{id}
Note Delete DELETE /notes/{id}
Analytics Get Summary GET /analytics/summary
Analytics Get Overview GET /analytics/overview
Analytics Get Account GET /analytics/accounts/{id}
Analytics Get Account History GET /analytics/accounts/{id}/history
Account Get Many GET /accounts
Member Get Many GET /members
Workspace Get GET /me

The node can also run as a tool of n8n's AI Agent node. On n8n 1.x, community nodes act as tools only when the environment variable N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE is true.

Using it

Times. Date fields are read in the workflow's time zone and sent to the API in UTC. A scheduled time in the past publishes within a minute.

Accounts. The account pickers list the workspace's connected accounts. In an expression, use accountId values from Account > Get Many.

Media. Media > Import From URL takes a public https image or video up to 200 MB (Google Drive share links work) and returns a media object. Put its gcsObjectName in Post > Schedule > Media, for example {{ $json.media.gcsObjectName }}. For a file that is not online yet, Create Upload Link returns a page where a person uploads it within 15 minutes; then Confirm Upload returns the media object. Instagram, TikTok, YouTube and Pinterest refuse a post without media.

Per-account overrides. Platform-Specific Content is a JSON object keyed by accountId, with platform-prefixed fields:

{ "<accountId>": { "youtube_title": "Launch film", "instagram_first_comment": "Link in bio" } }

Retries. Set an Idempotency Key on Schedule that is unique per item, for example {{ $workflow.id }}-{{ $json.id }} (1 to 255 characters of visible ASCII). Every item needs its own id there: if it is empty, every item gets the same key and only the first is posted. A key stays taken for as long as its post exists and counts across every workflow that uses the same API key. A repeat with the same key returns the post already made, even when the text changed, so a retry never posts that item twice. Without a key, a retry posts again.

Approvals. A post a member schedules comes back with processingStatus: pending_approval and waits for the owner. Approval > Get Many lists them; Approve releases one, Reject sends it back with an optional reason the member sees.

Delete. Post > Delete removes the post from Schedchie. A published post leaves the calendar only; nothing is deleted on the social platforms.

Limits

  • Calls are limited per key and once more per workspace, so more keys never mean more calls. The numbers for each plan are on schedchie.com/developers.
  • Analytics > Get Overview and Get Account read live from the platforms. Their answers are cached per workspace, and uncached reads count against an hourly budget. Get Summary and Get Account History read Schedchie's own store and do not count.
  • A 429 answer carries Retry-After. n8n's Retry On Fail runs the node again for every item, including the ones that already went through, so set a per-item Idempotency Key on Schedule before you turn it on. For large batches, a Loop Over Items node with a Wait node paces the calls better than retries.

Errors

Every API error is { "error": { "status", "code", "message", "requestId" } }, with details on a 422 validation_failed. The node shows the API's message as the error title, with the code, the request ID and any failing fields under it. Quote the request ID when you write to support.

Development

npm install
npm run lint
npm run build

Licence

MIT. See LICENSE. The licence covers this package. The Schedchie service is provided under schedchie.com/terms.

Security reports: SECURITY.md.

Discussion