Connections
Buttons act through your own connected accounts — Gmail today, more apps on the way. LocalMagik stores connection references only, never your passwords or raw tokens.
A draft is only useful once it goes somewhere. Connections are how Magik Buttons act in the real world — sending your newsletter, and over time publishing and posting — always through accounts you own.
The security posture is deliberately boring: you authorize each app on the provider's own consent screen, LocalMagik keeps only a reference to that authorization (never your password, never raw tokens), and any send that uses a connection sits behind the human approval gate like everything else. Revoking access is always in your hands.
Under the hood, connections sit behind a swappable connector layer — which is why the roadmap can grow (email platforms, publishing targets, social accounts) without your buttons changing shape. The button you learned this month works the same when it gains new places to deliver next year.
Questions, answered
Which apps can LocalMagik connect to today?
Gmail is the first connection — it powers personalized newsletter sending from your own address. More connections (email platforms, publishing, social) are on the roadmap, and the connector layer was built so adding them doesn't change your buttons.
Is it safe to connect my account?
Connections are authorized through the provider's own OAuth screen — you grant access directly, and you can revoke it there any time. LocalMagik stores a reference to the connection, never your password and never raw tokens.
What happens when new connectors arrive?
Your buttons just get new places to send. Because buttons are declarative, pointing a send step at a new connector is a definition change, not new software — your workflow and approval gates stay identical.
See it in a button
The fastest way to understand LocalMagik is to run one Magik Button end to end.