A full-suite platform to manage Clients, Invoices, Projects, Proposals, Estimates, Hours, Payments, Contractors and Staff. The perfect solution to win clients and save time.
A full-suite platform to manage Clients, Invoices, Projects, Proposals, Estimates, Hours, Payments, Contractors and Staff. The perfect solution to win clients and save time. On Nagent, Clientary is exposed as a fully-configurable project management integration that any agent can call — 57 actions, and API key authentication. No code is required to wire Clientary into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Clientary 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 Clientary 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 Clientary, with input parameters and output schema. Drop these into any step of an agent built in Helix.
CLIENTARY_CREATE_CLIENTTool to create a new client record in Clientary. Use when you need to add a new client to the system with company details and contact information.
Input parameters
Postal code or ZIP code
City name
The client's company or organization name (required)
State or province
A unique identifier for the client. Must be unique across all clients
Street address of the client
Country code or country name
Company website URL
Secondary address line (e.g., suite number, apartment number)
Additional details or notes about the client
Custom invoice fields 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
CLIENTARY_CREATE_CONTACTTool to create a new contact within a specified client. Use when you need to add a contact to a client account with name and email as required fields.
Input parameters
The ID of the client to which the contact belongs.
Client user data containing contact information.
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
CLIENTARY_CREATE_EXPENSETool to create a new expense record in Clientary to track expenditures within your account. Use when you need to record expenses, optionally assigning them to specific clients or projects. Requires an amount field.
Input parameters
The expenditure amount. This is a required field.
Assigns the expense to a specific client. Optional field.
Assigns the expense to a particular project. Optional field.
Details about the expense. Optional field.
The date the expense occurred, in YYYY-MM-DD format. Optional field.
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
CLIENTARY_CREATE_INVOICETool to create a new invoice in Clientary. Requires date, due_date, and currency_code. Optionally associate with a client using client_id.
Input parameters
Purchase order reference number
Invoice date in YYYY-MM-DD format (required)
Additional notes or comments for the invoice
Invoice title or subject
Invoice number. Will be auto-incremented if not provided. Must be unique.
Payment due date in YYYY-MM-DD format (required)
Client ID to associate with the invoice (optional)
Three-letter ISO currency code (e.g., USD, EUR, GBP) (required)
Array of invoice items to create
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
CLIENTARY_CREATE_LEADTool to create a new lead record in Clientary. Use when you need to add a new lead to the system with company details and contact information.
Input parameters
Postal code or ZIP code
City name
The lead's company or organization name (required)
State or province
A unique identifier for the lead. Must be unique across all leads
Street address of the lead
Country code or country name
Company website URL
Secondary address line (e.g., suite number, apartment number)
Additional details or notes about the lead
Custom invoice fields 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
CLIENTARY_CREATE_PROJECTTool to create a new project in Clientary with name and rate. Use when you need to set up a new project for tracking time, expenses, or managing client work.
Input parameters
Project data containing name, rate, and optional budget/project type 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
CLIENTARY_CREATE_PROJECT_HOURSTool to create a new time entry for a specific project in Clientary. Use when you need to log hours worked on a project with a title and hours count.
Input parameters
Date the hours were worked in YYYY-MM-DD format. If not provided, current date will be used.
Number of hours logged for the work performed
Title or brief description of the work performed
The unique identifier of the project to log hours for
Detailed description of the work performed
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
CLIENTARY_CREATE_RECURRING_SCHEDULETool to create a new recurring schedule for automatic invoice generation in Clientary. Use when you need to set up recurring invoices for a client at regular intervals (weekly, monthly, quarterly, etc.). Requires client_id, next_date, time_interval, currency_code, and due_period.
Input parameters
Title or name for the recurring schedule
Action to perform when generating recurring invoices.
Custom schedule number identifier
ID of the client for whom the recurring schedule is created (required)
Next invoice generation date in YYYY-MM-DD format (required)
Payment due period in days from invoice generation date. Required field.
Currency code for the recurring schedule (e.g., USD, EUR, GBP). Required field.
Frequency of recurring invoice generation: weekly (1), every_2_weeks (2), semimonthly (3), monthly (5), quarterly (7), or annually (9)
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
CLIENTARY_CREATE_TASK2Tool to create a new task in Clientary using API v2. Use when you need to create a task with a title, optionally associating it with a project, client, or assignee.
Input parameters
The task title (required)
When the task should be completed (date format: YYYY-MM-DD)
ID of the associated client
ID of the project to assign the task to
ID of the staff member to assign the task to
Task details and additional information
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
CLIENTARY_DELETE_CLIENTTool to remove a client and all associated projects, invoices, estimates, and contacts. Use when you need to permanently delete a client from Clientary. WARNING: Deletions are permanent and not reversible.
Input parameters
The unique identifier of the client 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
CLIENTARY_DELETE_CLIENTARY_CONTACTTool to permanently delete a contact and all associated comments. Use when you need to remove a contact that is no longer needed. Warning: This action is irreversible.
Input parameters
The unique identifier of the contact 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
CLIENTARY_DELETE_CLIENTARY_EXPENSETool to permanently remove an expense record from Clientary. Use when you need to delete an expense entry. WARNING: Deletions are permanent and not reversible.
Input parameters
The unique identifier of the expense 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
CLIENTARY_DELETE_CLIENTARY_PROJECTTool to permanently delete a project and all associated resources including tasks, hours, expenses, invoices, and estimates. Use when you need to remove a project from Clientary. WARNING: Deletions are permanent and not reversible.
Input parameters
The unique identifier of the project 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
CLIENTARY_DELETE_HOURTool to permanently delete a time entry (hour) from Clientary. Use when you need to remove a logged hour entry by its unique identifier. Warning: Deletions are permanent and cannot be undone.
Input parameters
The unique identifier of the hour/time entry 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
CLIENTARY_DELETE_LEADTool to permanently delete a lead and all associated Estimates and Contacts. Use when you need to remove a lead that is no longer needed. Warning: This action is irreversible.
Input parameters
The unique identifier of the lead 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
CLIENTARY_DELETE_PAYMENTTool to remove an existing payment from an invoice. Use when you need to permanently delete a payment record. WARNING: Deletions are permanent and not reversible.
Input parameters
The unique identifier of the payment record to delete
The unique identifier of the invoice containing the payment
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
CLIENTARY_DELETE_PAYMENT_PROFILETool to remove a specific payment profile from a client's account. Use when you need to delete a payment profile. Note: Client must have an active payment integration with Stripe to manage payment profiles.
Input parameters
The unique identifier of the payment profile to delete
The unique identifier of the client who owns the payment profile
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
CLIENTARY_DELETE_RECURRING_SCHEDULETool to remove a recurring schedule by its identifier. Use when you need to permanently delete a recurring schedule from Clientary. Once deleted, the recurring schedule will no longer generate periodic invoices.
Input parameters
The unique identifier of the recurring schedule 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
CLIENTARY_GET_CLIENTTool to fetch details for a specific client using its ID. Use when you need to retrieve complete information about a client from Clientary.
Input parameters
The unique identifier of the client 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
CLIENTARY_GET_CONTACTTool to retrieve a single contact by its ID. Use when you need to fetch detailed information about a specific contact from Clientary.
Input parameters
The unique identifier of the contact 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
CLIENTARY_GET_ESTIMATETool to retrieve details for a single estimate by ID. Use when you need to obtain comprehensive estimate information including line items, tax details, and financial data.
Input parameters
The unique identifier of the estimate 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
CLIENTARY_GET_EXPENSETool to retrieve details for a single expense record in Clientary. Use when you need to get specific information about an expense by its unique identifier.
Input parameters
The unique identifier of the expense 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
CLIENTARY_GET_HOURTool to obtain details about a specific time entry in Clientary. Use when you need to retrieve information about a logged hour entry by its unique identifier.
Input parameters
The unique identifier of the hours entry 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
CLIENTARY_GET_INVOICETool to retrieve detailed information for a specific invoice by ID. Use when you need to fetch invoice details including line items, payments, tax information, and current status.
Input parameters
The unique identifier of the invoice 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
CLIENTARY_GET_LEADTool to retrieve a single lead by its ID. Use when you need to fetch detailed information about a specific lead from Clientary.
Input parameters
The unique identifier of the lead 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
CLIENTARY_GET_PROJECTTool to retrieve a single project by its identifier. Use when you need to fetch detailed information about a specific project in Clientary.
Input parameters
The unique identifier of the project 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
CLIENTARY_GET_STAFFTool to retrieve a single staff member by their ID. Use when you need to fetch detailed information about a specific staff member from Clientary.
Input parameters
The unique identifier of the staff member 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
CLIENTARY_GET_TASKTool to retrieve a specific task by its ID. Use when you need to fetch detailed information about a task from Clientary.
Input parameters
The unique identifier of the task 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
CLIENTARY_LIST_CLIENT_CONTACTSTool to retrieve all contacts for a specific client with pagination support. Use when you need to fetch the list of contacts associated with a particular client in Clientary.
Input parameters
Page number for pagination. Default is 1.
The unique identifier for the client whose contacts you want to retrieve.
Number of results per page. Default is 10, maximum is 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
CLIENTARY_LIST_CLIENT_ESTIMATESTool to retrieve all estimates for a specific client with pagination support (30 results per page). Use when you need to fetch estimates associated with a particular client from Clientary.
Input parameters
Page number for pagination. Returns 30 results per page. Defaults to page 1
The unique identifier of the client whose estimates 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
CLIENTARY_LIST_CLIENT_EXPENSESTool to retrieve all expenses for a specific client within an optional date range. Use when you need to fetch expense records associated with a particular client from Clientary.
Input parameters
End date for expense range in YYYY-MM-DD format. Defaults to current fiscal year end if omitted
The unique identifier of the client whose expenses to retrieve
Start date for expense range in YYYY-MM-DD format. Defaults to current fiscal year start if omitted
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
CLIENTARY_LIST_CLIENT_INVOICESTool to retrieve all invoices for a specific client with pagination support (30 results per page). Use when you need to fetch invoices associated with a particular client from Clientary.
Input parameters
Page number for pagination. Returns 30 results per page
The unique identifier of the client whose invoices to retrieve
Filter invoices by update timestamp. Format: 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
CLIENTARY_LIST_CLIENT_PAYMENT_PROFILESTool to retrieve payment profiles for a specific client. Payment profiles store credit card information securely via Stripe integration. Use when you need to fetch payment methods associated with a client account.
Input parameters
The unique identifier of the client whose payment profiles 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
CLIENTARY_LIST_CLIENT_PROJECTSTool to retrieve all projects associated with a specific client with pagination support (10 results per page). Use when you need to fetch projects for a particular client from Clientary.
Input parameters
Page number for pagination. Defaults to page 1 with 10 results per page
The unique identifier of the client whose projects you want 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
CLIENTARY_LIST_CLIENTSTool to retrieve all clients with pagination support (10 results per page). Use when you need to fetch a list of clients from Clientary with optional filtering by modification date or custom sorting.
Input parameters
Page number to retrieve. Default is page 1 with 10 results per page
Sort order for results. Use 'date' to retrieve most recently created clients instead of default alphabetical name-based sorting
Filter clients modified after this date. Format: 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
CLIENTARY_LIST_ESTIMATESTool to retrieve all estimates with pagination support (30 results per page). Use when you need to fetch a list of estimates from Clientary, which serve as proposals or quotes to be sent to clients.
Input parameters
Page number for pagination. Returns 30 results per page. Defaults to page 1
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
CLIENTARY_LIST_EXPENSESTool to retrieve expenses by date range (defaults to current fiscal year). Use when you need to fetch a list of expenses from Clientary with optional filtering by start and end dates.
Input parameters
End date for expense range in YYYY-MM-DD format. If not specified, defaults to the end of the current fiscal year
Start date for expense range in YYYY-MM-DD format. If not specified, defaults to the beginning of the current fiscal year
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
CLIENTARY_LIST_LEADSTool to retrieve all leads with pagination support. Use when you need to fetch a list of leads from Clientary with optional sorting by name or date.
Input parameters
Page number to retrieve. Pagination through more results, you can use the page parameter
Sort order options: 'name' (alphabetical) or 'oldest' (chronological ascending); default sorts by newest first
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
CLIENTARY_LIST_PAYMENTSTool to retrieve all payments with pagination support (30 results per page). Use when you need to fetch a list of payments from Clientary with optional pagination and custom sorting.
Input parameters
Page number to retrieve. Default is page 1 with 30 results per page
Sort field. Accepts 'created_at' to sort by creation date. Defaults to reverse chronological order by 'received_on'
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
CLIENTARY_LIST_PROJECT_ESTIMATESTool to retrieve estimates scoped to a particular project with pagination support (30 results per page). Use when you need to fetch all estimates associated with a specific project.
Input parameters
Page number for pagination. Returns 30 results per page. Defaults to page 1
The unique identifier of the project whose estimates you want 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
CLIENTARY_LIST_PROJECT_EXPENSESTool to retrieve all expenses for a specific project within an optional date range. Use when you need to fetch expense records associated with a particular project from Clientary.
Input parameters
Page number for pagination. Use this to retrieve additional pages if the result set is large
End date for expense range in YYYY-MM-DD format. Defaults to current fiscal year end if omitted
Start date for expense range in YYYY-MM-DD format. Defaults to current fiscal year start if omitted
The unique identifier of the project whose expenses 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
CLIENTARY_LIST_PROJECT_HOURSTool to retrieve all time tracking entries logged against a specific project. Use when you need to fetch hour entries for a particular project, optionally filtering by billed or unbilled status.
Input parameters
Narrows results to either 'billed' or 'unbilled' hours. Note: The user associated with the API token must have appropriate permissions to view billed/unbilled hour information
The unique identifier of the project for which to retrieve hour entries
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
CLIENTARY_LIST_PROJECT_INVOICESTool to retrieve all invoices linked to a specific project with pagination support (30 results per page). Use when you need to fetch invoices associated with a particular project from Clientary.
Input parameters
Page number for pagination. Returns 30 results per page. Defaults to page 1
The unique identifier of the project whose invoices to retrieve
Filter invoices by update timestamp. Format: 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
CLIENTARY_LIST_PROJECTSTool to retrieve all projects with pagination support (10 results per page). Use when you need to fetch a list of projects from Clientary with optional filtering for closed projects.
Input parameters
Page number to retrieve. Default is page 1 with 10 results per page
Use 'all' to include closed projects alongside active/billable ones. By default, only active and billable projects are returned
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
CLIENTARY_LIST_PROJECT_TASKSTool to retrieve all tasks for a specific project. Use when you need to fetch a list of tasks associated with a particular project in Clientary.
Input parameters
The ID of the project to get tasks 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
CLIENTARY_LIST_RECURRING_SCHEDULE_INVOICESTool to retrieve all invoices generated by a specific recurring schedule with pagination support (30 results per page). Use when you need to fetch invoices associated with a particular recurring schedule from Clientary.
Input parameters
The unique identifier of the recurring schedule whose invoices to retrieve
Page number for pagination. Returns 30 results per page
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
CLIENTARY_LIST_STAFFTool to retrieve all staff members for an account. Use when you need to fetch a complete list of staff members from Clientary.
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
CLIENTARY_LIST_TASKSTool to retrieve all tasks with pagination support (50 results per page). Use when you need to fetch a list of tasks from Clientary.
Input parameters
Page number to retrieve. Default is page 1 with 50 results per page
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
CLIENTARY_SEND_INVOICE_MESSAGETool to send an invoice message to recipients via email. Use when you need to email an invoice to clients with customizable subject, message content, and options to send a copy to yourself or attach a PDF.
Input parameters
The unique identifier of the invoice to send
Email body content. If not provided, a default message will be used.
Email subject line. If not provided, a default subject will be used.
Set to 1 to send a copy of the email to the API token user. Set to 0 or omit to not send a copy.
Set to 1 to include a PDF attachment of the invoice with the email. Set to 0 or omit to not attach PDF.
An array of email addresses to receive the invoice. At least one recipient is required.
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
CLIENTARY_UPDATE_CLIENTTool to update an existing client record in Clientary with partial or complete field modifications. Use when you need to modify client details such as name, address, description, or custom fields. All fields except ID are optional.
Input parameters
The unique identifier of the client to update
Postal code. Include to update the postal code.
City location. Include to update the city.
Client company or organization name. Include to update the name.
State or province. Include to update the state.
Client reference number. Must be unique across all clients. Returns HTTP 422 on duplicate.
Primary street address. Include to update the address.
Country code (e.g., 'US'). Include to update the country.
Client website URL. Include to update the website.
Secondary address line (suite, unit, etc.). Include to update the secondary address.
Additional client notes or details. Include to update the description.
Custom invoice field data as key-value pairs. Include to update custom 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
CLIENTARY_UPDATE_CLIENTARY_CONTACTTool to update an existing contact in Clientary with partial or complete field modifications. Use when you need to modify contact details such as name, email, title, or phone numbers. Supports partial updates via the client_user wrapper object.
Input parameters
The unique identifier of the contact to update.
Client user data containing contact fields to update. All fields are optional for partial updates.
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
CLIENTARY_UPDATE_CLIENTARY_LEADTool to update an existing lead record in Clientary with partial or complete field modifications. Use when you need to modify lead details such as name, address, website, description, or custom fields. All fields except ID are optional.
Input parameters
The unique identifier of the lead to update
Postal code. Include to update the postal code.
City location. Include to update the city.
Lead company or organization name. Include to update the name.
State or province. Include to update the state.
Lead reference number. Must be unique across all leads. Returns HTTP 422 on duplicate.
Primary street address. Include to update the address.
Country code (e.g., 'US'). Include to update the country.
Lead website URL. Include to update the website.
Secondary address line (suite, unit, etc.). Include to update the secondary address.
Additional lead notes or details. Include to update the description.
Custom invoice field data as key-value pairs. Include to update custom 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
CLIENTARY_UPDATE_EXPENSETool to update an existing expense record in Clientary with partial or complete field modifications. Use when you need to modify expense details such as amount, description, client assignment, project assignment, or incurred date. All fields except ID are optional.
Input parameters
The unique identifier of the expense to update
The monetary value of the expense. Include to update the amount.
Client assignment identifier. Include to update the associated client.
Project assignment identifier. Include to update the associated project.
Expense description. Include to update the description.
Date when expense was incurred in YYYY-MM-DD format. Include to update the date.
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
CLIENTARY_UPDATE_HOURTool to modify an existing time entry in Clientary with partial or complete field updates. Use when you need to update hours, title, date, description, rate, or billing status of a logged hour entry.
Input parameters
The unique identifier of the hours entry to update
Work date in YYYY/MM/DD format. Optional for partial updates.
Billing rate per hour. Optional for partial updates.
Duration of work logged in hours. Optional for partial updates.
Name or label for the time entry. Optional for partial updates.
Billing status indicator. Optional for partial updates.
Detailed notes about work performed. Optional for partial updates.
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
CLIENTARY_UPDATE_INVOICETool to update an existing invoice in Clientary with partial or complete field modifications. Use when you need to modify invoice details such as number, dates, currency, or line items. For invoice_items_attributes: include item ID to edit existing items, omit ID to create new items, or set destroy=true with ID to delete items.
Input parameters
The unique identifier of the invoice to update
Purchase order reference number
Invoice date in YYYY-MM-DD format
Additional notes or comments for the invoice
Invoice title or subject
Invoice number. Must be unique across all invoices. Returns HTTP 422 on duplicate.
Payment due date in YYYY-MM-DD format
Three-letter ISO currency code (e.g., USD, EUR, GBP)
Array of invoice items to create, update, or delete. Include item ID to edit or delete existing items, omit ID to create new items, or set destroy=true with ID to delete items.
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
CLIENTARY_UPDATE_PROJECTTool to update an existing project in Clientary with partial or complete field modifications. Use when you need to modify project details such as name, rate, description, budget, status, or other project attributes. All fields except ID are optional - only provided fields will be updated.
Input parameters
The unique identifier of the project to update
The project name. Include to update the project name.
Project rate (hourly rate or total cost depending on project type). Include to update the rate.
Budget amount. Include to update the budget.
Unique project number. Include to update the project number. Note: triggers HTTP 422 if duplicate.
Project status code. Include to update the status.
Project end date in YYYY-MM-DD format. Include to update the end date.
Budget type: 0 = total budgeted hours; 1 = total budgeted amount. Include to update the budget type.
Project description. Include to update the description.
Project type: 0 = hourly rate project; 2 = fixed amount project. Include to update the project type.
Currency code (e.g., USD, EUR, GBP). Include to update the currency code.
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
CLIENTARY_UPDATE_TASKTool to update an existing task in Clientary with partial or complete field modifications. Use when you need to modify task details such as title, description, completion status, assignee, or due date. All fields except ID are optional.
Input parameters
The unique identifier of the task to update
Task title/name. Include to update the title.
Task completion status (true/false). Include to update completion status.
Task deadline in date format (e.g., YYYY-MM-DD). Include to update due date.
Related client ID. Include to update client association.
Associated project ID. Include to update project association.
Staff member ID assigned to task. Include to update assignee.
Detailed task information. Include to update the description.
Timestamp when task was marked complete. Include to update completion timestamp.
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 33 agents privately built on Nagent that already use Clientary.
Build on Nagent
Connect Clientary 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 Clientary, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Clientary is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Clientary is connected, you configure its 57 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Clientary 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 Clientary event fires, the agent kicks off automatically.
Every Clientary 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 Clientary ships with 57 pre-built project management actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Clientary together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Clientary-based workflows tailored to your business.