Telagus

Retrieves MySQL database schema information including tables, columns, relationships, and indexes. This tool covers these tables: invoices, invoice_items, invoice_payments, 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_invoice_schema

Retrieves MySQL database schema information including tables, columns, relationships, and indexes. This tool covers these tables: leads, lead_contacts, lead_companies. 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_lead_schema

Retrieves MySQL database schema information including tables, columns, relationships, and indexes. This tool covers these tables: lead_tasks, lead_task_status, lead_task_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_lead_task_schema

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

Clocks the signed-in user in by creating a new attendance record. The clock-in time defaults to now.

clock_in

Clocks out an existing attendance record by setting its clock-out time, which defaults to now. Non-admins can only clock out their own records.

clock_out

Creates an invoice from an existing quote, copying its items. It does not send the invoice.

convert_quote_to_invoice

Saves a new automation definition in the user's Telagus account (Marketing > Automation): a trigger and an ordered list of steps, stored as configuration in the same format the Automation page's builder saves. Use IDs from get_automation_options. This call only writes that one record. It performs none of the steps: it sends, assigns, tags, moves and creates nothing, and the automation is always saved switched off. Telagus's own automation scheduler carries out the steps later, for leads that match the trigger, and only once the user has switched the automation on with set_automation_status. Returns the automation ID and editor link.

create_automation

Saves HTML the user supplied as a new email campaign. It does not send anything. To have an email written from a brief, use write_campaign_email instead. You can use shortcodes like {!!customerName!!}, {!!companyName!!} and {!!mobileNumber!!} in html_body for data filled in when the campaign is sent.

create_campaign

Creates a new contract for the latest lead with the given email, optionally with items. It does not send it. Each item needs a title and a quantity, and may give a rate, e.g. [{"title": "Website Development", "quantity": 2, "rate": 100}]. A title matching a catalogue item takes that item's rate and unit type.

create_contract

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

Creates a new invoice for a lead, optionally with line items. It does not send it. Each item needs an item_id (an existing catalogue item) or a title, and a quantity, e.g. [{"title": "Website Development", "quantity": 2, "rate": 100}, {"item_id": 5, "quantity": 1}].

create_invoice

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

Creates a new project. The signed-in user is emailed about it.

create_project

Creates a project from a quote, found by quote_id or by the lead's email, and returns a link to open the project.

create_project_from_quote

Creates a task in a project. The assignee is added to the collaborators, and the signed-in user, the assignee and the collaborators are emailed about it.

create_project_task

Creates a new quote for the latest lead with the given email, optionally with items. It does not send it. Each item needs an item_id (an existing catalogue item) or a title, and a quantity, e.g. [{"title": "Website Development", "quantity": 2}, {"item_id": 5, "quantity": 1}]. A title matching a catalogue item takes that item's rate and unit type.

create_quote

Deletes a project.

delete_project

Deletes a project task.

delete_project_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

Emails a contract to the address given, with optional CC and BCC addresses and a message.

email_contract

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 143; use it for questions about "me" or "my". Every SELECT must be scoped to this account: constrain client_id to 1 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 143; use it for questions about "me" or "my". Every SELECT must be scoped to this account: constrain client_id to 1 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 143; use it for questions about "me" or "my". Every SELECT must be scoped to this account: constrain client_id to 1 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 143; use it for questions about "me" or "my". Every SELECT must be scoped to this account: constrain client_id to 1 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 143; use it for questions about "me" or "my". Every SELECT must be scoped to this account: constrain client_id to 1 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 1 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 12, 16, 21, 69, 143, 515, 519, 645, 1677, 1748, 1753, 1764, 1900, 1909, 2042, 2154, 2205, 2259, 2302, 2344, 2350, 2397, 2434, 2534, 2555, 2560, 2594, 2595, 2596, 2653, 2658, 2668, 2669, 2673, 2681, 2685, 2686, 2689, 2693, 2694, 2695, 2697, 2706, 2715, 2724, 2749, 2752. When query is specific to current user only, use user id 143. 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 143; use it for questions about "me" or "my". Every SELECT must be scoped to this account: constrain client_id to 1 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 143; use it for questions about "me" or "my". Every SELECT must be scoped to this account: constrain client_id to 1 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 143; use it for questions about "me" or "my". Every SELECT must be scoped to this account: constrain client_id to 1 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 143; use it for questions about "me" or "my". Every SELECT must be scoped to this account: constrain client_id to 1 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 143; use it for questions about "me" or "my". Every SELECT must be scoped to this account: constrain client_id to 1 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