threadliner
WordPress Plugin

Installation and connection

Install the plugin and connect it to your Threadliner workspace.

Internally the plugin still uses "threadline" for its settings keys, block IDs, and REST API namespace (/wp-json/threadline/v1/...) — none of that is visible to you, and keeping it stable is what lets existing installs and any pages you've already built upgrade with no reconfiguration. Everything you actually see now says "Threadliner".

Requirements

  • WordPress 6.4 or later
  • PHP 8.0 or later

Installing

Download the latest plugin zip from the WordPress Plugin releases (or from Settings → API Keys in Threadliner, if a download link is configured there), then install and activate it like any other plugin — either via Plugins → Add New if it's listed in your directory, or Plugins → Add New → Upload Plugin for the zip.

Building it yourself from source works too — see the WordPress plugin's own README in the Threadliner repo for the build steps.

Connecting

  1. In Threadliner, go to Settings → API Keys, create a key, and copy it immediately — it's only shown once, and starts with tl_live_.
  2. In WordPress, go to Settings → Threadliner.
  3. Fill in:
    • API URL — your Threadliner API endpoint (e.g. https://api.threadliner.io, or your own domain if you're self-hosting), no trailing slash needed.
    • API Key — the key from step 1.
  4. Click Save & Test Connection.

If the connection succeeds, the page shows "Connected to Threadliner." in a green notice above the form. If it fails, you'll see "Could not connect to Threadliner: <reason>" — see Troubleshooting for what the reason usually means.

What the API key can do from WordPress

The key is stored in WordPress's own options table and never sent to the browser — form and list pickers in the block editor go through a small WordPress REST API proxy (/wp-json/threadline/v1/forms and /wp-json/threadline/v1/lists) that attaches the key server-side, gated to users who can edit posts. The public-facing embed itself (rendering a form, accepting a submission) doesn't use the key at all — see Embedding a form for why that's unauthenticated by design.

Uninstalling

Deleting the plugin from Plugins removes its two stored settings (API URL and key) along with it — nothing is left behind in wp_options.

Was this page helpful?

Last updated on

Example recipes

Realistic automation rules built from the real trigger, condition, and action types.

Forms block

Embed a Threadliner form on any WordPress page or post.

On this page

RequirementsInstallingConnectingWhat the API key can do from WordPressUninstalling