Do I need to know how to code?

No coding required. You describe what you want in plain English — for example, "scrape Primal for trending posts about Bitcoin and save them to a Google Sheet" — and Twin builds the agent. You can adjust the goal at any time without editing any code.

Can my Primal agent run on a schedule?

Scheduling is supported. You can set a Primal agent to run daily, weekly, or at any custom interval. Each run browses Primal fresh, so your reports always reflect current trending posts and profiles rather than a stale snapshot.

How does Twin access Primal?

Twin operates the Primal browser interface directly. Because Primal's workflows may not expose all data through a structured API, Twin uses browser automation to reach pages, search results, and profile data that are visible in the UI.

What can I do with the data Twin collects from Primal?

Agents can write results to Google Sheets, push data to GitHub, or pass it to other tools in a multi-step workflow. The BitVault Nostr Lead Hunter agent, for example, combines Primal data with Nostr Band results and stores output for further processing.

Which Primal agents in the Twin community can I clone?

The Primal agents section above lists the most-run community builds, with run and clone counts on each card so you can pick a battle-tested starting point. An adapted clone usually beats a blank canvas, especially for Primal workflows with established patterns.

Integration

Automate Primal with AI agents

Twin agents browse Primal to collect trending posts, profile data, and topic signals — then route results into spreadsheets, GitHub, or wherever you work.

Automate Primal Browse 2 Primal agents

Integration guide

How Twin uses Primal inside repeatable agent workflows

Twin treats Primal as part of a larger workflow, not as an isolated connector. An agent can read the relevant records, combine them with context from other tools, decide what needs to happen next, and report the finished work back to the team.

The page below shows the practical automation patterns for Primal: what the agent can monitor, which actions it can take, and how the workflow stays observable when it runs on a schedule.

Common starting points include nostr social listening, creator prospecting on nostr, content signal gathering. Each example is designed to become a reusable agent, so teams can start from a narrow job and expand it as the process matures.

Twin is most useful when primal workflows may require browser-visible pages rather than structured API data. Twin drives the browser directly, so data that isn't exposed through an API endpoint is still reachable.

What you can do with Primal

Real Primal workflows the Twin community runs every day, ready for you to clone.

Scrape trending posts by topic

Agent searches Primal for posts in a target topic area and extracts post content, dates, and links into structured output.
Explore
Collect top creator profiles

Pulls creator profile data from Primal search results, capturing names, statuses, and profile links for a given niche.
Explore
Build Web3 social monitoring reports

Combines scraped posts and profiles into a structured report, then writes rows to Google Sheets or a GitHub file.
Explore
Run recurring Nostr network scans

Pairs Primal browser data with Nostr Band API results to track activity across the decentralized network on a schedule.
Explore

How it works

Three steps from idea to a running Primal agent.

1

Twin logs in to Primal

Twin opens a private browser session on your behalf and authenticates to Primal just like you would.
2

Describe the workflow

Tell Twin what you want done in Primal in plain English — including any flow that has no public API.
3

Twin runs in your browser session

The agent operates Primal step by step, handling forms, modals, and dashboards exactly as a human would.

Why Twin for Primal

What makes Twin a better fit than a generic automation tool.

Browser access when APIs fall short

Primal workflows may require browser-visible pages rather than structured API data. Twin drives the browser directly, so data that isn't exposed through an API endpoint is still reachable.

No manual copying between tools

Copying Primal data by hand into spreadsheets or trackers creates stale records. Twin writes directly to Google Sheets or GitHub after each run, keeping downstream data current without human intervention.

Repeatable, not one-off

A single scrape is easy. Running the same workflow weekly against a changing topic feed is where manual work breaks down. Twin agents run on a schedule and handle the repetition.

Primal agents from the community

Be the first to build a Primal agent.

The Twin community hasn't published a Primal agent yet — describe what you'd like to automate and we'll build it for you in minutes.

Build the first Primal agent

Common Primal use cases

Patterns that show up across the Twin community — start from one and adapt it.

Nostr social listening

Monitor Primal for trending posts and creator activity on any topic.

See use case

Creator prospecting on Nostr

Identify top Primal profiles in a niche for outreach or partnership.

See use case

Content signal gathering

Pull trending Primal posts to inform content strategy and briefs.

See use case

Primal data to spreadsheet

Export scraped posts and profiles into Google Sheets automatically.

See use case

Build with more than Primal

These related integration pages give crawlers and readers another path through the automation catalog. They connect Primal to nearby apps, categories, and paired workflows that teams often evaluate together.

See all integrations