Перейти к содержанию

Peak Forms · AI agents

Your assistant drafts.
Вы утверждаете.

Connect an MCP-capable AI assistant to Peak One. It creates form drafts, changes them and asks for your approval before anything goes live.

Start for free

Every agent has its own key and only the permissions you give it.

Peak FormsYour answer
HubSpotThe matching field
HubSpot · CRM adapter
One mapping in detail
01 / Peak FormsEmail
02 / Fictional test valuedemo@example.com
03 / HubSpotemail

A readable field path from the adapter. No transfer, no verified delivery.

View all 5 mappings
Field mapping from the existing adapter. Fictional values, no delivery.
Peak FormsHubSpot property
Emailemail
First namefirstname
Last namelastname
Lifecycle stagelifecyclestage
Lead statushs_lead_status
Code present
Delivery unverified
The connection is set up in the real product. No OAuth happens here.
One concrete target

Understand fields. Check access.

HubSpotReceipt in the target accountNot checked yet

A mapping shows the translation. Only a test in the authorised account shows that data arrived.

02 / How to connect

Connected in five minutes.

This is how a request to an assistant connected to Peak One runs. The tool names are the real names of the interface.

  1. 01 / Agent

    Create an agent

    In Peak One under Settings → AI & agents, create an agent and pick its permissions. The key is shown once.

    One key, your permissions.Settings → AI & agentsPick permissionsThe key is shown once
  2. 02 / Connection

    Connect the assistant

    Enter the MCP address app.peak-atlas.com/api/mcp with the key as bearer token. The page shows ready-made commands.

    app.peak-atlas.com/api/mcpKey as bearer tokenOne workspace per keyReady-made commands on the page
  3. 03 / Approval

    Ask for the first draft

    Describe your form in one sentence. You open the draft through the link the assistant returns.

    Nothing goes live without you.create_form_draftget_form_previewrequest_form_publish

Trust needs clarity

The agent works by your rules.

01 / The existing evidence

Approval for exactly this version

request_form_publish waits for your approval in the Inbox. The approval applies to the reviewed revision; if the draft changes afterwards, nothing is published.

Adapter / ReceiptDELIVERY OPEN
Peak FormsField mappingHubSpot
Adapter in source code
Present
Receipt in the target account
Not checked

02 / Your check

Drafts yes, live no

New agents may read forms and change drafts. You grant the right to publish separately.

Account
Not connected
Permission
Grant in the product

03 / The clear limit

To be honest

Drafting from a brief follows fixed rules over the Peak Forms templates today; no language model inside Peak Forms writes it. Your assistant handles the wording in the conversation. Connection by key only, no OAuth yet.

  • Adapter
  • Webhook
  • Embed
  • Planned

The next step

Give your assistant a workplace.

Create a free account, connect your assistant and let it build the first draft.

Start for free
Your field translationNOT CONNECTED
Peak Forms→HubSpot
Email → email

Check in the target account what actually arrived.

Инструменты

What an agent can do with Peak Forms.

The same tools are available through MCP and through the REST interface.

Read

Draft

Not available yet

Frequently asked questions

Which assistants work?

Any client that speaks MCP over HTTP with its own Authorization header, for example Claude Code or Codex. Peak One shows ready-made commands for both.

Can an agent publish without me?

No. Publishing has an external effect and always waits for your approval in the Inbox.

What happens on retries?

With the same idempotency key Peak One returns the first result again instead of creating twice.

Is there a limit?

120 calls per agent and minute. Above that the interface answers with 429.