Build your own agent: describe it in your own words#
Open Agents and click Build your own agent. Step 1, "Describe what your agent should do": write what the agent should look at and what the result should contain (20 to 4,000 characters), optionally what the report should show and when it should run, and choose what it may read. Click Generate agent. Alignify turns your text into a draft agent and shows it next to what you wrote ("We turned your description into this agent"): name, instructions, output fields, what it reads and its price. Click Use this draft to open it in the builder, adjust anything, and save. Build manually skips the description and starts from an empty builder. Only owners and admins can generate, save and run custom agents; members can open their reports and can suggest an agent instead.
How to describe an agent well: good examples#
Say three things: which records it runs on, what it should check, and what the result should contain. Good examples:
- "For the deals in the Contract sent stage, rank how likely each one is to close this month and name the main blocker for each."
- "For a contact, tell me whether they fit our ideal customer profile and what I should ask on the first call."
- "Check how healthy a customer account is from its open tickets, recent emails and the deals on it. Give a health score, a tier (Healthy, Watch, At risk) and the top risks."
Name the outputs you want (a score, a category with its options, a list, findings). Do not ask it to send, delete, merge or change data in bulk, and never paste passwords or API keys.
What a custom agent runs on: one record or a segment#
A custom agent runs on one HubSpot deal, contact, company or ticket that you pick at run time, or on a segment. A segment is up to 25 records of one type matched by 1 to 5 filters combined with AND, analysed together in one report: a comparison, ranking or pattern, not one report per record. Build the filters with pickers: pipeline and stage (deals, tickets), lifecycle stage (contacts, companies), lead status (contacts), owner (when the HubSpot connection allows reading owners), "no activity for N days", "created in the last N days" and an amount range for deals. Raw HubSpot filters are under Advanced. Segment runs need no record pick and never propose HubSpot updates.
Choosing what a custom agent may read (data access)#
In "What may it access?" tick what the agent may read besides its main record: contacts, companies, deals, tickets, line items, products, quotes, owner names and custom objects, plus engagement history (emails, calls, meetings, notes, tasks) at Recent or Extended depth (twice as much, costs more). "Also read how these records relate to each other" adds a second level of related records (for example deal → company → tickets). The agent reads only what you ticked. Items your HubSpot connection cannot read are greyed out with "Reconnect HubSpot to allow …".
Output fields of a custom agent#
Each custom agent declares 1 to 12 output fields. A field is a score, a category (2 to 8 options), text, a list or findings. The report shows each field, and fields can be written back to HubSpot. A workspace can have up to 25 custom agents.
What a custom agent costs#
The price is calculated from the saved agent and shown before you save ("This agent costs N credits per run (Expert)"). A baseline agent (one record, up to 2 related object types, recent engagements, one level, up to 6 fields) costs the standard Light 1, Expert 2, Deep 4 credits. The price rises with: each object type beyond the first three, Extended history, the second level of related records, each field beyond 6, HubSpot field updates, and especially the number of records in a segment. Examples: company plus contacts, deals and tickets with 8 fields costs 2 / 3 / 6; a segment of 10 deals with companies and contacts costs 4 / 7 / 13. One run never costs more than 24 credits; a bigger agent is trimmed to fit and the report says so. Generating a draft is free.
Why was my agent description refused?#
Agents analyse HubSpot data and report; the builder refuses descriptions that ask for something else and says why:
- Sending or exporting CRM data anywhere (agents show results in Alignify).
- Deleting, merging or bulk-changing records (act on the report yourself).
- Emailing or messaging customers (agents can draft text for you to send).
- Using anything outside HubSpot: the web, Slack, spreadsheets or other CRMs.
- Passwords, API keys or tokens in the description.
- Text that tries to change how the agent must behave.
- A description that is not an analysis, or too unclear to tell what to do.
Rewrite the description as "look at X and tell me Y" and generate again.
"Basic draft" notice in the builder#
If the builder says it made a basic draft, the AI step was not available, so the draft uses your description as the goal with a standard set of fields. Review and edit the instructions and fields before saving; the agent works the same once saved.
Generate agent limit#
Generating drafts is free and limited to 10 per workspace per hour. If you hit the limit, wait a little or edit the last draft in the builder by hand.
Custom agent HubSpot updates#
On a record run, a custom agent proposes a note on that record with its summary and every field. In the builder's Update HubSpot section you can also send a field to an Alignify property (alignify_…), to an existing HubSpot property, or to a task for the record owner. Protected fields (amount, stage, close date, owner and similar) cannot be targeted. Updates wait in WriteBacks; the agent's Automatic HubSpot updates switch becomes available after one of its proposals is approved and applied, and standard HubSpot fields still wait for review.
Why were automatic updates of my custom agent switched off?#
Changing a custom agent's instructions, output fields or HubSpot updates switches its automatic HubSpot updates off, and workspace admins get a notification. An approval only vouches for the version it was given on. To switch them on again, run the edited agent, approve and apply one of its HubSpot updates in WriteBacks, then turn on Automatic HubSpot updates. Renaming the agent or editing its description does not switch them off.
Editing or deleting a custom agent#
Owners and admins open the agent from Agents → Custom and edit it. Saving creates a new version; new runs, including scheduled ones, use it, and finished reports keep the version they ran with. The price is recalculated on save. Changing what the agent runs on pauses schedules that no longer fit. To delete it, click Delete custom agent twice to confirm; its schedules are deleted too, and completed runs keep their reports.
Can a custom agent run on a schedule?#
Yes. After one successful run of the agent (and, for an agent that runs on one record, one approved and applied HubSpot update from it), it appears on Schedules with Add schedule pre-filled from its "When should it run" suggestion. See "Scheduling a custom agent" in the Schedules article.
Suggest an agent for us to build#
If no agent fits, click Suggest an agent in Agents. Fill in what it should do, what you should get out of it, which HubSpot data it needs and how often it should run, then Send suggestion; tick "You may contact me about this request" if we may reply by email. Your requests and their status are listed under Your requests (only you see them). You can send up to 5 suggestions a day. Any member can suggest an agent.