Skip to main content

n8n Integration

Upload-Post provides seamless integration with n8n for automated video publishing workflows. This guide walks you through connecting your Upload-Post account with n8n.

tip

Upload-Post also has a verified n8n community node, n8n-nodes-upload-post. Search for "Upload-Post" in the n8n nodes panel, or install it from Settings → Community Nodes. The steps below use the HTTP Request node, which works the same way against the API.

Getting Started with Upload-Post​

  1. Create an account or log in to your existing Upload-Post account
  2. Navigate to the "API Keys" section
  3. Generate an API key for your n8n integration

API Configuration​

For n8n integration, you'll need to configure an HTTP Request node with the following parameters:

Endpoint: https://api.upload-post.com/api/upload
Method: POST
Headers: Authorization: Apikey your-api-key-here
info

URL Support for Media Files: You can now pass URLs for both photo and video uploads instead of binary files. Simply provide the direct URL to your media file in the video or photos[] parameter.

n8n Workflow Configuration​

Configure your n8n HTTP Request node with these parameters:

FieldValueRequired
titleYour video titleOptional
userYour usernameRequired
platform[]tiktokRequired
videoBinary fileRequired

Node Configuration Steps:​

  1. Add an HTTP Request Node to your workflow
  2. Configure the node settings:
    • Method: POST
    • URL: https://api.upload-post.com/api/upload
    • Headers: Authorization: Apikey [YOUR_API_KEY]
    • Body: Set to multipart/form-data and add the required fields

Complete JSON Node Configuration​

Below is the complete JSON configuration for the HTTP Request node in n8n:

{
"parameters": {
"method": "POST",
"url": "https://api.upload-post.com/api/upload",
"authentication": "none",
"sendHeaders": true,
"headerParameters": {
"parameters": [
{
"name": "Authorization",
"value": "Apikey YOUR_API_KEY_HERE"
}
]
},
"sendBody": true,
"bodyParameters": {
"parameters": [
{
"name": "user",
"value": "YOUR_USERNAME"
},
{
"name": "title",
"value": "= $input.item.title ? $input.item.title : 'My awesome video'"
},
{
"name": "platform[]",
"value": "tiktok"
}
]
},
"options": {
"redirect": {
"redirect": true
},
"proxy": {
"proxy": false
},
"timeout": 10000
},
"sendQuery": false,
"contentType": "multipart-form-data",
"queryParameterArrays": "indices",
"bodyContentType": "multipart-form-data",
"bodyParameterArrays": "indices",
"formBinaryData": {
"video": "={{$binary.data}}"
}
},
"name": "Upload Video to TikTok",
"type": "n8n-nodes-base.httpRequest",
"typeVersion": 4,
"position": [
860,
300
],
"id": "98a25a44-b7fb-41e3-8b8b-3d33c5c6ea65"
}

For Instagram Uploads​

To upload to Instagram instead, change the platform value:

"bodyParameters": {
"parameters": [
{
"name": "user",
"value": "YOUR_USERNAME"
},
{
"name": "title",
"value": "= $input.item.title ? $input.item.title : 'My awesome video'"
},
{
"name": "platform[]",
"value": "instagram"
}
]
}

Uploading to Multiple Platforms​

To upload to both TikTok and Instagram simultaneously:

"bodyParameters": {
"parameters": [
{
"name": "user",
"value": "YOUR_USERNAME"
},
{
"name": "title",
"value": "= $input.item.title ? $input.item.title : 'My awesome video'"
},
{
"name": "platform[]",
"value": "tiktok"
},
{
"name": "platform[]",
"value": "instagram"
}
]
}

Security Best Practices​

  • Never hardcode your API key directly in the workflow
  • Create a Credentials entry in n8n for your Upload-Post API key
  • Reference the credential in your HTTP Request node
  • For workflows that will be shared, export without credentials
  • Consider using environment variables or n8n's credential store

Example Workflow: AI-powered Social Media Publisher​

This workflow automates video publishing with AI-generated descriptions:

  1. Google Drive Trigger: Monitors a folder for new videos
  2. OpenAI Transcription: Extracts audio and converts to text
  3. OpenAI Description Generator: Creates engaging descriptions
  4. Upload-Post HTTP Request: Uploads to multiple platforms
  5. Error Handling: Sends notifications on completion/errors

This workflow is available as a template: View template on n8n.io

Trigger a workflow from Upload-Post events​

Not generally available yet

The Upload Post Trigger node and the webhook subscriptions behind it are not generally available yet: the node is not in the published community package, and until subscriptions are available activating it fails with 503 (reason: webhook_subscriptions_disabled).

The Upload Post Trigger node starts a workflow when Upload-Post sends an event: an upload finished (published or failed), a social account was connected, disconnected or needs reconnecting, a comment or DM arrived, a Telegram update, a Google Business review or listing change, a YouTube video published or updated.

  1. Add Upload Post Trigger, pick your Upload-Post credential and the Events (and, optionally, one Profile).
  2. Activate the workflow. The node creates a webhook subscription for its own URL (source: "n8n") and deletes it when you deactivate the workflow. It never changes your account webhook URL, so it can live next to other integrations.
  3. Use Listen for test event and send a sample from the subscription (POST /api/uploadposts/webhooks/subscriptions/{id}/test) to map the fields. The test URL and the production URL of n8n are two different subscriptions.

Things to know:

  • Upload-Post only delivers to a public HTTPS address. A local n8n (localhost, a private IP or plain http) cannot be activated (400 invalid_url): set n8n's WEBHOOK_URL to its public https address.
  • Verify Signature is on by default: the node checks X-Upload-Post-Signature with your account webhook secret and rejects anything else.
  • Every item carries the event body plus uploadPostDelivery (event, deliveryId, attempt, subscriptionId). Deliveries are at-least-once: deduplicate by deliveryId.
  • comment_received, dm_received and telegram_update need the feature turned on for the account (see Webhooks).
  • If the workflow is deleted without deactivating it, its URL starts answering 404 and Upload-Post disables the subscription by itself after a few attempts.

Need Assistance?​

For additional help with your n8n integration, contact our support team.