How it works
Spellcast connects to the social accounts you already have and schedules content on your behalf. Here's the full flow, from connecting an account to tracking how a post performs.
- 1
Connect your accounts
Sign in with your business's own platform login and authorise Spellcast to schedule and publish on your behalf. Nothing is shared until you connect an account.
Each platform connection goes through that platform's own official OAuth login — Spellcast never asks for or stores your social media password. You choose exactly which account to connect, and can disconnect it at any time from account settings.
- 2
Write once, tailor per platform
Draft a post and adjust the caption, media, and platform-specific settings for each destination before it goes out.
Start from a single draft, then adjust the caption length, hashtags, and platform-specific options (like TikTok's disclosure toggle or Instagram's alt text) per destination before scheduling — the base content only has to be written once.
- 3
Schedule and track
Queue posts for the right time on every connected account, then follow engagement and growth from a single dashboard.
Set a publish time per account and Spellcast queues the post through each platform's own posting API at that time. Once it's live, the analytics dashboard pulls back engagement data so you can see what worked.
What happens to your data
Spellcast only accesses the platform data needed to schedule, publish, and report on the posts you create. Full details are in our Privacy Policy. You can disconnect any account at any time from your account settings, and request deletion of your data via our Data Deletion page.
Questions
Does Spellcast see my password?
No. Every platform connection uses that platform's own OAuth login — Spellcast receives an access token, never your password.
Can I disconnect an account?
Yes, at any time from account settings. Disconnecting immediately stops Spellcast from being able to post to or read that account.
What happens if a post fails to publish?
Spellcast flags failed posts in the dashboard so you can see why (an expired token, a platform-side rejection, etc.) and retry or edit before rescheduling.