I IngestAI docs
/

WordPress & WooCommerce

Plugin distribution

Pitchbar ships with two admin-editable knobs that control the "Need the plugin?" copy + download CTA rendered at the bottom of every workspace's /app/integrations page (in the WordPress / WooCommerce card). Use them when you're hosting the plugin somewhere other than the default CodeCanyon receipt — a WordPress.org listing, an S3 bucket, a corporate file share.

Where to set them

Super-admin only. Sign in as a platform admin and visit /settings/system#integrations (the "Integrations" tab inside System settings — the WordPress plugin block lives there alongside the workspace-facing integration toggles). Two fields:

  • Download URL — absolute https:// link to the .zip (or to your WP.org listing). Becomes a "Download plugin" link rendered next to the existing "WordPress install & connect" doc link. Validated as a URL, max 500 chars.
  • Help text — short blurb that replaces the default "Need the plugin? Download it from your CodeCanyon receipt…" copy. Max 2000 chars. Leave blank to fall back to the default.

What customers see

On /app/integrations the WordPress card footer reads: 

{help_text} Download plugin · WordPress install & connect

When both fields are blank the page falls back to the original "Need the plugin? Download it from your CodeCanyon receipt, or read the setup guide:" copy. The "Download plugin" anchor is omitted entirely so we don't render a dead link.

Why customize this

  • You're hosting the plugin on WordPress.org and want customers landing through their wp-admin's plugin search instead of CodeCanyon.
  • You're running a Pitchbar fork under your own brand ("Replibar", "Whispbar", "Dirty Good") and the CodeCanyon reference is out of place.
  • You run a paid SaaS license + a separate plugin distribution channel (Gumroad, Lemon Squeezy, your own storefront) and want the workspace integrations page to deep-link there.

Security notes

  • The "Download URL" is rendered as a plain <a href> with target="_blank" + rel="noopener noreferrer". Validation rejects non-URL strings, but the link still goes wherever you point it — only super-admins can change this field.
  • Help text is rendered as plain text (no HTML escaping bypass). Putting markdown or HTML in there won't render — it shows as literal characters.

Related