Set up Hyperagent to create Flint pages

1. 1.Overview
2. 2.Before you start
3. 3.Part 1: Create the agent
4. 4.Part 2: Connect Slack
5. 5.Part 3: Build the Flint skill
6. 6.Part 4: Use the agent
7. 7.Tips

Skip ahead: Already created an agent? Jump to Connect Slack. Already connected Slack? Jump to Build the Flint skill.

The goal is to give your marketing and setup teams a simple way to create Flint pages from Slack. Someone mentions the agent with a request. The agent previews the planned sections and headline direction. After the requester approves, a background agent builds the page. The requester then reviews the preview and keeps editing in the same Slack thread.

Page creation is not instant. Background agents start after approval and need a little time to finish. The agent bases each new page on one of your hidden vertical or solution template pages, which keeps the structure and format on brand.

Make sure you have:

• •Access to your Hyperagent workspace
• •The right admin permissions. You may need them to create the agent and connect Slack, so confirm who can do this on your side
• •A Flint API key and Site ID from Flint Team Settings, with member role or higher
• •At least one Flint template page, such as a vertical or solution template, set to hidden or unpublished to guide the agent
• •A Slack workspace and a channel for the agent, plus permission to install or approve the Hyperagent Slack app

The names in this guide are examples. You can give the agent and its skill any names that fit your team. They do not need to match this page or each other.

1. 1.In Hyperagent, create a new agent.
2. 2.Set the name to Flint Page Builder, or use your preferred name.
3. 3.Add this description: Creates and edits Flint pages from Slack, based on your templates. Previews for approval, then builds.
4. 4.Open the Model tab and choose a model tier covered by your plan. If you see a subscription or model access error, switch to a lower tier and try again.
5. 5.Open Tools and Integrations. Turn on Code execution, Webpage publishing, and Web search. Connect the Slack integration here.
6. 6.Open Autonomy and select Ask first so the agent pauses before sensitive actions.
7. 7.Open Identity and paste the system prompt below.

You are the Flint Page Builder, an agent that creates and edits Flint landing pages from Slack. You turn a request into a page that matches our templates, preview it for approval, then build it.

## What you do
Take a page request in Slack, plan it using our template pages as the structure guide, show a preview of the structure for approval, build the page after approval, and keep editing in the same thread.

## Source of truth
Use your pinned Flint skill for every Flint action. Base new pages on our hidden template pages so structure and format stay on brand. Do not invent endpoints, field names, or Flint capabilities. If the skill cannot do something, say so.

## Workflow
1. Read the request. If audience, offer, primary CTA, destination URL, or which template to base it on is unclear, ask for all of it in one message before building. If the requester attached a doc such as an account plan or research, read it and fold the relevant details into the page.
2. Preview the page structure you plan to build, meaning the sections and headline direction, and ask the requester to approve before creating anything.
3. After approval, create the page with the Flint skill. Creation runs in the background and is not instant, so tell the requester it is working.
4. Reply with the preview URL and a two line summary of what you built.
5. For edits, continue in the same thread to keep context, apply the change, and re-post the preview.

## Approval rules
Never create a page until the requester approves the previewed structure. Publishing is separately gated: only publish after a clear "approved", "publish", or "ship it". Anything ambiguous means ask. Always show the current preview URL before asking to publish. There is no unpublish; if asked to take a page down, say it must be done in the Flint editor and share the edit URL.

## Slack behavior
Respond to each mention with a single message that contains your full reply. Do not post a separate acknowledgment or "I'm on it" message first. Never send more than one message per turn.

## Style
Keep replies short and skimmable, lead with the preview URL, skip preamble. Do not use em dashes.

1. 1.Open the agent's Invocations tab.
2. 2.Enable Slack.
3. 3.Add the channel or channels where people should use the agent.
4. 4.Select Mentions and thread replies.
5. 5.Test the connection by mentioning the agent in an approved channel, then replying in the same thread.

Slack users in those channels can use the agent without a Flint license. They can request pages, approve plans, review previews, and ask for edits from Slack.

In Hyperagent, you do not upload a script file. The agent builds the skill by completing the task once in a thread and then saving it. The skill name flint-page-builder is only an example. You can use another name, and it does not need to match the agent name.

1. 1.Open a thread with the agent you just created.
2. 2.Paste the prompt below.
3. 3.When the agent asks, provide your Flint API key and Site ID.
4. 4.Wait for the live draft test to succeed and confirm that the agent saved and pinned the skill.

This step connects the agent to Flint. It must succeed before the Slack workflow will work.

Build a reusable skill that creates and publishes pages on our Flint site via the Flint Agent Tasks API, then save it.

API details:
- Base URL: https://app.tryflint.com/api/v1
- Auth: Authorization: Bearer <FLINT_API_KEY>
- Create task: POST /agent/tasks with JSON { "siteId": <FLINT_SITE_ID>, "prompt": "<what to build, including which template page to base it on>", "publish": false }. Returns { "taskId", "status" }.
- Poll: GET /agent/tasks/{taskId} until status is "completed" or "failed". On completed, read output.pagesCreated[] and output.pagesModified[]; each has slug, previewUrl, editUrl, publishedUrl. publishedUrl is set only when the task ran with publish true.
- To publish, resend the POST with "publish": true.
- There is no unpublish endpoint.
- Handle HTTP 429 (rate limited) with backoff; report other HTTP errors and failed tasks clearly.

Do this:
1. Write a Python script (standard library only) that creates a task and polls to completion, taking the prompt text and a publish flag as arguments, and prints the resulting URLs as JSON.
2. Store our Flint API key and Site ID as this skill's credentials named FLINT_API_KEY and FLINT_SITE_ID. Ask for them now, and read them from the environment in the script. Never print them.
3. Test it live: create a real draft page based on one of our template pages and show the preview URL. Do not publish during the test.
4. Once the draft works, save this as a skill named "flint-page-builder" and pin it to this agent.

1. 1.Mention the agent with a request. Include the audience, offer, primary CTA, destination URL, and which hidden template to use. Attach a document, such as an account plan or research, if you have one. The agent will read it and fold relevant details into the page.
2. 2.The agent replies with the planned page structure. Review the sections and headline direction.
3. 3.Approve the plan. The agent builds the page in the background. This takes a little time, so it is not instant.
4. 4.The agent shares the preview URL. Open it and review the page.
5. 5.To change anything, reply in the same thread so the agent keeps the full context. Do not start a new thread.
6. 6.When the page looks right, tell the agent to publish it.

• •Keep your template pages hidden from the public so they can guide the agent without going live
• •Setup and the Slack connection may require admin permissions. Confirm who can do this on your side