# Forcemanager AI integration on Definable > ForceManager is a mobile-first CRM designed to enhance sales team productivity by providing real-time insights and streamlined management of customer interactions. ## What this connects ForceManager is a mobile-first CRM designed to enhance sales team productivity by providing real-time insights and streamlined management of customer interactions. Vendor: https://www.forcemanager.com ## Tools available **20** tools available. First 12: - `FORCEMANAGER_DELETE_ACTIVITY` — Delete Activity — Delete an existing activity by ID. Tries multiple base hosts and path variants to maximize compatibility across environments and gateways. - `FORCEMANAGER_DELETE_COMPANY` — Delete Company — Tool to delete a company by its ForceManager ID. Use when you need to remove an existing company from the system. - `FORCEMANAGER_DELETE_CONTACT` — Delete Contact — Permanently 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. - `FORCEMANAGER_DELETE_SALES_ORDER` — Delete Sales Order — Delete 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. - `FORCEMANAGER_DELETE_SALES_ORDER_LINE` — Delete Sales Order Line — Delete 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. - `FORCEMANAGER_DELETE_VALUE` — Delete Master Data Value — Delete 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. - `FORCEMANAGER_DELETE_VIEW` — Delete View — Delete 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. - `FORCEMANAGER_GET_ACTIVITY` — Get Activity — Retrieves 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. - `FORCEMANAGER_GET_COMPANY` — Get Company — Retrieve 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. - `FORCEMANAGER_GET_INTERNAL_ID` — Get Internal ID — Tool 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. - `FORCEMANAGER_GET_PRODUCT` — Get Product — Retrieve 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. - `FORCEMANAGER_GET_SALES_ORDER_LINE` — Get Sales Order Line — Retrieves 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. ## Auth Auth schemes: `API_KEY`. ## How agents use Forcemanager Inside a Definable workflow, Forcemanager is one of the tools the **Distributor specialist** can call. Example coordination patterns: - **Researcher → Forcemanager** — the Researcher (GPT-5.5) pulls context from Forcemanager (records, threads, documents), synthesises findings, and briefs the rest of the team. - **Writer → Distributor → Forcemanager** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Forcemanager (create record, post message, draft email). - **Designer / Engineer → Distributor → Forcemanager** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Forcemanager (attach file, open PR comment, post status). The Verifier checks every Forcemanager call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention. ## Categories - crm — https://definable.ai/apps/category/crm/ - sales & crm — https://definable.ai/apps/category/sales-&-crm/ ## Related - HTML page: https://definable.ai/apps/forcemanager/ - Same category (crm): https://definable.ai/apps/category/crm/ - All integrations: https://definable.ai/apps/ - Workflow (multi-agent loop): https://definable.ai/workflow/ - Apps llms.txt index: https://definable.ai/llms-apps.txt