Article angle extraction

Turn article links you share with the bot into key points and hooks for Import and Repurpose.

Plan access

Requires the Starter plan or higher.

Where to find it

1. DM Slash Social a public article or page URL.
2. On the intake card, choose Import & Repurpose or a format-focused repurpose action.
3. When angle extraction is enabled, Slash Social fetches readable text and presents key points and hooks in the repurpose preview.

You can also reach this extraction from Import and Repurpose flows started inside Create when the source URL is already attached.

What you get

Extracted angles include:

• Short hooks suitable for posts or threads
• Key points you can mix into carousel or multi-part formats
• Prefill for the repurpose composer so you edit instead of starting blank

Extraction runs only when enough article text is available and your organization still has AI generation quota.

The preview identifies the validated source, whether Slash Social generated new angles or reused a previous result, and the model confidence. Saved results remain limited to the same organization, brand, user, and source.

If the page is paywalled, inaccessible, or too thin, paste the article text instead. If a plan limit, billing issue, timeout, or extraction error stops the process, the validated source text remains available and you can continue the repurpose flow manually.

Slash Social checks angle picker submissions against the current organization, brand, and user. An outdated picker closes with recovery guidance before it changes the selection or starts draft generation.

Verify

After choosing repurpose, the preview or composer shows extracted hooks and key points from the same URL. Saving a draft keeps the source URL linked to the item.

Related docs

• DM the bot when the idea is still raw
• Plan comparison
• Usage limits
• Feature modes

Usage note

Use this page as a lookup when a workflow, plan comparison, or troubleshooting guide mentions Article angle extraction. Confirm the active brand, connected account, and workspace plan before promising the capability to a customer. If the article marks the feature as not launch-ready or hidden, treat it as operator context and do not describe it as available in customer onboarding.

When the page lists plan availability, compare it with Plan comparison and Usage limits rather than old sales names. When availability is not stated, avoid inventing a plan gate; verify access in Billing & Plan from Settings. Capture the workspace, brand, feature name, and blocker text before you contact support.