ExpoFP provides free interactive floor plan software for expos and conferences.
ExpoFP provides free interactive floor plan software for expos and conferences. On Nagent, Expofp is exposed as a fully-configurable event management integration that any agent can call — 18 actions, and API key authentication. No code is required to wire Expofp into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Expofp to automate the kinds of tasks event management 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 Expofp 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 Expofp, with input parameters and output schema. Drop these into any step of an agent built in Helix.
EXPOFP_ADD_CATEGORYTool to add a new category to an expo. Use when you have both the expo event ID and a valid API token. Example: "Add category 'Keynotes' to event 2655."
Input parameters
Name of the category to add
API token obtained from ExpoFP profile page.
Unique numeric ID of the expo event.
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
EXPOFP_DELETE_EXHIBITORTool to delete an exhibitor from an expo by their ID. Use when you have the exhibitor ID and a valid API token.
Input parameters
Unique ID of the exhibitor to delete.
API token obtained from ExpoFP profile page.
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
EXPOFP_DELETE_SESSION_SPEAKERSTool to delete session speakers by their IDs. Use when you need to remove one or more session speakers from an expo.
Input parameters
List of session speaker IDs to delete. Must contain at least one ID.
Unique numeric ID of the expo event
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
EXPOFP_DELETE_SESSION_TRACKSTool to delete session tracks by IDs from an expo. Use when you need to remove multiple session tracks. Provide the expo ID, API token, and list of session track IDs to delete.
Input parameters
List of session track IDs to delete. Must contain at least one ID.
Expo ID to delete session tracks from.
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
EXPOFP_GET_BULK_READ_EXHIBITORS_TEMPLATETool to get the template structure for bulk reading exhibitors from an expo. Use when you need to understand the required format for bulk importing exhibitor data.
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
EXPOFP_GET_OFFLINE_ARCHIVELightweight retrieval of offline archive state that never starts a build. Returns the current known ExpoOfflineState for the specified version if available, or null if not. Use when you need to check the status of an existing archive without triggering a new build.
Input parameters
The expo key slug (human-readable identifier for the expo)
Version number (integer) or 'latest'/'l' for the most recent version
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
EXPOFP_GET_OR_CREATE_OFFLINE_ARCHIVERetrieve the offline archive state for a specific expo version. If the archive does not exist and the requested version is 'latest', the server automatically starts the creation process and returns the build state. Use this action when you need to download an expo for offline use or check the status of an ongoing archive build. The optional waitseconds parameter enables server-side polling for synchronous workflows.
Input parameters
Version number (integer) or 'latest'/'l' for the most recent version
The expo key slug identifying the expo event
Enables server-side polling for up to N seconds. If specified, the server will wait up to this many seconds for archive completion before responding. Useful for synchronous workflows.
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
EXPOFP_GET_SESSION_TRACKSRetrieve all session tracks for a specific expo event. Session tracks are categories or themes used to organize sessions within an expo, such as "Technology", "Marketing", "Product", etc. This action returns the complete list of tracks with their IDs, names, external IDs, and color codes. Use this action when you need to categorize or filter sessions by track. Example: "Get all session tracks for expo 32971"
Input parameters
Unique numeric ID of the expo event. Use the List All Expos action to get valid expo IDs.
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
EXPOFP_LIST_ALL_EXPO_EXTRASRetrieves all extras (additional services/items) available for a specific expo event, including general extras and booth-specific extras with exhibitor details. Use this action to get a comprehensive list of purchasable extras for an event. Example: "List all extras for event 2655."
Input parameters
Unique numeric ID of the expo event. Use the List All Expos action to get valid event IDs.
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
EXPOFP_LIST_ALL_EXPOSRetrieve all expos (events/exhibitions) accessible with the authenticated ExpoFP account. This action fetches a complete list of expos with their details including event IDs, names, descriptions, dates, time zones, locations, and status. The expo IDs returned can be used with other ExpofP actions that require an event ID parameter. No input parameters are required - the action uses the authentication token to determine which expos the user has access to. Example usage: - "List all my expos" - "Show me all available events" - "Get all expo IDs"
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
EXPOFP_LIST_CATEGORIESRetrieve all categories for a specific expo event. This action fetches a complete list of categories with their IDs and names for a given expo. The category IDs returned can be used with other ExpofP actions that require a category ID parameter (e.g., updating or removing categories). Use this action when you need to see all categories configured for an expo. Example: "List all categories for event 32971" or "Show me categories for expo 2655".
Input parameters
Unique numeric ID of the expo event. Use the List All Expos action to get valid event IDs.
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
EXPOFP_LIST_EXHIBITORSTool to bulk read exhibitors from an expo with customizable response template. This action retrieves all exhibitors from a specified expo. You can optionally provide a response template to control which fields are returned, or pass null/omit the template to receive all available exhibitor data. Use when you need to fetch exhibitor information from an expo event. The expo ID can be obtained from the List All Expos action.
Input parameters
API token obtained from ExpoFP profile page
Unique numeric ID of the expo event to read exhibitors from
Optional template to customize response fields. Copy response from Bulk Read Exhibitors Template and remove extra fields, or pass null to take all fields.
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
EXPOFP_REMOVE_CATEGORYTool to remove a category from an expo. Use when you have the category ID and a valid API token. Example: "Remove category #123."
Input parameters
Unique ID of the category to remove.
API token obtained from ExpoFP profile page.
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
EXPOFP_SET_EXHIBITOR_LOGOTool to set or remove an exhibitor logo using multipart/form-data. Use when you need to upload a logo image file or provide an image URL for an exhibitor, or remove an existing logo by passing null for the image file.
Input parameters
API token obtained from ExpoFP profile page.
Image URL as an alternative to uploading a file. Provide either img_file or img_url, not both.
Image file to upload as exhibitor logo. Pass null to remove the existing logo.
Unique numeric ID of the exhibitor.
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
EXPOFP_UPDATE_CATEGORYTool to update an existing category. Use when you have the category ID and a valid API token. Example: "Update category #1 name to 'Category Blue'."
Input parameters
Unique ID of the category to update.
New name for the category (maximum 50 characters)
API token obtained from ExpoFP profile page.
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
EXPOFP_UPDATE_EXHIBITORTool to update an existing exhibitor. Use when you have the exhibitor ID and want to modify exhibitor details. Only fields provided in the request are updated; undefined fields remain unchanged.
Input parameters
Unique ID of the exhibitor to update.
Postal/ZIP code for the exhibitor.
City where the exhibitor is located.
Exhibitor name.
Array of tag strings to assign to the exhibitor.
XING profile URL.
State or province where the exhibitor is located.
API token obtained from ExpoFP profile page.
Primary phone number for the exhibitor.
Secondary phone number for the exhibitor.
Primary address line for the exhibitor.
Country where the exhibitor is located.
Twitter profile URL.
Exhibitor website URL.
YouTube channel URL.
Secondary address line for the exhibitor.
Facebook profile or page URL.
Whether the exhibitor is featured.
LinkedIn profile or company page URL.
Array of metadata objects for custom fields.
URL to a promotional or informational video.
Instagram profile URL.
VAT (Value Added Tax) number for the exhibitor.
Internal administrative notes about the exhibitor.
Whether the exhibitor logo is advertised in the header.
Array of category IDs to assign to the exhibitor.
External ID for linking the exhibitor to external systems.
Google Plus profile URL.
Name of the primary contact person.
User-provided sanitized HTML description of the exhibitor.
Public-facing email address for the exhibitor.
Auto-login URL for the exhibitor portal.
Phone number for the primary contact person.
Private email address for the exhibitor.
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
EXPOFP_UPSERT_SESSIONSTool to create or update sessions in bulk for an expo event. Sessions are upserted based on externalId if provided - existing sessions with matching externalId are updated, otherwise new sessions are created. Use this action when you need to add new sessions to an event or update existing sessions. Example: "Add a keynote session to expo 32971" or "Update session details for external ID 'session-001'."
Input parameters
Unique numeric ID of the expo event. Use the List All Expos action to get valid event IDs.
List of sessions to create or update. Each session with an externalId will be updated if it exists, otherwise created.
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
EXPOFP_UPSERT_SESSION_TRACKSTool to create or update session tracks in bulk for an expo. Use when you need to add new tracks or modify existing ones. Provide an id in the track object to update; omit it to create new. Example: "Create a new session track called 'Workshops' with color #FF5733."
Input parameters
API token obtained from ExpoFP profile page
Unique numeric ID of the expo event
Array of session track objects to create or update. Each track must have a name; provide an id to update an existing track
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 68 agents privately built on Nagent that already use Expofp.
Build on Nagent
Connect Expofp 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 Expofp, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Expofp is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Expofp is connected, you configure its 18 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Expofp 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 Expofp event fires, the agent kicks off automatically.
Every Expofp 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 Expofp ships with 18 pre-built event management actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Expofp together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Expofp-based workflows tailored to your business.