Package Information
Documentation
@social-use/n8n-nodes-social-use-connector
@social-use/n8n-nodes-social-use-connector creates and updates content in a single Social-Use channel. It follows the channel API exposed at /dashboard/cms/content-assets/channels/{channelDocumentId}/api.
Install
In n8n, open Settings > Community Nodes, install @social-use/n8n-nodes-social-use-connector, then add the Social-Use node to a workflow.
For local development:
cd n8n-connector/social-use-connector
npm install
npm run build
Credentials
Create a Social-Use API credential with:
| Field | Value |
|---|---|
| Base URL | Your Social-Use application URL, for example https://social-use.example.com |
| Channel ID | The channel documentId in Social-Use |
| API Credential | The channel API token created in the channel content page |
The token is sent only as Authorization: Bearer <token>. Keep it in n8n credentials rather than workflow data.
Operations
| Operation | Endpoint |
|---|---|
| Upload File | POST /api/distribution/channel/{channelId}/upload |
| Create / Update Video | POST / PUT content video endpoints |
| Create / Update Image Text | POST / PUT content image-text endpoints |
| Create / Update Article | POST / PUT content article endpoints |
Upload file
Use an upstream node that produces binary data, select its binary field, and choose Video or Content Asset or Cover Image. The node returns the uploaded file URL. Pass that URL to Video URL, Cover Image URL, or Image URLs in a later Social-Use node.
Create content
- Video requires a title, description, video URL and status.
- Image Text requires a title, description, at least one image URL and status.
- Article requires a title, description, Markdown body and status.
- Scheduled content requires an expected publish time. Content is created in Social-Use and then follows its normal channel publishing workflow.
Development
The package follows the n8n node starter layout. Run npm run lint and npm run build before packaging or publishing.
Continuous Publishing
GitHub Actions validates pull requests that change this package. A version tag created by npm run release triggers npm publication through npm Trusted Publishing (GitHub Actions OIDC), so no NPM_TOKEN is required.
Before the first CI release, configure npmjs.com: package settings -> Trusted Publishers -> GitHub Actions with repository social-use-org/social-use and workflow file .github/workflows/publish.yml. Leave the npm environment blank because this workflow does not use a GitHub Environment.
Use npm run release locally to choose a version and create and push the release tag. The CI workflow publishes that tag with provenance. Do not run npm publish directly. npm run release -- --publish is only a local browser-login fallback; it does not include npm provenance and cannot produce a verified n8n community node. This fallback only requires the connector directory to be clean and never stages or commits other monorepo files; commit its version update after a successful publication. The local command intentionally calls release-it directly because @n8n/node-cli@0.44.3 passes a removed release-it option outside GitHub Actions.