Telagus

Retrieves MySQL database schema information including tables, columns, relationships, and indexes. This tool covers these tables: mms, mms_trackings. MANDATORY: Use this tool FIRST before writing any SQL queries to understand the database structure. Essential for generating accurate queries with proper table/column names, JOIN conditions, and performance optimization. NEVER assume you know the database structure - ALWAYS use this tool first. Do NOT guess or assume column names exist without verifying them through this schema tool first.

analyze_mysql_database_mms_schema

Retrieves MySQL database schema information including tables, columns, relationships, and indexes. This tool covers these tables: phone_numbers, users. MANDATORY: Use this tool FIRST before writing any SQL queries to understand the database structure. Essential for generating accurate queries with proper table/column names, JOIN conditions, and performance optimization. NEVER assume you know the database structure - ALWAYS use this tool first. Do NOT guess or assume column names exist without verifying them through this schema tool first.

analyze_mysql_database_phone_number_schema

Retrieves MySQL database schema information including tables, columns, relationships, and indexes. This tool covers these tables: projects, project_notes, project_tasks, project_members, project_categories, project_comments, statuses. MANDATORY: Use this tool FIRST before writing any SQL queries to understand the database structure. Essential for generating accurate queries with proper table/column names, JOIN conditions, and performance optimization. NEVER assume you know the database structure - ALWAYS use this tool first. Do NOT guess or assume column names exist without verifying them through this schema tool first. when some one ask you to summarize a project by title, please add all possible titles in or condition and use like '%%' query. when someone ask the project status, the status field in project stores id to the statuses table and use this get status name and show it.

analyze_mysql_database_project_schema

Retrieves MySQL database schema information including tables, columns, relationships, and indexes. This tool covers these tables: project_tasks, project_members, project_comments. MANDATORY: Use this tool FIRST before writing any SQL queries to understand the database structure. Essential for generating accurate queries with proper table/column names, JOIN conditions, and performance optimization. NEVER assume you know the database structure - ALWAYS use this tool first. Do NOT guess or assume column names exist without verifying them through this schema tool first.

analyze_mysql_database_project_task_schema

Retrieves MySQL database schema information including tables, columns, relationships, and indexes. This tool covers these tables: estimates, estimate_items, leads, lead_contacts. MANDATORY: Use this tool FIRST before writing any SQL queries to understand the database structure. Essential for generating accurate queries with proper table/column names, JOIN conditions, and performance optimization. NEVER assume you know the database structure - ALWAYS use this tool first. Do NOT guess or assume column names exist without verifying them through this schema tool first.

analyze_mysql_database_quote_schema

Retrieves MySQL database schema information including tables, columns, relationships, and indexes. This tool covers these tables: sms, sms_trackings. MANDATORY: Use this tool FIRST before writing any SQL queries to understand the database structure. Essential for generating accurate queries with proper table/column names, JOIN conditions, and performance optimization. NEVER assume you know the database structure - ALWAYS use this tool first. Do NOT guess or assume column names exist without verifying them through this schema tool first.

analyze_mysql_database_sms_schema

Retrieves MySQL database schema information including tables, columns, relationships, and indexes. This tool covers these tables: users, user_infos. MANDATORY: Use this tool FIRST before writing any SQL queries to understand the database structure. Essential for generating accurate queries with proper table/column names, JOIN conditions, and performance optimization. NEVER assume you know the database structure - ALWAYS use this tool first. Do NOT guess or assume column names exist without verifying them through this schema tool first.

analyze_mysql_database_user_schema

Retrieves MySQL database schema information including tables, columns, relationships, and indexes. This tool covers these tables: website_pages, users. MANDATORY: Use this tool FIRST before writing any SQL queries to understand the database structure. Essential for generating accurate queries with proper table/column names, JOIN conditions, and performance optimization. NEVER assume you know the database structure - ALWAYS use this tool first. Do NOT guess or assume column names exist without verifying them through this schema tool first.

analyze_mysql_database_website_page_schema

This tool helps with Attendance management. It allows you to create, update and manage attendance records. 1. GENERAL_ATTENDANCE: general enquiry for attendance details. 2. VIEW_ATTENDANCE: view details of a specific attendance record by ID. 3. CREATE_ATTENDANCE: create a new attendance record (clock in). 4. UPDATE_ATTENDANCE: update an existing attendance record (clock out). 5. USER_ATTENDANCE: check attendance records for a specific user (identified by username or email). 6. SEARCH_ATTENDANCE: search for attendance records by user email or name. IMPORTANT: Return proper response related to attendance related questions. Over this connection note is not accepted.

attendance_tool

Create a new custom field on a Telagus module, so records in that module can carry a value the standard fields do not have. Provide title, field_type and related_to. One of: text, textarea, selectbox, radiobuttons, checkboxes, single_checkbox, date. Everyday names are accepted too and are converted to the stored name — "dropdown" becomes selectbox, "radio" becomes radiobuttons, "checkbox" becomes checkboxes, "toggle" becomes single_checkbox. Options must be supplied for selectbox, radiobuttons, checkboxes. This tool defines the field itself. It does not set a value on any record: filling a custom field in for a particular lead or user is done in Telagus. When the user message contains 'create custom field from below details' followed by parameter details in the format 'parameter_name:parameter_value', extract these parameters and use them directly without asking for additional information. Fields for health information, biometric data, national or government identifiers, payment card or bank details, authentication credentials, or a protected characteristic such as a date of birth or gender cannot be created or renamed over this connection, and neither can a field that accepts a file upload. They are managed in Telagus at Dashboard > Settings > Custom Fields. Over this connection client_id is not accepted: every call acts on your own account and is attributed to you.

create_custom_field

Create a new lead task in the database. Required parameters: lead_email, title, activity, set_remainder. Optional parameters: description, due_date_time, remainder_time, tags, assigned_to, lead_task_status_id, job_id. The lead_id is automatically determined from the lead with the specified email. If multiple leads match the email, the most recently updated one is used.

create_lead_task

Edit an existing lead task in the database. Required parameters: lead_email, task_title. Optional parameters: activity, description, due_date_time, set_remainder, remainder_time, tags, assigned_to, lead_task_status_id, job_id. The lead_id is automatically determined from the lead with the specified email. If multiple leads match the email, the most recently updated one is used.

edit_lead_task

Use this tool only to run SELECT query against the tables related to campaign in MySQL database. This the tool to use only to gather information from the MySQL database. The signed-in user is id 2253; use it for questions about "me" or "my". Every SELECT must be scoped to this account: constrain client_id to 2761 in the WHERE clause (scope child tables through their parent). Do not respond with id instead give user name. IMPORTANT: Only use columns that exist in the database schema. Do not assume column names. If a column or table is unclear, call the matching schema tool first and then write the query. SCHEMA VALIDATION: Before it runs, your query is automatically checked against the live database schema. If it references a table or column that does not exist, the query is NOT executed — you receive the database error together with the real columns of every table the query references. When that happens, do not give up or ask the user: read the listed columns, rewrite the query using only those names, and retry immediately. You may query directly and let this check correct you rather than always calling the schema tool first.

execute_campaign_select_query

Use this tool only to run SELECT query against the tables related to client in MySQL database. This the tool to use only to gather information from the MySQL database. The signed-in user is id 2253; use it for questions about "me" or "my". Every SELECT must be scoped to this account: constrain client_id to 2761 in the WHERE clause (scope child tables through their parent). Do not respond with id instead give user name. IMPORTANT: Before using this tool, you MUST first call MySQLClientSchemaTool to understand the database structure. Common mistakes to avoid: - Many tables that seem logical DO NOT exist (e.g., website_page_visits) - Always verify table existence in schema before querying - Use statuses table instead of module-specific status tables IMPORTANT: Only use columns that exist in the database schema. Do not assume column names. If a column or table is unclear, call the matching schema tool first and then write the query. SCHEMA VALIDATION: Before it runs, your query is automatically checked against the live database schema. If it references a table or column that does not exist, the query is NOT executed — you receive the database error together with the real columns of every table the query references. When that happens, do not give up or ask the user: read the listed columns, rewrite the query using only those names, and retry immediately. You may query directly and let this check correct you rather than always calling the schema tool first.

execute_client_select_query

Use this tool only to run SELECT query against the tables related to contract in MySQL database. This the tool to use only to gather information from the MySQL database. The signed-in user is id 2253; use it for questions about "me" or "my". Every SELECT must be scoped to this account: constrain client_id to 2761 in the WHERE clause (scope child tables through their parent). When someone ask you specifically to get info about sent contracts, bring contracts with the statuses 'sent', 'accepted', 'declined', 'messaged', 'bounced', 'clicked', 'complaint', 'delivered', 'viewed', as other statuses can only be assigned after after 'sent' status. When some ask you to get contracts information according to whom it is assigned to, use leads tables assigned_to field, which is foreign key to id of users table, to get the related quotes as quotes are meant for leads. Do not respond with id instead give title or first 30 characters of description. IMPORTANT: Only use columns that exist in the database schema. Do not assume column names. If a column or table is unclear, call the matching schema tool first and then write the query. VERY IMPORTANT: if table has column deleted_at, bring records where deleted_at field's value is null. Always add client_id condition if the column exists as we dont want to leak one client's data to another client. SCHEMA VALIDATION: Before it runs, your query is automatically checked against the live database schema. If it references a table or column that does not exist, the query is NOT executed — you receive the database error together with the real columns of every table the query references. When that happens, do not give up or ask the user: read the listed columns, rewrite the query using only those names, and retry immediately. You may query directly and let this check correct you rather than always calling the schema tool first.

execute_contract_select_query

Use this tool only to run SELECT query against the tables related to form in MySQL database. This the tool to use only to gather information from the MySQL database. The signed-in user is id 2253; use it for questions about "me" or "my". Every SELECT must be scoped to this account: constrain client_id to 2761 in the WHERE clause (scope child tables through their parent). Leads that comes through forms, stores form_id(not the id column) field of forms table to telsa_form_id column of leads table. Do not respond with id instead give user name. IMPORTANT: Only use columns that exist in the database schema. Do not assume column names. If a column or table is unclear, call the matching schema tool first and then write the query. SCHEMA VALIDATION: Before it runs, your query is automatically checked against the live database schema. If it references a table or column that does not exist, the query is NOT executed — you receive the database error together with the real columns of every table the query references. When that happens, do not give up or ask the user: read the listed columns, rewrite the query using only those names, and retry immediately. You may query directly and let this check correct you rather than always calling the schema tool first.

execute_form_select_query

Use this tool only to run SELECT query against the tables related to invoice in MySQL database. This the tool to use only to gather information from the MySQL database. The signed-in user is id 2253; use it for questions about "me" or "my". Every SELECT must be scoped to this account: constrain client_id to 2761 in the WHERE clause (scope child tables through their parent). When some ask you to get invoice information according to whom it is assigned to, use leads tables assigned_to field, which is foreign key to id of users table, to get the related invoices as invoices are meant for leads. Do not respond with id instead give title or first 30 characters of description. IMPORTANT: Only use columns that exist in the database schema. Do not assume column names. If a column or table is unclear, call the matching schema tool first and then write the query. VERY IMPORTANT: if table has column deleted_at, bring records where deleted_at field's value is null. Always add client_id condition if the column exists as we dont want to leak one client's data to another client. SCHEMA VALIDATION: Before it runs, your query is automatically checked against the live database schema. If it references a table or column that does not exist, the query is NOT executed — you receive the database error together with the real columns of every table the query references. When that happens, do not give up or ask the user: read the listed columns, rewrite the query using only those names, and retry immediately. You may query directly and let this check correct you rather than always calling the schema tool first.

execute_invoice_select_query

Use this tool only to run SELECT query against the tables related to leads in MySQL database. This the tool to use only to gather information from the MySQL database. When some ask you to get the best lead generation method, use the leads table and include records where the lead_source column and lead_source is not null and date filter apply on the created_at column, and returned response with lead source name and total lead count of lead source and proper format. IMPORTANT: Before using this tool, you MUST first call MySQLLeadSchemaTool to understand the database structure. Common mistakes to avoid: - Do not assume column names exist in tables without checking schema first - leads table does not have first_name, last_name - these are in lead_contacts table - Use proper JOINs to get contact and company information for leads SCHEMA VALIDATION: Before it runs, your query is automatically checked against the live database schema. If it references a table or column that does not exist, the query is NOT executed — you receive the database error together with the real columns of every table the query references. When that happens, do not give up or ask the user: read the listed columns, rewrite the query using only those names, and retry immediately. You may query directly and let this check correct you rather than always calling the schema tool first. Every SELECT must be scoped to this account: constrain client_id to 2761 in the WHERE clause (scope child tables through their parent).

execute_lead_select_query

Use this tool only to run SELECT query against the tables related to lead_task in MySQL database. always use condition of user must be one of 2247, 2248, 2249, 2250, 2251, 2252, 2253, 2254, 2255, 2256, 2257, 2369, 2636, 2682, 2700, 2744. When query is specific to current user only, use user id 2253. This the tool to use only to gather information from the MySQL database. IMPORTANT: Only use columns that exist in the database schema. Do not assume column names. If a column or table is unclear, call the matching schema tool first and then write the query. SCHEMA VALIDATION: Before it runs, your query is automatically checked against the live database schema. If it references a table or column that does not exist, the query is NOT executed — you receive the database error together with the real columns of every table the query references. When that happens, do not give up or ask the user: read the listed columns, rewrite the query using only those names, and retry immediately. You may query directly and let this check correct you rather than always calling the schema tool first.

execute_lead_task_select_query

Use this tool only to run SELECT query against the tables related to mms in MySQL database. This the tool to use only to gather information from the MySQL database. The signed-in user is id 2253; use it for questions about "me" or "my". Every SELECT must be scoped to this account: constrain client_id to 2761 in the WHERE clause (scope child tables through their parent). Do not respond with id instead give title or first 30 characters of description. Available MMS Tables and their columns: mms table columns: id, user_id, client_id, title, from, description, media_type, is_text_to_speech_audio, text_to_speech_content, created_at, updated_at, deleted_at mms_trackings table columns: id, user_id, client_id, mms_id, lead_id, phone_number, media_type, delivered, twilio_valid, created_at, updated_at, deleted_at If a column or table is unclear, call the matching schema tool first and then write the query. SCHEMA VALIDATION: Before it runs, your query is automatically checked against the live database schema. If it references a table or column that does not exist, the query is NOT executed — you receive the database error together with the real columns of every table the query references. When that happens, do not give up or ask the user: read the listed columns, rewrite the query using only those names, and retry immediately. You may query directly and let this check correct you rather than always calling the schema tool first.

execute_mms_select_query

Use this tool only to run SELECT query against the tables related to phone numbers in MySQL database. This the tool to use only to gather information from the MySQL database. The signed-in user is id 2253; use it for questions about "me" or "my". Every SELECT must be scoped to this account: constrain client_id to 2761 in the WHERE clause (scope child tables through their parent). Do not respond with id instead give phone number. The main table is phone_numbers. Its assigned_to column is JSON (a list of user ids), and user_id/client_id are foreign keys to the users and clients tables. Join users to resolve the owner of a number. IMPORTANT: Only use columns that exist in the database schema. Do not assume column names. If a column or table is unclear, call the matching schema tool first and then write the query. SCHEMA VALIDATION: Before it runs, your query is automatically checked against the live database schema. If it references a table or column that does not exist, the query is NOT executed — you receive the database error together with the real columns of every table the query references. When that happens, do not give up or ask the user: read the listed columns, rewrite the query using only those names, and retry immediately. You may query directly and let this check correct you rather than always calling the schema tool first.

execute_phone_number_select_query

Use this tool only to run SELECT query against the tables related to projects in MySQL database. This the tool to use only to gather information from the MySQL database. The signed-in user is id 2253; use it for questions about "me" or "my". Every SELECT must be scoped to this account: constrain client_id to 2761 in the WHERE clause (scope child tables through their parent). when some one ask you to summarize a project by name, please add all possible names in or condition and use like '%%' query. Do not respond with id instead give name or title. IMPORTANT: Only use columns that exist in the database schema. Do not assume column names. If a column or table is unclear, call the matching schema tool first and then write the query. SCHEMA VALIDATION: Before it runs, your query is automatically checked against the live database schema. If it references a table or column that does not exist, the query is NOT executed — you receive the database error together with the real columns of every table the query references. When that happens, do not give up or ask the user: read the listed columns, rewrite the query using only those names, and retry immediately. You may query directly and let this check correct you rather than always calling the schema tool first.

execute_project_select_query

Use this tool only to run SELECT query against the tables related to project tasks in MySQL database. This the tool to use only to gather information from the MySQL database. The signed-in user is id 2253; use it for questions about "me" or "my". Every SELECT must be scoped to this account: constrain client_id to 2761 in the WHERE clause (scope child tables through their parent). Do not respond with id instead give name or title. IMPORTANT: Only use columns that exist in the database schema. Do not assume column names. If a column or table is unclear, call the matching schema tool first and then write the query. SCHEMA VALIDATION: Before it runs, your query is automatically checked against the live database schema. If it references a table or column that does not exist, the query is NOT executed — you receive the database error together with the real columns of every table the query references. When that happens, do not give up or ask the user: read the listed columns, rewrite the query using only those names, and retry immediately. You may query directly and let this check correct you rather than always calling the schema tool first.

execute_project_task_select_query

Use this tool only to run SELECT query against the tables related to quote also referred as estimates in MySQL database. This the tool to use only to gather information from the MySQL database. The signed-in user is id 2253; use it for questions about "me" or "my". Every SELECT must be scoped to this account: constrain client_id to 2761 in the WHERE clause (scope child tables through their parent). If Request is for single record then, response must contain ID. When someone ask you specifically to get info about sent quotes or estimates, bring estimates with the statuses 'sent', 'accepted', 'declined', 'messaged', 'bounced', 'clicked', 'complaint', 'delivered', 'viewed', as other statuses can only be assigned after after 'sent' status. When some ask you to get quotes information according to whom it is assigned to, use leads tables assigned_to field to get the related quotes as quotes are meant for leads. When some ask you to get total revenue, use estimates and estimate_items table and use estimate_items total column for calculate the revenue and include records where status is accepted and deleted_at is null and date filter apply on estimate_accepted_at column and the total revenue should be returned with proper format, and should remove quote id and type from the response. When some ask to get best sales person/user by revenue, use estimates and estimate_items table and use estimate_items total column for calculate the revenue and include records where status is accepted and deleted_at is null and date filter apply on estimate_accepted_at column and created_by column use for specific user and the total revenue should be returned with proper format, and should remove quote id and type from the response. Do not respond with id instead give title or first 30 characters of description. IMPORTANT: Before using this tool, you MUST first call MySQLQuoteSchemaTool to understand the database structure. Common mistakes to avoid: - Do not assume column names exist - always check schema first - There may be no 'title' column in estimates table - verify in schema - Use estimates table, not quotes table for quote information IMPORTANT: Only use columns that exist in the database schema. Do not assume column names. Don't calculate placeholders value or any other placeholder values in the response. If a column or table is unclear, call the matching schema tool first and then write the query. VERY IMPORTANT: if the table has a column deleted_at, bring records where the deleted_at field's value is null, and the same applies to join tables. Also, Always add client_id condition if the column exists as we dont want to leak one client's data to another client SCHEMA VALIDATION: Before it runs, your query is automatically checked against the live database schema. If it references a table or column that does not exist, the query is NOT executed — you receive the database error together with the real columns of every table the query references. When that happens, do not give up or ask the user: read the listed columns, rewrite the query using only those names, and retry immediately. You may query directly and let this check correct you rather than always calling the schema tool first.

execute_quote_select_query

Use this tool only to run SELECT query against the tables related to SMS/campaigns in MySQL database. This the tool to use only to gather information from the MySQL database. The signed-in user is id 2253; use it for questions about "me" or "my". Every SELECT must be scoped to this account: constrain client_id to 2761 in the WHERE clause (scope child tables through their parent). Do not respond with id instead give title or first 30 characters of description. IMPORTANT: Only use columns that exist in the database schema. Do not assume column names. If a column or table is unclear, call the matching schema tool first and then write the query. SCHEMA VALIDATION: Before it runs, your query is automatically checked against the live database schema. If it references a table or column that does not exist, the query is NOT executed — you receive the database error together with the real columns of every table the query references. When that happens, do not give up or ask the user: read the listed columns, rewrite the query using only those names, and retry immediately. You may query directly and let this check correct you rather than always calling the schema tool first.

execute_sms_select_query

Use this tool only to run SELECT query against the tables related to user in MySQL database. This the tool to use only to gather information from the MySQL database. The signed-in user is id 2253; use it for questions about "me" or "my". Do not respond with id instead give user name. IMPORTANT: Before using this tool, you MUST first call MySQLUserSchemaTool to understand the database structure. Common mistakes to avoid: - There is NO 'name' column in users table - use first_name and last_name instead - Use CONCAT(first_name, ' ', last_name) to get full name - Check schema first to understand table structure All response should be in detailed. Like need to describe the answer in detail. Also ask user for more details if needed. Like, Let me know for more details or etc. IMPORTANT: Only use columns that exist in the database schema. Do not assume column names. If a column or table is unclear, call the matching schema tool first and then write the query. SCHEMA VALIDATION: Before it runs, your query is automatically checked against the live database schema. If it references a table or column that does not exist, the query is NOT executed — you receive the database error together with the real columns of every table the query references. When that happens, do not give up or ask the user: read the listed columns, rewrite the query using only those names, and retry immediately. You may query directly and let this check correct you rather than always calling the schema tool first. Every SELECT must be scoped to this account: constrain client_id to 2761 in the WHERE clause (scope child tables through their parent).

execute_user_select_query

Use this tool only to run SELECT query against the tables related to website page in MySQL database. This the tool to use only to gather information from the MySQL database. The signed-in user is id 2253; use it for questions about "me" or "my". Every SELECT must be scoped to this account: constrain client_id to 2761 in the WHERE clause (scope child tables through their parent). Do not respond with id instead give title. IMPORTANT: Only use columns that exist in the database schema. Do not assume column names. If a column or table is unclear, call the matching schema tool first and then write the query. SCHEMA VALIDATION: Before it runs, your query is automatically checked against the live database schema. If it references a table or column that does not exist, the query is NOT executed — you receive the database error together with the real columns of every table the query references. When that happens, do not give up or ask the user: read the listed columns, rewrite the query using only those names, and retry immediately. You may query directly and let this check correct you rather than always calling the schema tool first.

execute_website_page_select_query

Returns the click path to a feature in the Telagus dashboard, for "how do I ...", "where do I ...", or "how do I set up ..." questions about parts of the app that have no tool of their own. Call it with an optional `topic` to get the routes that match, or with no arguments to get every route it knows. It only returns navigation guidance: it reads no account data and changes nothing, so it is safe to call whenever a user asks where something lives. Topics covered: create forms, update forms, check client campaign, list mms, create mms, update mms, check report of mms, whatsapp, create automation, update automation, website builder, gmail integration, outlook integration, create events, update events, scheduled events, manage availability, appointments, xero, quickbooks, ecommerce integration, seo reports, ppc reports, website ads reports, website analytics, page visitors, call tracking, chat, team, leave, public holiday, time card, monthly invoice, settings. Give the user the path exactly as returned.

extra_tool

Insert a new lead to database with contact and company information. Required parameters: first_name, email, lead_title. Optional parameters: last_name, lead_source, mobile_number, position_name, lead_stage_name, company_name, company_website, phone_number, street_address, city, state, postcode. If position_name is provided and that position has stages enabled (has_stages=1), lead_stage_name is required.

insert_lead

This tool helps with invoice management. It allows you to create, update, and manage invoices and their items: 1. LIST INVOICES: Get a list of all invoices by setting action='list_invoices'. You can optionally filter by email. Returns: A list of invoices with their IDs and details. 2. CREATE INVOICE: Create a new invoice by setting action='create_invoice' and providing the required parameters: bill_to (lead ID), bill_date (YYYY-MM-DD format), due_date (YYYY-MM-DD format). Optional parameters include note, tax_id, tax_id2, and items. If you want to add items during invoice creation, provide an array of items with either item_id or title, and quantity (both required). Example format for items: [{'title': 'Website Development', 'quantity': 2, 'rate': 100}, {'item_id': 5, 'quantity': 1}]. Returns: Confirmation message with the invoice ID and number of items added (if any). 3. UPDATE INVOICE: Update an existing invoice by setting action='update_invoice' and providing invoice_id. You can update bill_date, due_date, note, status, tax_id, and tax_id2. Returns: Confirmation message with the invoice ID and updated details. 4. LIST INVOICE ITEMS: View all items for a specific invoice by setting action='list_invoice_items' and providing invoice_id. Returns: A list of items with their IDs and details, along with invoice summary. 5. ADD ITEM TO INVOICE: Add an item to an invoice by setting action='add_item_to_invoice' and providing invoice_id and item details. Required item parameters: title, quantity, rate. Optional item parameters: description, unit_type, item_id (if referencing an existing item). Returns: Confirmation message that the item was added to the invoice. 6. UPDATE INVOICE ITEM: Update an item in an invoice by setting action='update_invoice_item' and providing item_id. You can update title, quantity, rate, description, and unit_type. Returns: Confirmation message with the updated item details. 7. REMOVE INVOICE ITEM: Remove an item from an invoice by setting action='remove_invoice_item' and providing item_id. Returns: Confirmation message that the item was removed from the invoice. 8. SEND INVOICE EMAIL: Send an invoice by email by setting action='send_invoice_email' and providing invoice_id, to, and subject parameters. Optional parameters include cc and bcc. Returns: Confirmation message that the invoice was sent by email. You can use these actions in any order as needed.

invoice_tool

This tool allows you to manage MMS messages. Available actions: 1. SEND MMS: Set action='send_mms' to send an MMS message. Required parameters: - to_number: The recipient's phone number (must include country code) - media_id: ID of the media to send The tool will validate that you have sufficient MMS credits and a valid sender number before sending the message. Returns a success message if the MMS was sent successfully, or an error message if there was a problem. 2. LIST MMS: Set action='list_mms' to get a list of MMS messages. Returns a list of MMS messages, each containing mmsId, title, mediaType, and fromNumber. Use these actions as needed to manage your MMSId.

mms_tool

Returns a progressive, plan-ready brief for a project task: the task itself (resolved status, assignee, collaborators, document attachments), its parent project, the task comment thread (with attachments and nested replies), a paged basic list of its sub-tasks (10 at a time, with offset/total/next_offset), and the FULL detail of one focused sub-task (description, attachments, comments, replies) ready to be planned/resolved. Defaults to focusing the first sub-task of the returned page (newest-first ordering, so the most recent on page one); pass subtask_id to focus a specific one and subtask_offset to page the list, so an agent can resolve sub-tasks one at a time. The brief is capped at 40,000 characters: if it runs over, the oldest comments are dropped and the result says truncated: true with a notice — read totals from the `totals` keys, not from the lists.

project_task_details

This tool helps with project and task management. It allows you to create, update, and manage projects and tasks: 1. LIST PROJECTS: Get a list of all projects by setting action='list_projects'. Returns: A list of projects with their IDs and details. 2. GET PROJECT: Get details of a specific project by setting action='get_project' and providing project_id. Returns: Details of the specified project. 3. CREATE PROJECT: Create a new project by setting action='create_project' and providing the required parameters: title, start_date, deadline. Optional parameters include description, status, and category_id. Returns: Confirmation message with the project ID. 4. UPDATE PROJECT: Update an existing project by setting action='update_project' and providing project_id and the parameters to update. Returns: Confirmation message with the updated project details. 5. DELETE PROJECT: Delete a project by setting action='delete_project' and providing project_id. Returns: Confirmation message that the project was deleted. 6. LIST TASKS: Get a list of all tasks for a project by setting action='list_tasks' and providing project_id. Returns: A list of tasks with their IDs and details. 7. GET TASK: Get details of a specific task by setting action='get_task' and providing task_id. Returns: Details of the specified task. 8. CREATE TASK: Create a new task by setting action='create_task' and providing the required parameters: title, project_id, status_id, and assigned_to. Optional parameters include description, collaborators, start_date, deadline, and time_estimate. Note: The assigned user will automatically be added to the collaborators list. Returns: Confirmation message with the task ID. 9. UPDATE TASK: Update an existing task by setting action='update_task' and providing task_id and the parameters to update. Returns: Confirmation message with the updated task details. 10. DELETE TASK: Delete a task by setting action='delete_task' and providing task_id. Returns: Confirmation message that the task was deleted. 11. ASSIGN MEMBER: Assign a member to a project by setting action='assign_member' and providing project_id and user_id. Optional parameter is_leader to set the member as a project leader. Returns: Confirmation message that the member was assigned to the project. 12. REMOVE MEMBER: Remove a member from a project by setting action='remove_member' and providing project_id and user_id. Returns: Confirmation message that the member was removed from the project. 13. ADD COMMENT: Add a comment to a project or task by setting action='add_comment' and providing description and either project_id or task_id. Optional parameter parent_comment_id to reply to an existing comment. Returns: Confirmation message that the comment was added. 14. ADD SUBTASK: Add a sub-task to a task by setting action='add_subtask' and providing task_id and sub_task_title. Optional parameters include description and time_in_minutes. Returns: Confirmation message with the sub-task ID. 15. EDIT SUBTASK: Edit an existing sub-task by setting action='edit_subtask' and providing subtask_id and sub_task_title. Optional parameters include description and time_in_minutes. Returns: Confirmation message that the sub-task was updated. You can use these actions in any order as needed. Over this connection client_id is not accepted: every call acts on your own account and is attributed to you.

project_tool

This tool allows you to manage SMS messages. Available actions: 1. SEND SMS: Set action='send_sms' to send an SMS message. Required parameters: - to_number: The recipient's phone number (must include country code) Optional parameters (one of these must be provided): - message: The content of the SMS message to send (required if sms_id is not provided) - sms_id: ID of an existing SMS to send (if provided, message parameter is ignored) The tool will validate that you have sufficient SMS credits and a valid sender number before sending the message. Returns a success message if the SMS was sent successfully, or an error message if there was a problem. 2. LIST SMS: Set action='list_sms' to get a list of SMS messages. Returns a list of SMS messages with their IDs, descriptions, and from numbers. Use these actions as needed to manage your SMS messages.

sms_tool

Change an existing custom field's definition. Identify it by its current title and supply only what should change. If several custom fields share a title, the most recently updated one is the one modified. One of: text, textarea, selectbox, radiobuttons, checkboxes, single_checkbox, date. Everyday names are accepted too and are converted to the stored name — "dropdown" becomes selectbox, "radio" becomes radiobuttons, "checkbox" becomes checkboxes, "toggle" becomes single_checkbox. Options must be supplied for selectbox, radiobuttons, checkboxes. This tool changes the field definition. It does not set a value on any record: filling a custom field in for a particular lead or user is done in Telagus. When the user message contains 'update custom field from below details' followed by parameter details in the format 'parameter_name:parameter_value', extract these parameters and use them directly without asking for additional information. Fields for health information, biometric data, national or government identifiers, payment card or bank details, authentication credentials, or a protected characteristic such as a date of birth or gender cannot be created or renamed over this connection, and neither can a field that accepts a file upload. They are managed in Telagus at Dashboard > Settings > Custom Fields.

update_custom_field

Update an existing lead in the database. Required parameters: email (to identify the lead). If multiple leads have the same email, only the most recently updated lead will be modified. Optional parameters include lead properties (lead_title, lead_source, assigned_to, lead_position_id, lead_stage_name), contact properties (first_name, last_name, new_email, mobile_number, job_title), and company properties (company_name, company_website, phone_number, street_address, city, state, postcode). If lead_position_id is provided and that position has stages enabled (has_stages=1), lead_stage_name is required. If company properties are provided but no company exists, a new company will be created.

update_lead

Returns the profile details of the current authenticated user (the one making this request) as JSON. Takes no parameters — use it to answer "who am I", "my account", or "my details" style questions. To look up other users in the account, use the user schema and select tools instead.

user_get