Hyperise is a personalization toolkit that enables sales and marketing teams to add dynamic, personalized elements to images, videos, and websites, enhancing engagement across various channels.
Hyperise is a personalization toolkit that enables sales and marketing teams to add dynamic, personalized elements to images, videos, and websites, enhancing engagement across various channels. On Nagent, Hyperise is exposed as a fully-configurable marketing automation integration that any agent can call — 5 actions, and API key authentication. No code is required to wire Hyperise into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Hyperise to automate the kinds of tasks marketing automation teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Hyperise into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Hyperise, with input parameters and output schema. Drop these into any step of an agent built in Helix.
HYPERISE_CREATE_CLIENT_ACCOUNTCreates a new Hyperise business/client account for personalized image campaigns. Use this to provision prospect records that can be linked to Hyperise image templates. The website field is required in the extras parameter. Returns the created account's ID, which can be used with other Hyperise actions like personalized short links.
Input parameters
Name of the client account (business name) to be created.
Contact email address for the client account.
Additional fields for client creation. REQUIRED: 'website' (e.g., 'https://example.com'). Optional fields include: first_name, last_name, business_phone, business_address, category, job_title, logo (URL), profile_image (URL), custom_text_1 through custom_text_4, custom_image_1 through custom_image_3, lat, long.
Parent business/agency ID to associate with the client account (used for organization purposes in the response).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HYPERISE_LIST_IMAGE_TEMPLATESRetrieves all active personalized image templates for the authenticated user. Use this tool when you need to: - Get a list of available Hyperise image templates - Find template IDs for use with other Hyperise actions - Check template dimensions, preview URLs, or metadata Returns an empty list if no templates exist.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HYPERISE_PERSONALIZED_SHORT_LINKSGenerate a personalized short link with Open Graph metadata for rich link previews. This tool creates a shareable URL that: - Redirects to your destination page - Shows personalized image previews when shared on social media - Passes personalization data to your landing page Prerequisites: 1. At least one image template must exist in your Hyperise account 2. A custom link domain must be configured in Settings > Custom Domain Use HYPERISE_LIST_IMAGE_TEMPLATES first to get the image_hash parameter.
Input parameters
The destination URL that the short link will redirect to. Must be a valid, fully-qualified URL (e.g., https://example.com/landing).
The page description for Open Graph metadata. This appears as the link preview description when shared on social media or messaging apps.
The page title for Open Graph metadata. This appears as the link preview title when shared on social media or messaging apps.
The unique hash identifier for your Hyperise image template. Obtain this from the HYPERISE_LIST_IMAGE_TEMPLATES action or from your Hyperise dashboard under Image Templates.
Personalization data as key-value pairs. Common keys include: first_name, last_name, email, company_name, job_title, website, profile_image_url. Example: {'first_name': 'John', 'company_name': 'Acme'}
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HYPERISE_PROSPECT_BUSINESS_DATATool to perform CRUD operations on Hyperise business prospect records. Use when managing business data via the Hyperise API.
Input parameters
Record ID; required for retrieve, update, delete
Latitude coordinate
Logo URL or base64 image source
Longitude coordinate
Contact email; must be valid; required for create/update
Alternate contact phone number
Job title of contact
Gender of contact
Website URL; required for create/update
Category of the business
Job title of contact
Last name of contact
CRUD operation to perform: list, retrieve, create, update, or delete
First name of contact
Name of the business
Custom text field 1
Custom text field 2
Custom text field 3
Custom text field 4
Profile image URL or base64 source
Phone number of the business
Custom image 1 URL or base64
Custom image 2 URL or base64
Custom image 3 URL or base64
Address of the business
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
HYPERISE_USER_AUTHENTICATIONTool to authenticate an API token and retrieve user details. Use after obtaining a valid API token from Hyperise settings.
Input parameters
Hyperise API token generated in account settings. Optional: if omitted, uses the token from the authenticated connection.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 89 agents privately built on Nagent that already use Hyperise.
Build on Nagent
Connect Hyperise to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Hyperise, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Hyperise is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Hyperise is connected, you configure its 5 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Hyperise steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Hyperise event fires, the agent kicks off automatically.
Every Hyperise action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Hyperise ships with 5 pre-built marketing automation actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Hyperise together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Hyperise-based workflows tailored to your business.