NagentArtefacts
Dev & Technology
Enterprise and White Glove
Company
Specific connects to a Nagent workspace with an API key. Once it is connected, agents can call 18 Specific actions, such as "Create Company", "Create Conversation" and "Create or Update Company". Nothing is enabled on connect: each action is allowed one at a time, and an action with side effects runs or waits for a person according to the agent's level.
Every operation an agent can call against Specific, with input parameters and output schema.
SPECIFIC_CREATE_COMPANYTool to create a new company record in the Specific platform. Use when you need to add a new company to the workspace with optional ID, name, and custom attributes.
Input parameters
Company ID - unique identifier for the company. If not provided, Specific will auto-generate one.
Company name - the display name of the company.
Company custom fields - key-value pairs for custom company attributes (can include fields like tier, ARR, etc.).
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
SPECIFIC_CREATE_CONVERSATIONTool to create a new conversation (survey response) in the Specific platform. Use when you need to add a new conversation with content, optional contacts, companies, and custom fields. Content can be a simple string or structured ProseMirror document with headings and paragraphs.
Input parameters
Source connection input.
Company connection or creation input.
Contact connection or creation input.
Conversation content as a simple string or ProseMirror document structure with headings and paragraphs
Source reference URL where the conversation originated
Date and time when the conversation was inserted. Accepts YYYY-MM-DD or RFC 3339 format (e.g., 2007-12-03T10:15:30Z)
Custom field data as key-value pairs
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
SPECIFIC_CREATE_OR_UPDATE_COMPANYTool to upsert a company record in the Specific platform (create if not exists, update if exists). Use when you need to ensure a company exists with specific data, creating or updating as necessary based on the filter criteria.
Input parameters
Company data to create or update - must include ID and optionally name and attributes.
Filter criteria to identify which company to update - typically matches by 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
SPECIFIC_CREATE_OR_UPDATE_USERTool to upsert a user record in the Specific platform (creates if not exists, updates if exists). Use when you need to ensure a contact exists with specific data, merging with existing records based on email or ID.
Input parameters
Contact information to create or update
Filter criteria to identify which contact to modify (by id or email). At least one field must be provided.
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
SPECIFIC_CREATE_USERTool to create a new user (contact) record in the Specific platform. Use when you need to add a new contact with email, name, and optional custom attributes or company association.
Input parameters
Optional custom identifier for the contact. If not provided, Specific will generate one automatically.
The full name of the contact.
The email address of the contact. While optional, it's highly recommended for user identification.
Defines a relationship between a contact and a company.
Custom attributes/fields for the contact as key-value pairs. Use this to store additional metadata.
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
SPECIFIC_DELETE_COMPANYTool to delete a company record from the Specific platform. Use when you need to remove a company by its ID. The operation is permanent and returns the deleted company's details.
Input parameters
The unique identifier of the company to delete.
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
SPECIFIC_DELETE_COMPANY_ATTRIBUTESTool to delete specific custom field attributes from a company record. Use when you need to remove custom attributes by their keys from a company. Returns the updated company details.
Input parameters
Custom field identifiers to delete from the company. Must provide at least one key.
The unique identifier of the company to delete attributes 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
SPECIFIC_DELETE_USERTool to remove a user record from the Specific platform. Use when you need to permanently delete a contact from the workspace.
Input parameters
The email address of the user to delete. Either user_id or email must be provided.
The unique identifier of the user to delete. Either user_id or email must be provided.
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
SPECIFIC_DELETE_USER_ATTRIBUTESTool to delete specific custom field attributes from a user record in the Specific platform. Use when you need to remove custom field values from a contact without deleting the contact itself.
Input parameters
Specifies which custom field attributes to delete from the user record.
Filter to identify which contact to delete attributes from (by id or email).
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
SPECIFIC_GET_MY_WORKSPACETool to get current workspace information for the authenticated user. Use when you need to retrieve the workspace ID and name for the authenticated API key.
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
SPECIFIC_LIST_COMPANIESTool to query company records from the Specific platform via GraphQL. Use when you need to retrieve company information, optionally filtering by ID or name.
Input parameters
Filter for company 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
SPECIFIC_LIST_CONVERSATIONSTool to query conversation records (survey responses) from the Specific platform via GraphQL. Use when you need to retrieve customer feedback, survey responses, or conversation history. Returns up to 20 most recent conversations, optionally filtered by source identifiers.
Input parameters
Filter for conversations by source identifiers.
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
SPECIFIC_LIST_CUSTOM_FIELDSTool to query custom field definitions in the Specific platform. Use when you need to retrieve available custom fields that can be associated with companies, contacts, or conversations. Optionally filter by entity type.
Input parameters
Optional filter to retrieve only custom fields of a specific type. 'user' for contact/user attributes, 'group' for company attributes, 'conversation' for conversation attributes. If not provided, returns all custom fields across all types.
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
SPECIFIC_LIST_SOURCESTool to retrieve all data sources from the Specific platform. Use when you need to fetch available sources in the workspace.
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
SPECIFIC_LIST_SURVEYSTool to retrieve multiple survey records from the Specific platform via GraphQL. Use when you need to fetch all available surveys with their metadata, including names, contexts, tones, and associated conversation 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
SPECIFIC_LIST_USERSTool to query user accounts from the Specific platform via GraphQL. Use when you need to retrieve user information, optionally filtering by ID, email, or custom attributes.
Input parameters
Filter for contact/user 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
SPECIFIC_UPDATE_COMPANYTool to update an existing company record in the Specific platform. Use when modifying company name or custom attributes.
Input parameters
The unique ID of the company to update (e.g., 'specific_cGkw1X80bpo').
New name for the company. If not provided, the name remains unchanged.
Custom field values to update on the company. Merges with existing values.
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
SPECIFIC_UPDATE_USERTool to modify an existing user record in the Specific platform via GraphQL mutation. Use when you need to update contact information such as name, email, company association, or custom attributes.
Input parameters
Data fields to update for the contact
Filter to identify which contact to update (by id or email)
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
Agents can call 18 Specific actions on Nagent, including "Create Company", "Create Conversation" and "Create or Update Company". Create Company: Create a new company record in the Specific platform. Each action is listed on this page with its input parameters and its output.
Specific connects with an API key, under your workspace's own connection. Nothing is enabled on connect: each action is allowed one at a time and can be scoped to the agents that need it.
It also takes 3 optional inputs: id, name and attributes. It returns data, error and successful.