ForceManager is a mobile-first CRM designed to enhance sales team productivity by providing real-time insights and streamlined management of customer interactions.
ForceManager is a mobile-first CRM designed to enhance sales team productivity by providing real-time insights and streamlined management of customer interactions. On Nagent, Forcemanager is exposed as a fully-configurable crm integration that any agent can call — 20 actions, and API key authentication. No code is required to wire Forcemanager into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Forcemanager to automate the kinds of tasks crm 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 Forcemanager 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 Forcemanager, with input parameters and output schema. Drop these into any step of an agent built in Helix.
FORCEMANAGER_DELETE_ACTIVITYDelete an existing activity by ID. Tries multiple base hosts and path variants to maximize compatibility across environments and gateways.
Input parameters
Activity identifier (positive integer)
ForceManager API version to use (sent via X-FM-API-Version header)
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
FORCEMANAGER_DELETE_COMPANYTool to delete a company by its ForceManager ID. Use when you need to remove an existing company from the system.
Input parameters
Company identifier (positive integer)
ForceManager API version to use (sent via X-FM-API-Version header)
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
FORCEMANAGER_DELETE_CONTACTPermanently deletes a contact from ForceManager by its unique ID. This action removes the specified contact and all associated data. The operation is irreversible. The action automatically tries multiple API endpoint combinations to ensure compatibility across different ForceManager deployments and configurations. Returns the HTTP status code and any response message from the API. A successful deletion typically returns a 200 status code.
Input parameters
The unique ID of the contact to delete. Must be a positive integer that represents an existing contact in ForceManager.
Optional API version number to use for this request. If specified, it will be sent in the X-FM-API-Version header. Leave empty to use the default API 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
FORCEMANAGER_DELETE_SALES_ORDERDelete a sales order by ID using ForceManager REST API. Tries multiple base hosts and path variants to maximize compatibility across environments. Accepts successful HTTP status codes (< 300) even when the response is non-JSON, capturing response text.
Input parameters
The unique identifier of the sales order to delete
ForceManager API version to use. If specified, sends X-FM-API-Version header with the request
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
FORCEMANAGER_DELETE_SALES_ORDER_LINEDelete a sales order line by ID. Attempts deletion across multiple ForceManager API hosts and path variations to ensure compatibility. Returns detailed information about the deletion result, including any messages or status codes from the API. Use this when you need to remove a specific sales order line item from the system.
Input parameters
The unique identifier of the sales order line to delete. Must be a positive integer representing an existing sales order line ID.
ForceManager API version to use for this request. If specified, sends X-FM-API-Version header. Leave unset to use the default API 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
FORCEMANAGER_DELETE_VALUEDelete a master-data value (Z_ table) by ID using ForceManager REST API. Tries multiple base hosts and path variants to maximize compatibility across environments. Accepts successful HTTP status codes (< 300) even when the response is HTML instead of JSON, capturing the response text as a message. Also retries sending authentication headers as query parameters on HTTP 401 as some gateways expect them in query string.
Input parameters
Identifier of the master-data value to delete
Optional ForceManager API version to use (sent via X-FM-API-Version)
Name of the Z_ master data table containing the value (e.g., Z_Test)
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
FORCEMANAGER_DELETE_VIEWDelete a saved view (custom filter) by its ID. Views in ForceManager are saved filter configurations that users create to quickly access filtered lists of entities (accounts, activities, opportunities, etc.). This action permanently removes a view that the authenticated user has permission to delete. **Use Cases:** - Remove outdated or unused custom filters - Clean up views after organizational changes - Programmatically manage view lifecycle **Requirements:** - Valid view ID that exists in the system - Appropriate permissions to delete the view - The view must be owned by or shared with the authenticated user **Note:** This action tries multiple ForceManager API endpoints to maximize compatibility across different deployment environments and API versions.
Input parameters
ID of the saved view (custom filter) to delete. A view in ForceManager represents a saved filter configuration for entities like accounts, activities, or opportunities. The ID must match an existing view that the authenticated user has permission to delete.
ForceManager API version to use (sent via X-FM-API-Version header). Optional - defaults to the API's default version if not specified.
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
FORCEMANAGER_GET_ACTIVITYRetrieves a single activity by its ID from ForceManager CRM. Use this tool when you need to: - Fetch details of a specific activity by its ID - Check if an activity exists - Retrieve activity data including comments, dates, linked contacts/accounts, and location info The action attempts multiple ForceManager API endpoints to ensure compatibility across different API versions and deployment configurations. Returns found=False if the activity does not exist or cannot be retrieved. Authentication is handled automatically via headers from the connected account.
Input parameters
The unique identifier of the activity to retrieve. Accepts numeric IDs (e.g., '1', '12345') or alphanumeric external IDs (e.g., 'abc123'). This is passed as a path parameter in the API request.
ForceManager API version to use. If not specified, the API will use the default version. Sent via X-FM-API-Version header.
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
FORCEMANAGER_GET_COMPANYRetrieve a single company by its ID from ForceManager. Returns company details when found, or an empty entity with found=False when the company doesn't exist or the API returns non-JSON content. The action automatically tries multiple ForceManager API endpoints for maximum compatibility. Use this to fetch company information including name, address, contact details, and custom fields. Check the 'found' field to determine if the company exists.
Input parameters
The unique identifier of the company to retrieve. Can be a numeric ID (e.g., '5000') or alphanumeric external ID
Optional API version number to use (sent via X-FM-API-Version header). Leave unset to use the default 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
FORCEMANAGER_GET_INTERNAL_IDTool to retrieve ForceManager internal IDs mapping for a given externalId and entity type. This action calls the documented endpoint /api/internalid with required authentication headers and optional pagination/version headers. It tries multiple base hosts to avoid HTML app shell responses and gracefully handles non-JSON responses and error codes by returning empty results instead of failing the execution.
Input parameters
Zero-based page index to request (sent as X-FM-Page header)
Entity type to search for internal ID mapping. Use one of the predefined entity types: Company, User, Offer, Product, Contact, Activity, or Schedule.
External identifier of the entity in your system. Some API examples use 'externalid' (lowercase); this action sends both for compatibility.
ForceManager API version to use (sent as X-FM-API-Version header)
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
FORCEMANAGER_GET_PRODUCTRetrieve a single product by its ID from ForceManager/Sage Sales Management. This action tries multiple known ForceManager API endpoints in sequence until one succeeds. If a product is not found or the API returns non-JSON content, it returns found=False with an empty entity dict. This graceful handling allows agents to check for product existence without encountering errors. Use this when you need to fetch product details such as name, price, cost, category, or custom fields by product ID.
Input parameters
Identifier of the product to retrieve (positive integer)
ForceManager API version to use (sent via X-FM-API-Version header)
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
FORCEMANAGER_GET_SALES_ORDER_LINERetrieves a single sales order line by ID from ForceManager. A sales order line represents a product item within a sales order, including quantity, pricing, and discount information. Use this when you need to fetch details about a specific line item in a sales order, such as product information, quantities, prices, or applied discounts.
Input parameters
The unique identifier of the sales order line to retrieve (numeric string or integer)
ForceManager API version to use (sent via X-FM-API-Version header). Optional, defaults to API's default version if not specified.
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
FORCEMANAGER_GET_USERRetrieves a single ForceManager user by their ID, returning comprehensive user information including name, email, phone, active status, permission level, manager, branches, and more. Returns the complete user object if found, or an empty entity with found=False if the user doesn't exist, was deleted, or the API returns an error. Automatically tries multiple ForceManager API endpoints and versions to ensure compatibility. Use this when you need to: fetch user profile details, verify user existence, check user permissions/status, or retrieve user contact information.
Input parameters
User ID to retrieve. Can be a numeric string (e.g., '123') or alphanumeric identifier
ForceManager API version to use (sent via X-FM-API-Version header). Defaults to version 4 if not specified
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
FORCEMANAGER_GET_VIEWTool to get a single view by ID. Returns a list with zero or one view object.
Input parameters
Unique identifier of the view to retrieve (numeric or alphanumeric string)
ForceManager API version to use (sent via X-FM-API-Version header)
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
FORCEMANAGER_LIST_VIEWSTool to list saved view filters. Use when you need to retrieve saved views for a specific entity (e.g., list views for entity 'account').
Input parameters
Advanced search query (SQL-like) applied to views
Important-field LIKE filter to match view name
Zero-based page index to request (sent as X-FM-Page header)
Important-field LIKE filter to match target entity name
ForceManager API version to use (sent as X-FM-API-Version header)
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
FORCEMANAGER_UPDATE_ACTIVITYTool to update an existing activity by ID. Use when you need to change fields such as comment, date/time, linked entities, or geocode.
Input parameters
Activity identifier (positive integer)
External id from third-party system
Comments for the activity
Calculated if geocode exists (read-only, discourage sending)
Linked account id
Linked contact id
Whether this is a check-in (boolean, sent as 'True'/'False' per FM API)
ForceManager API version to use (sent as X-FM-API-Version header)
If is_checkin=True: Standard Checkin \\ | Opportunity \\ | FastCheckin
Sales rep ID (may be read-only)
Linked opportunity id
Activity type id
Geocode accuracy
Latitude for check-ins
Permission level (1–5)
Longitude for check-ins
UTC date and time of the activity in ISO 8601 format (YYYY-MM-DDThh:mm:ss)
Checkout date-time for check-out activities (ISO 8601 UTC)
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
FORCEMANAGER_UPDATE_COMPANYUpdate Company
Input parameters
Company identifier (positive integer). Must be an existing company ID from your ForceManager account.
Fax number
Company name
Email address
Primary phone number
External system identifier for integration with other systems
Comments or notes about the company
Secondary phone number
Website URL
Postal/ZIP code
Primary address line
Secondary address line
Branch identifier (string ID from ForceManager)
City name
Country identifier (numeric string or country code)
Market segment identifier (string ID from ForceManager)
VAT/tax identification number for the company
ForceManager API version to use (sends X-FM-API-Version header)
Dictionary of extra custom fields (z_*) to merge into payload
Mobile phone number
Primary sales representative user ID (string ID from ForceManager)
Province or state name
Secondary sales representative user ID
Third sales representative user ID
Fourth sales representative user ID
Fifth sales representative user ID
Whether the company is visible to all users in the organization
Account type identifier (string ID from ForceManager)
Default product rate/price list identifier
Access permission level (1=lowest to 5=highest)
Account status identifier (string ID from ForceManager)
Geolocation accuracy radius in meters (e.g., '50', '100')
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
FORCEMANAGER_UPDATE_PRODUCTUpdates an existing product by ID in ForceManager. Use this tool to modify product details such as name, price, cost, description, availability status, category, family, discount limits, and custom fields. The product must already exist - this action does not create new products. At least one field besides 'id' must be provided to update.
Input parameters
Product identifier (positive integer)
Manufacturing or acquisition cost (in currency units)
Product name or model identifier
Selling price (in currency units, e.g., 99.99)
External ID from third-party system
Product family ID for grouping related products
ForceManager API version to use (sends X-FM-API-Version header)
Category ID to classify the product
Product description or additional comment/notes
Dictionary of extra custom fields (z_*) to merge into payload
Maximum allowed discount percentage (e.g., 15.5 for 15.5%)
Set to True to mark product as unavailable/out of stock, False to mark as available
Permission level (1–5)
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
FORCEMANAGER_UPDATE_SALES_ORDERUpdate Sales Order
Input parameters
Sales order identifier (positive integer)
Order year
Sales order topic
Order amount, must be non-negative
External identifier
Order number
Address line for the order
Rate ID for the order
Archive flag; True to archive
Sales order comments
Branch ID
Sales order status ID
Linked account ID
Linked contact ID
First discount value
Second discount value
Third discount value
Fourth discount value
ForceManager API version to use (sends X-FM-API-Version header)
Actual closed date (YYYY-MM-DD)
Currency ID
Dictionary of extra custom fields (z_*) to merge into payload
Sales representative ID
Linked opportunity ID
Expected closing date (YYYY-MM-DD)
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
FORCEMANAGER_UPDATE_SALES_ORDER_LINETool to update sales order line by ID. Use when modifying details of an existing sales order line. Retries with query auth on 401 for proxy-pro host.
Input parameters
Identifier of the sales order line to update
Unit price before discounts, must be non-negative
Quantity for this line, must be non-negative
First discount, must be non-negative
Second discount, must be non-negative
Third discount, must be non-negative
Fourth discount, must be non-negative
Identifier of the product for this line
ForceManager API version to use (sends X-FM-API-Version header)
Final price after discounts, must be non-negative
Additional custom fields (e.g., z_customField) to merge into the payload
Identifier of the sales order owning the line
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 56 agents privately built on Nagent that already use Forcemanager.
Build on Nagent
Connect Forcemanager 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 Forcemanager, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Forcemanager is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Forcemanager is connected, you configure its 20 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Forcemanager 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 Forcemanager event fires, the agent kicks off automatically.
Every Forcemanager 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 Forcemanager ships with 20 pre-built crm actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Forcemanager together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Forcemanager-based workflows tailored to your business.