Medium, Framer & Newsletters (ConvertKit, MailerLite, Beehiiv)

Connect lightweight, outbound-only publishers — Medium, Framer CMS, and the ConvertKit, MailerLite, and Beehiiv newsletter platforms.

Alongside the deeper WordPress and Webflow integrations, Rankturn supports a set of lightweight, send-only publishers: Medium, Framer CMS, and three newsletter platforms — ConvertKit (Kit), MailerLite, and Beehiiv. Each one takes a finished article and sends it to the destination in one step.

These are one-way connections. Rankturn creates a post, broadcast, or campaign on the platform, but it never reads content back, so there is no two-way sync here (unlike WordPress, Webflow, GitHub, and Notion — see Two-way sync). Your article stays the master copy inside Rankturn.

Connect any of these from Settings → Integrations. After you save credentials, use Test connection to confirm they work before scheduling a publish.

Medium

To publish to Medium, you connect it with a Medium Integration Token. You supply:

FieldRequiredWhat it does
Integration TokenYesAuthorizes Rankturn to publish to your Medium account.
User IDYesYour Medium user ID; used to post to your personal profile.
Publication IDNoIf set, the post is created under that Medium publication instead of your personal profile.
Publish statusNoSets who can see the post: Public, Draft, or Unlisted.

When you publish, Rankturn creates a Medium post with your article's title, formatted content, and (optionally) a canonical URL. Up to 3 tags are sent, each trimmed to 25 characters, and the title is capped at 100 characters to satisfy Medium's limit. The article's top heading is removed from the body because Medium shows the post title separately.

The visibility follows your saved Publish status if you set one. Otherwise, the Draft format posts as a draft, and the Blog post format posts publicly.

Test connection confirms the link is working and, on success, shows the connected handle (for example, "Connected to Medium: @yourname").

Framer

Publishing to Framer adds a new item to a Framer CMS collection. You supply:

FieldRequiredWhat it does
API TokenYesAuthorizes Rankturn to publish to your Framer site.
Collection IDYesThe CMS collection that new items are created in.

Rankturn fills in the collection item's built-in fields: the name (title, capped at 256 characters), the slug (created automatically from the title), the body (the full content), and the excerpt (the article excerpt or meta description, capped at 500 characters).

Optional details are added only when you map them to a collection field in the connection settings. If you provide field names, Rankturn will also write your tags (as a comma-separated list), the author name, and the canonical URL. Structured data (Schema.org) is written to a field named structured-data by default, or to a field you specify.

The Blog post format publishes the item right away, while the Draft format creates it as a draft.

Test connection finds the collection and, on success, shows its name.

ConvertKit

ConvertKit (now Kit) needs a single field:

FieldRequiredWhat it does
API KeyYesAuthorizes Rankturn to publish to your Kit account.

Every format is published as a broadcast. Rankturn sends the article title as the broadcast subject (capped at 255 characters), the content as the email body (styled so it displays reliably in inboxes), and the excerpt or meta description as the description (capped at 500 characters).

The format controls whether the broadcast is public:

  • Email campaign and Blog post create a public broadcast.
  • Draft creates a private broadcast.

On success, Rankturn shows the broadcast's public link when one is available.

Test connection confirms the link is working and, on success, shows the connected account name.

MailerLite

Publishing to MailerLite creates an email campaign. You supply:

FieldRequiredWhat it does
API TokenYesAuthorizes Rankturn to publish to your MailerLite account.

Each publish creates a regular campaign using the article title as the subject (capped at 255 characters for the Email campaign format) and the content as both a styled email body and a plain-text version. The sender uses your MailerLite account defaults.

The format controls whether the campaign is sent:

  • Email campaign creates the campaign and then sends it immediately.
  • Draft creates the campaign but leaves it unsent.

If sending fails or takes too long after the campaign is created, Rankturn leaves the campaign in place rather than trying again — it already exists (and may even have sent), so retrying could send a duplicate email to your subscribers.

Test connection confirms the link is working and, on success, shows the connected account name or email.

Beehiiv

Publishing to Beehiiv creates a newsletter post. You supply:

FieldRequiredWhat it does
API KeyYesAuthorizes Rankturn to publish to your Beehiiv account.
Publication IDYesThe Beehiiv publication that posts are created in.

Rankturn fills the post with the article title (capped at 255 characters), the full content (styled for email), the excerpt or meta description as a subtitle, the thumbnail image, and any tags.

The format controls the post status:

  • Email campaign creates the post ready to send.
  • Draft creates the post as a draft.

Important: Sending posts requires an Enterprise plan on Beehiiv. If your Beehiiv plan does not include it, publishing fails with a clear message asking you to upgrade your Beehiiv plan.

Test connection looks up the publication you entered and, on success, shows its name. If the Publication ID does not exist or your key cannot access it, the test tells you so directly.

Common Notes

Supported formats. Each connector accepts the formats that make sense for the destination:

PlatformSupported formats
MediumBlog post, Draft
FramerBlog post, Draft
ConvertKit (Kit)Email campaign, Blog post, Draft
MailerLiteEmail campaign, Draft
BeehiivEmail campaign, Draft

In every case, the Draft format sends the article without making it fully live: a draft post on Medium and Framer, a private broadcast on Kit, and an unsent campaign or draft post on MailerLite and Beehiiv. This lets you send an article to the platform and give it a final review there before it reaches readers.

One-way only. These publishers send content out; they never pull status or edits back into Rankturn. Keep editing in the Article Editor and re-publish to update the destination.

Test before you schedule. After saving your credentials, always run Test connection in the integration card. It checks your token and (where relevant) your Publication ID or Collection ID against the live platform, so you catch a typo or an expired key before a scheduled publish quietly fails.

Field limits. Short header fields — titles, subjects, excerpts — are automatically trimmed to each platform's limit so an over-long title can't fail the whole publish. The article body is always sent in full.

Your credentials are kept safe. All tokens and keys are stored encrypted. See Credentials & Security for details, and the Integrations overview for the full list of destinations.