Magnetic is an all-in-one platform designed to help professional services firms manage projects, resources, and finances efficiently.
Magnetic is an all-in-one platform designed to help professional services firms manage projects, resources, and finances efficiently. On Nagent, Magnetic is exposed as a fully-configurable project management integration that any agent can call — 14 actions, and API key authentication. No code is required to wire Magnetic into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Magnetic to automate the kinds of tasks project 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 Magnetic 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 Magnetic, with input parameters and output schema. Drop these into any step of an agent built in Helix.
MAGNETIC_CLIENTS_GET_CURRENT_FOLLOWUPSTool to retrieve upcoming follow-ups assigned to the authenticated user. Use after authentication to view scheduled tasks.
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
MAGNETIC_CLIENTS_SEARCH_CONTACTSTool to search contacts by field or client ID. Use when you need to retrieve client contacts matching given criteria after authentication.
Input parameters
The contact field to search by (e.g., 'email', 'name').
Maximum number of results to return.
The value to match in the specified field.
Number of items to skip for pagination.
Filter results to contacts belonging to this client ID.
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
MAGNETIC_CREATE_GROUPINGTool to create a new opportunity or job (grouping) in Magnetic HQ. Use when you need to organize tasks and track project progress for a new opportunity or job.
Input parameters
Name of the new opportunity or job grouping
Description or additional details about the opportunity/job
The user who will be the owner of this grouping. Must provide user ID.
Contact object to associate with the grouping.
Company object to associate with the grouping.
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
MAGNETIC_CREATE_TASKTool to create a new task in Magnetic HQ. Use when you need to add tasks to the system, optionally assigning them to users or linking to opportunities.
Input parameters
Name of the task to create. This is the primary identifier displayed for the task.
Reference to a user to assign the task to.
End date or due date for the task in ISO 8601 format (e.g., '2024-01-20T17:00:00Z').
Whether time tracked on this task should be billable. Set to true for client-billable work.
Reference to a grouping/opportunity to associate with the task.
Start date for the task in ISO 8601 format (e.g., '2024-01-15T09:00:00Z').
Detailed description of the task. Can contain additional context or instructions.
Amount of time already tracked on this task, in minutes.
Estimated effort for this task, in minutes. Used for time estimation and planning.
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
MAGNETIC_GET_CONTACT_TAGSTool to get all tags associated with a contact. Use after confirming the contactId to list contact tags.
Input parameters
Unique ID of the contact whose tags to retrieve.
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
MAGNETIC_GET_GROUPING_BY_IDTool to retrieve details for a specific grouping (opportunity/job) by its ID. Use when you need detailed information about a specific grouping.
Input parameters
The unique ID of the grouping/opportunity to retrieve (must be positive).
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
MAGNETIC_GET_GROUPING_STATUSESTool to retrieve the list of statuses for signed groupings. Use after authentication when you need available grouping status options for tasks or jobs.
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
MAGNETIC_GET_GROUPING_TAGSTool to retrieve tags associated with any groupings owned by the company. Use after authentication when grouping tags are needed.
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
MAGNETIC_GET_OPPORTUNITY_STATUSESTool to retrieve opportunity statuses. Use when you need current status options for unsigned groupings (opportunities).
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
MAGNETIC_GET_TASKTool to retrieve a task by its ID. Use after confirming you have the taskId.
Input parameters
The unique ID of the task to retrieve (must be positive).
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
MAGNETIC_GET_USER_BY_IDTool to retrieve details for a specific Magnetic user by their ID. Use when you need to fetch a user's profile information.
Input parameters
The unique identifier of the user to retrieve
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
MAGNETIC_GET_USERSTool to retrieve the list of all users in the authenticated user's company. Use after authentication to audit or manage user accounts.
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
MAGNETIC_LIST_COMPANIESTool to retrieve all companies from the Magnetic HQ account. Use after authentication to view all client companies.
Input parameters
Maximum number of companies to return.
Number of items to skip for pagination.
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
MAGNETIC_TASKS_GET_GROUPING_CUSTOM_FIELD_DEFINITIONSTool to retrieve all custom field definitions for groupings. Use after authentication when you need to fetch available grouping custom field definitions for tasks.
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 44 agents privately built on Nagent that already use Magnetic.
Build on Nagent
Connect Magnetic 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 Magnetic, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Magnetic is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Magnetic is connected, you configure its 14 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Magnetic 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 Magnetic event fires, the agent kicks off automatically.
Every Magnetic 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 Magnetic ships with 14 pre-built project management actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Magnetic together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Magnetic-based workflows tailored to your business.