Mopinion captures user feedback across websites and apps, providing insights, analytics, and reporting to optimize user experiences and drive conversions
Mopinion captures user feedback across websites and apps, providing insights, analytics, and reporting to optimize user experiences and drive conversions On Nagent, Mopinion is exposed as a fully-configurable analytics integration that any agent can call — 11 actions, and API key authentication. No code is required to wire Mopinion into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Mopinion to automate the kinds of tasks analytics 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 Mopinion 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 Mopinion, with input parameters and output schema. Drop these into any step of an agent built in Helix.
MOPINION_GET_ACCOUNTTool to retrieve the current authenticated account information. Use to verify authentication and get account details.
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
MOPINION_GET_DATASET_BY_IDRetrieve complete metadata for a specific Mopinion dataset (feedback form) by its ID. Returns dataset properties including name, associated report ID, data source type, and description. Use this action when you need detailed information about a specific dataset/form. To discover available dataset IDs, use the List Datasets action first. This is a read-only operation that does not modify any data.
Input parameters
The unique identifier of the dataset (form) to retrieve. Can be provided as an integer or string. Use the List Datasets action to discover available dataset 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
MOPINION_GET_DATASET_FEEDBACKRetrieve feedback items (survey responses) for a specific dataset/form with optional pagination and filtering. Use this action to fetch multiple feedback entries from a dataset. Each feedback item contains the survey responses including custom fields, scores, metadata, and timestamps. Supports pagination for large result sets and filtering by field values. For retrieving a single feedback item by ID, use GET_DATASET_FEEDBACK_BY_ID instead.
Input parameters
Page number to return
Maximum number of results per page (max 100)
Field-level filters as a map of field_key to filter value. Serialized as filter\[{field_key}\]=value in the query string
Identifier of the dataset (form) to retrieve feedback for
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
MOPINION_GET_DATASET_FEEDBACK_BY_IDRetrieves a single feedback item by its unique identifier from a specific dataset. Use this tool when you need detailed information about a specific feedback item. First obtain the dataset_id using List Datasets, then get feedback_id values using Get Dataset Feedback. **Important Notes:** - Returns a warning in metadata if the feedback item doesn't exist (with null field values) - Returns 404 error if the dataset_id itself is invalid or inaccessible - The response includes feedback fields, tags, scores, timestamps, and associated metadata
Input parameters
Numeric identifier of the dataset (form) containing the feedback. Obtain this from List Datasets action.
Numeric identifier of the specific feedback item to retrieve. Obtain this from Get Dataset Feedback action.
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
MOPINION_GET_DATASET_FIELDSTool to retrieve field definitions for a dataset. Use when you need the schema of a dataset's fields.
Input parameters
Unique identifier of the dataset whose field definitions should be retrieved. Use the LIST_DATASETS action to discover available dataset 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
MOPINION_GET_DEPLOYMENT_BY_IDRetrieves detailed configuration for a specific feedback form deployment by its ID. Returns deployment rules, trigger conditions, scheduling settings, target URLs, and active status. Use this to understand when, where, and how a feedback form is displayed to users.
Input parameters
The deployment key (identifier) to retrieve. This is the 'key' field from the deployments list.
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
MOPINION_GET_DEPLOYMENTSTool to list all deployments for the authenticated Mopinion account. Use after setting up authentication.
Input parameters
Optional Accept header override, e.g., application/json
Optional Mopinion API version header value, e.g., v1 or v2
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
MOPINION_GET_REPORT_BY_IDRetrieves detailed information about a specific Mopinion report by its ID. Returns comprehensive report details including name, description, language, creation date, and all associated datasets with their metadata. Use this when you need full information about a specific report. To find available report IDs, use the Get Reports action first. Example use case: Get complete details of report 22511 to understand its datasets and configuration.
Input parameters
Unique numeric identifier of the Mopinion report to retrieve. Obtain this from the Get Reports action.
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
MOPINION_GET_REPORT_FEEDBACKTool to retrieve feedback items for a report. Use when you need paginated and filtered feedback entries for analysis.
Input parameters
Page number to retrieve (1-based).
Maximum number of feedback items to return per page (1-100).
Server-side filters serialized as filter\[field\]=value in query parameters.
The unique identifier of the report to retrieve feedback for.
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
MOPINION_GET_REPORT_FIELDSTool to retrieve field definitions for a specific report. Use when you need the schema of a report's feedback fields before constructing or analyzing forms.
Input parameters
The unique ID of the report to retrieve fields for.
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
MOPINION_GET_ROOTCheck Mopinion API availability and get version information. Pings the API health check endpoint (/ping) and returns status code, 'pong' response, and current API version. Use this to verify the API is reachable and operational.
Input parameters
Optional path to append to the base URL. Defaults to '/ping' for the standard health check endpoint. Use this to test other endpoints if needed.
Optional override for the Mopinion API base URL. If not provided, the action uses the connection's base_url when it points to a Mopinion domain; otherwise it falls back to 'https://api.mopinion.com'.
Whether to include the Authorization header in the request. Defaults to False because the root ping does not require authentication.
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 Mopinion.
Build on Nagent
Connect Mopinion 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 Mopinion, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Mopinion is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Mopinion is connected, you configure its 11 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Mopinion 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 Mopinion event fires, the agent kicks off automatically.
Every Mopinion 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 Mopinion ships with 11 pre-built analytics actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Mopinion together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Mopinion-based workflows tailored to your business.