Integrations

Connected honestly.

QueueTempo uses official OAuth and publishing APIs. Provider capability, QueueTempo implementation, production approval, and your account eligibility are four different checks-and this page keeps them separate.

Status language

An API path is not the same as a live integration.

Only Supported-and explicitly opted-in Beta-capabilities may auto-publish. Everything else stays out of automatic delivery.

Supported

Supported

Implemented, approved, fully verified, and available for eligible accounts.

Beta

Beta

Implemented for controlled use, with explicit enrollment and capability checks.

Manual handoff

Manual handoff

QueueTempo prepares content, but a person must publish it on the destination.

Planned

Planned

On the roadmap. It switches on once it is implemented, approved, and tested.

Awaiting provider API

Awaiting provider API

The platform does not publish an official creation path for this workflow yet. We track it and ship support when it lands.

Supported Production-live

Beta Controlled availability

X

Beta
Eligible accounts
An X account that authorizes QueueTempo with the required user write scope.
Supported content
Text-only posts today. Customer-provided images follow once the configured API access supports and tests them.
Automatic publishing
Yes, only for an eligible, healthy, explicitly enrolled Beta Connection.

Production access, pay-per-use economics, app and user quotas, automation rules, token refresh, ambiguous-timeout reconciliation, and revocation must all pass before broader availability.

Docs checked July 26, 2026Official docs (opens in a new tab)

Threads

Beta
Eligible accounts
A Threads profile that authorizes QueueTempo through the official Threads API with the basic and content-publish scopes.
Supported content
Text posts up to 500 characters today. Media follows once the official media path is implemented and tested.
Automatic publishing
Yes, only for an eligible, healthy, explicitly enrolled Beta Connection.

Threads app credentials, Meta review where required, rate limits, token refresh, and revocation behavior must all pass before broader availability.

Docs checked July 26, 2026Official docs (opens in a new tab)

Instagram

Beta
Eligible accounts
Eligible Instagram professional accounts: Business or Creator. Personal consumer accounts are not supported.
Supported content
One customer-provided image with an AI-assisted or manually written caption.
Automatic publishing
Yes, only after Meta permissions, account eligibility, media validation, and Beta enrollment pass.

Instagram feed posts are not plain text posts. QueueTempo creates and publishes a media container, supplies provider-retrievable media, and waits for the provider result. Meta App Review or Advanced Access may be required for your account.

Docs checked July 26, 2026Official docs (opens in a new tab)

Manual handoff A person finishes the post

YouTube Community

Manual handoff
Eligible accounts
A YouTube channel where the owner is eligible to create Community posts in YouTube.
Supported content
A prepared text draft, copy controls, and a reminder at the scheduled moment, so the post is ready to go the second you open YouTube.
Automatic publishing
Not yet. You publish the final post from YouTube while we work toward an official automatic path.

Because this is a handoff rather than a live API call, it does not consume publishing allowance. QueueTempo stays inside official Google OAuth and never asks for your password.

Docs checked July 26, 2026Official docs (opens in a new tab)

Planned Not available

YouTube video upload

Planned
Eligible accounts
A YouTube channel authorized through Google OAuth, after QueueTempo completes the required verification and compliance work.
Supported content
Customer-provided video upload once it ships. AI-generated video is deliberately not part of this roadmap.
Automatic publishing
Not yet. Video upload is queued behind the work below.

The Data API exposes videos.insert, so the path exists. We are completing the quota, audit, resumable upload, metadata, rights, made-for-kids, synthetic-media disclosure, processing, and failure-recovery work that a production upload deserves before turning it on.

Docs checked July 26, 2026Official docs (opens in a new tab)

Additional destinations

Planned
Eligible accounts
Platform-specific eligible accounts only after each official API and permission model is evaluated.
Supported content
LinkedIn, TikTok, Facebook Pages, Pinterest, Bluesky, Mastodon, and other destinations are on the roadmap rather than in today's release.
Automatic publishing
Not yet. Each one appears as a working Connection the moment its adapter is ready.

We list these so you know what we are building toward, not as a capability claim. Every destination gets its own adapter, policy review, approvals, rate-limit behavior, safety controls, and controlled live test before it appears.

Docs checked July 26, 2026

Awaiting provider API Tracked, ready to ship

YouTube Community auto-publishing

Awaiting provider API
Eligible accounts
Eligible channel owners, as soon as the public Data API exposes a Community-post creation resource we can build against.
Supported content
Automatic YouTube Community post creation.
Automatic publishing
Not yet. In the meantime, the manual handoff above keeps your Community posts on schedule.

Our July 26, 2026 review of the official YouTube Data API found resources such as videos, playlists, comments, and activities, but no Community-post insert yet. We recheck the reference on every provider audit and will turn automatic posting on through the official API as soon as one is published, rather than driving the consumer website on your behalf.

Docs checked July 26, 2026Official docs (opens in a new tab)

What every Connection shows

Capability belongs to the exact account.

A connected account is not treated as a universal green light. QueueTempo stores and rechecks the selected Channel’s supported post types, limits, granted scopes, health, and observation date.

  • Authenticated provider identity and concrete destination
  • Healthy, expiring, reauthorization-required, restricted, or unknown state
  • Supported text, image, video, and accessibility fields
  • Current provider limit observation time
  • Reconnect and disconnect actions with clear consequences

Illustrative capability check

StatusBeta
AccountEligible professional account
ContentSingle image + caption
Auto-publishEnabled after explicit enrollment
ObservedJuly 26, 2026

Set the next beat

Connect only what QueueTempo can explain.

Start free, inspect the capability shown for your exact account, and preview the first Tempo before anything can publish.