{"id":"com.serviche/sergio","slug":"com-serviche-sergio","title":"Sergio by Serviche","description":"Make sure nothing falls through the cracks in your cleaning business, even when you're not watching.","version":"1.0.2","publisher":{"kind":"domain","id":"serviche.com","label":"serviche.com","url":"https://serviche.com"},"website":"https://sergio.serviche.com/mcp","repository":"","remotes":[{"type":"streamable-http","url":"https://sergio.serviche.com/api/agent/mcp"}],"packages":[],"published":"2026-11-08","updated":"2026-11-08","status":"online","auth":"","latency_ms":4183,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"whoami","title":"Who am I","description":"Returns this agent seat: its name, role, member id, the organization it belongs to, the key id this call used, whether the owner allowed it to run SQL queries, and what it reads as (readsAs: \"owner\" when the owner allowed owner-level reading for this key, else its role) versus what it acts as (actsAs: always its role).","read_only":true},{"name":"catalog","title":"What can I do","description":"Returns `asks`, a short list of things a person can ask (give your user these when they ask what you can do), then lists every tool this seat can call right now, grouped by family, with whether each one changes anything, and under `held` the actions only a person can do (sending, money, access), each with the reason and where in the app the owner does it, and under `not_lent` every other app actio","read_only":true},{"name":"report_feedback","title":"Report a bug or idea to the Sergio team","description":"Files a bug report or feature request with the Sergio team. It lands in the team's one Feedback inbox, the same place the in-app help bubble's reports go, tagged with this agent seat, and the team is notified the moment it is filed. There is no other feedback channel to try. Check with your user first unless they have already told you that you may report without asking; afterwards, tell your user ","read_only":false},{"name":"events_subscribe","title":"Subscribe to events","description":"Create or update this seat's one event subscription. inputs: which arrivals (omit for all: text_in, text_out, email_in, email_out, call_answered, call_missed, voicemail, booking_created, booking_changed, booking_cancelled, staff_clocked_in, staff_not_clocked_in, job_finished, visit_unconfirmed). contact_types: only arrivals for these contact types. A field you omit keeps its current value, so {pau","read_only":false},{"name":"events_list","title":"Pull events","description":"Returns the next events for this seat, oldest first, after `cursor` (omit it to continue from your last ack). Each event names an arrival by id (a text, email, call, or booking change); fetch its detail with read(). Delivery is at-least-once: dedupe on event_id. Pass next_cursor to the next call, and ack it with events_ack once you have processed the page. An error cursor_expired (410) means event","read_only":true},{"name":"events_ack","title":"Acknowledge events","description":"Stores `cursor` (a next_cursor you received) as this seat's high-water mark, so events_list with no cursor resumes after it. It only moves forward; an older cursor changes nothing.","read_only":false},{"name":"read","title":"read","description":"Read ANYTHING about the business: read(entity, filters). ENTITIES (key: purpose [main filters]): conversations: The inbox list of conversations [status, from, to, needs_reply, conversation_id, ...] | conversation_transcript: A client's whole history in one timeline [conversation_id, client_ref, from, to, search] | communications: Every text, email and call across the business in ONE read [from, to","read_only":true},{"name":"query","title":"query","description":"Run a read-only SQL SELECT over the business database and get rows back. It is the FALLBACK, not the first move: when a read(entity) answers the question (leads, clients, conversations, bookings and the rest of read's catalog), use read, which carries the business's own definitions (e.g. open leads = read lead_pursuits active:true) that raw tables do not. Use query only when read cannot express th","read_only":true},{"name":"findClientByIdentifier","title":"findClientByIdentifier","description":"Look up a client ID by a single identifier (phone or email). Returns the client ID or null. Simpler than resolveClient. No creation, no merge. Use for a quick check: \"is this phone number already a client?\".","read_only":true},{"name":"send_text","title":"Send a text (after your person confirms)","description":"Texts a client or teammate on your person's order, from the business number, as a Manual send under the business's Sending setting. Use it whenever your person asks you to text someone now, with their words or words you wrote for them (\"text today's cleaners about the weather\"); create_draft leaves it for someone else to send later. First call without confirm_token: nothing is sent; you get a prev","read_only":false},{"name":"start_group_text","title":"Open a group text thread","description":"Opens the one group text thread for 2 to 9 contacts who each have a phone, as the inbox's New conversation with several people checked does (an existing group for the same people is reused). Nothing is sent; texting it is send_conversational_message, which shows your person the words first. Pass the same idempotency_key when retrying.","read_only":false},{"name":"open_conversation_by_phone","title":"Open a conversation for a phone number","description":"Opens (or finds) the one conversation for a phone number nobody is saved under, as the inbox search's Text <number> does. Nothing is sent. Pass the same idempotency_key when retrying.","read_only":false},{"name":"assign_conversation","title":"Assign a conversation","description":"Assigns a conversation to a teammate, as the thread header's Assign menu does: assigned_member_id is the teammate's id (read entity org_members), or null to unassign; assigned_to (the teammate's exact name) is accepted instead. A name that is not exactly one current teammate is refused. Pass the same idempotency_key when retrying.","read_only":false},{"name":"set_conversation_status","title":"Mark a conversation done, or reopen it","description":"Marks a thread done (status resolved) or reopens it (status new), as the inbox's Done and Reopen do; the Quo inbox follows when the business's write setting allows. A thread that still owes the customer a reply is refused unless replyOwedOverride is true (say why to your person first). Pass the same idempotency_key when retrying.","read_only":false},{"name":"bulk_clear_conversations","title":"Clear old conversations in bulk","description":"Clears every thread older than a cutoff at once, as the inbox's bulk Clear does (owner or admin seats only): mode date clears threads quiet for olderThanDays (default 14) or since cutoff (ISO date); mode leads clears threads a lead follow-up owns. includeTasks also closes their open tasks; includeReplyOwed also clears threads the customer wrote last in (date mode). The Quo inbox follows when the b","read_only":false},{"name":"snooze_conversation","title":"Mute a conversation for a few minutes","description":"Mutes a conversation until snoozed_until (ISO 8601, in the future), at most 10 minutes from now (a later time is cut to 10 minutes), as the inbox's Mute does while someone is on a call. note is optional. For a later follow-up, use set_conversation_reminder. Pass the same idempotency_key when retrying.","read_only":false},{"name":"unsnooze_conversation","title":"Unmute a conversation","description":"Ends a conversation's mute now, as the inbox's Unmute does. Pass the same idempotency_key when retrying.","read_only":false},{"name":"set_conversation_reminder","title":"Set a reminder on a conversation","description":"Adds a reminder on a conversation, as the thread's bell does: remind_at (ISO 8601) and an optional note become a task due then. hide_until_due: true also tucks the thread away until the reminder is due (a reply from the person brings it back). Pass the same idempotency_key when retrying; a repeat returns the first reminder.","read_only":false},{"name":"dismiss_conversation_reminders","title":"Dismiss a conversation's reminders","description":"Dismisses every open reminder on a conversation, as the bell's Dismiss does. Pass the same idempotency_key when retrying.","read_only":false},{"name":"link_conversation_to_client","title":"Link a conversation to a contact","description":"Links a conversation to a contact, as the inbox's Link to a contact does: if the contact already has a one-to-one thread, it is folded into this one, and an email thread's address is saved to the contact. Sergio learns the correction for later emails. Pass the same idempotency_key when retrying.","read_only":false},{"name":"merge_conversations","title":"Merge two conversations","description":"Moves everything in conversation_id (messages, calls, emails, tasks) into target_conversation_id and removes the empty one, as the thread menu's Merge does. It cannot be split back. Pass the same idempotency_key when retrying; the same pair merges once.","read_only":false},{"name":"track_conversation_as_lead","title":"Track a conversation as a new lead","description":"Opens a lead for this thread's contact, as the thread header's Track this as a new lead does, for a customer asking about new work. request is what they asked for, in a line. Refused when lead follow-up is off, the thread has no contact, or the contact is staff, an applicant or spam. Pass the same idempotency_key when retrying.","read_only":false},{"name":"disposition_conversation","title":"Record a quiet thread's disposition","description":"Records why a quiet thread needs no reply, as the clear gate's picker does: spam (the contact becomes spam; its lead work stops and its Quo card is tagged when the business's write setting allows), lead (the contact becomes a lead), reengage (tags the contact for a later marketing touch) or no_action. It does not clear the thread. Pass the same idempotency_key when retrying.","read_only":false},{"name":"start_conversation_flow","title":"Start a flow on a conversation","description":"Starts a flow on a conversation, as the thread's flow picker does: flowId names an active flow (read entity flows); its steps become tasks with deadlines. label is optional. Pass the same idempotency_key when retrying.","read_only":false},{"name":"close_conversation_flow","title":"Mark a conversation's flow done","description":"Marks a conversation's flow done, as the flow chip's Mark done does. conversationFlowId names the flow when the thread has more than one. outcome (for example declined) closes it early without marking its steps done; close_note is optional. Pass the same idempotency_key when retrying.","read_only":false},{"name":"remove_conversation_flow","title":"Remove a flow from a conversation","description":"Takes one flow off a conversation, as the flow chip's Remove does; its open step tasks are removed. conversationFlowId names the flow. reason is optional. Pass the same idempotency_key when retrying.","read_only":false},{"name":"edit_draft","title":"Edit or discard a draft","description":"Edits a draft in a conversation's draft box, as a person typing in it does: body, subject (email), whyNote, isReady, or status 'discarded' to throw it away. Nothing is sent; a person still presses Send. draft_id comes from create_draft or read. Pass the same idempotency_key when retrying.","read_only":false},{"name":"send_email","title":"Send an email (after your person confirms)","description":"Emails a client from the business mailbox on your person's order, as a Manual send under the business's Sending setting. First call without confirm_token: nothing is sent; you get a preview (to, subject and the exact text) and a confirm_token. Show your person the preview word for word, and only after they say yes, call again with the same arguments and the SAME idempotency_key, plus confirm_token","read_only":false},{"name":"create_draft","title":"Draft a message","description":"Writes a message into a client conversation's draft box. It never sends: a person on the team reviews the exact text and presses Send in Sergio, where the organization's sending policy applies. Give conversationId, or clientId to use that client's conversation. Pass the same idempotency_key when retrying; a repeat returns the original draft.","read_only":false},{"name":"redraft_lead_step","title":"Redraft a lead's upcoming text step","description":"Rewrites the text of a lead's upcoming step that a person sends, from the conversation so far, as the journey's Update draft does (one AI draft, billed like the composer's Draft). Refused for a call step, a step Sergio sends on its own, or a step already past. Nothing is sent. task_id is the lead (read entity tasks); step_id is the step's id from the lead's journey. Pass the same idempotency_key w","read_only":false},{"name":"set_lead_outcome","title":"Record a lead's outcome","description":"Records what happened with a lead, as the lead card's Close menu and taps do. tap: quoted (they have a price); booked (closes it won, on the booking when one for them exists, else on your word); confirmed_booked (the same as booked); call_back_on (date YYYY-MM-DD, or at as an ISO time: pauses the lead until then; the pause ends by itself on that date, when a message goes either way, or when a step","read_only":false},{"name":"move_lead_journey","title":"Move a lead to another journey","description":"Moves a lead to another follow-up journey (segmentId, as Settings > Lead follow-ups names them: read the lead program), at the same place in the sequence, as the lead's journey tag does. Pass the same idempotency_key when retrying.","read_only":false},{"name":"hold_follow_ups","title":"Hold automatic follow-ups","description":"Puts a lap's automatic follow-ups on hold, as its Hold follow-ups switch does: lead follow-ups, a feedback check-in and a review request all obey the one hold. No step goes out on its own; each is drafted for a person. Turning them back on is your person's, in the app. Pass the same idempotency_key when retrying.","read_only":false},{"name":"hold_lead_follow_ups","title":"Hold automatic follow-ups","description":"Puts a lap's automatic follow-ups on hold, as its Hold follow-ups switch does: lead follow-ups, a feedback check-in and a review request all obey the one hold. No step goes out on its own; each is drafted for a person. Turning them back on is your person's, in the app. Pass the same idempotency_key when retrying.","read_only":false},{"name":"edit_lead_step","title":"Change a step in a lead's follow-ups","description":"Changes one step of one lead's follow-ups, as the journey list does. Send one or more of: dueAt (ISO time, or null for the plan's timing; must stay after the step before it), channel ('message', 'email', 'call', 'reply', or null for the plan), removed (true takes it out, false puts it back), keep: true (its custom text is still right after the latest conversation). Or addAfter ('message', 'email',","read_only":false},{"name":"update_payroll_settings","title":"Change payroll settings","description":"Changes one payroll setting per call, as Payroll settings on the staff page does: providerPayFallbackPct (0 to 1), providerPayDefault ({ unit: visit or hour, cents }), or payHoursFrom (booked or approved_time_logs). Staff pay settings only; no money moves. Pass the same idempotency_key when retrying. An owner-level change: Sergio tells the owner after it is made.","read_only":false},{"name":"add_staff_member","title":"Add a staff member","description":"To rename someone already on the roster, pass rename_staff_id with the new name; the old spelling keeps pointing at them. Otherwise adds a field worker to the roster, as the staff page's Add staff does: name (a profile with that name is reused, never duplicated), optional employment_type (employee or contractor), or client_id to make an existing contact staff (a name clash comes back as name_confl","read_only":false},{"name":"edit_staff_member","title":"Change a staff member's details","description":"Changes one staff member (staff_id, from read staff_roster or staff_detail) as Save in their staff drawer does. Pass only what changes: employmentType (employee reads Staff, contractor reads Contractor), payRateCents with payRateUnit (hour, visit or percent; null clears), publicBookable (customers can pick them on the booking page), portalBookable (clients can pick them in the portal), payHidden (","read_only":false},{"name":"clear_staff_availability_override","title":"Clear a worker's schedule change for a date","description":"Clears one field worker's schedule change on a date (YYYY-MM-DD), so their normal weekly hours apply again, as Clear on the staff calendar does. To set a change, use set_staff_availability. Nothing is sent. Pass the same idempotency_key when retrying.","read_only":false},{"name":"set_staff_weekly_hours","title":"Save a field worker's weekly hours or details","description":"Replaces the regular weekly hours of the workers named in staffNames with exactly the windows in entries (day_of_week 0 = Sunday to 6 = Saturday, HH:MM times; several windows a day allowed; a named worker with no entries has no regular hours). Workers not in staffNames are untouched. Omit entries to leave hours alone and only save profiles (the worker's details: email, phone, allergies, and venmo ","read_only":false},{"name":"record_staff_event","title":"Record a warning, kudos or note for a field worker","description":"Adds one entry to a field worker's (staff_id) staff log and their attendance and feedback counts: kind warning (a conduct warning), kudos, note, client_feedback (with sentiment), or sick, late, no_show. A sick day, late arrival or no-show that cancelled or moved a visit is recorded by cancelling or reassigning that booking with the cleaner's reason instead, so do not record those twice. occurredOn","read_only":false},{"name":"add_staff_scheduling_rule","title":"Add a scheduling rule for a field worker","description":"Adds a plain-English scheduling rule for one field worker (staff_id), as Add rule on their Rules tab does, e.g. \"Won't work Tuesdays\" or \"Only mornings in Brooklyn\". hardness hard (default: never scheduled against it) or soft (avoided when possible). The same wording again updates the same rule. Answers the worker's rules with their ids. Remove one with remove_staff_scheduling_rule; read every rul","read_only":false},{"name":"remove_staff_scheduling_rule","title":"Remove a field worker's scheduling rule","description":"Removes one plain-English scheduling rule (ruleId, from add_staff_scheduling_rule or read staff_scheduling_rules) from a field worker (staff_id), as remove on their Rules tab does. Answers the rules left. Pass the same idempotency_key when retrying. An owner-level change: Sergio tells the owner after it is made.","read_only":false},{"name":"review_cleaner_roster","title":"Sort a cleaner name from bookings","description":"Sorts one cleaner name found on bookings, as the Get started card's Review your cleaner roster does: action add (adds them to the roster and links their past jobs), not_staff (this name is not one of our cleaners), or link (it is staffId under another spelling; links their past jobs). Nothing is sent. Pass the same idempotency_key when retrying.","read_only":false},{"name":"answer_google_review_match","title":"Link or unlink a Google review and a client","description":"Says which client wrote a Google review, as Contacts > Needs review does: client_id links it (also moving a review linked to the wrong client), client_id null says no client wrote it (unlinking a linked review). A link closes that client's review requests. Find reviews and their ids with read google_reviews. Nothing is sent or posted to Google. Pass the same idempotency_key when retrying.","read_only":false},{"name":"edit_contacts","title":"Edit contacts in bulk","description":"Applies one edit to up to 5000 contacts, as the Contacts page's selection bar does: op add_to_list / remove_from_list (listId), add_tags / remove_tags (tagIds), set_service_category (value residential, commercial, both or null), set_lead_source (value thumbtack, google_lsa, yelp, bark, website_form, google_business_profile, referral, booking_software, direct, web_chat, other or null), set_type (ty","read_only":false},{"name":"accept_smaller_sync","title":"Accept a smaller sync","description":"Applies a booking sync Sergio held back for returning far fewer bookings than it holds, once, and makes that size the new normal, as Accept this smaller sync on Data sources does. job_id is the held sync's import job. Pass the same idempotency_key when retrying. An owner-level change: Sergio tells the owner after it is made.","read_only":false},{"name":"upload_spreadsheet","title":"Upload a spreadsheet to import","description":"Uploads a bookings or clients spreadsheet (CSV text) and queues its import, as Upload on the Imports page does; nothing is written to customers until its columns are checked. source is the import source spelling, not a free label: a booking platform's key for its bookings export (for example bookingkoala), that key plus -clients for its clients export (for example bookingkoala-clients), or spreads","read_only":false},{"name":"start_spreadsheet_import","title":"Start an uploaded spreadsheet's import","description":"Starts the import of a spreadsheet uploaded with upload_spreadsheet, as Start in the import drawer does: Sergio checks its columns; a confident mapping imports, an uncertain one answers status needs_review and waits for review_import_mapping. Pass the same idempotency_key when retrying.","read_only":false},{"name":"review_import_mapping","title":"Approve or discard a spreadsheet's columns","description":"Settles an import waiting at the column review, as its review card does: decision approve (the import runs with the confident columns plus keepFields; keepValues and assignValues teach status words) or discard (nothing is written). Pass the same idempotency_key when retrying. An owner-level change: Sergio tells the owner after it is made.","read_only":false},{"name":"set_scanner_on","title":"Turn a Scanner on or off","description":"Turns one of the business's Scanners on or off, as the On switch in Automations > Scanners does. A Scanner is only ever on or off (never a trial mode). scanner_id comes from read('scanners'). Pass the same idempotency_key when retrying. An owner-level change: Sergio tells the owner after it is made.","read_only":false},{"name":"create_scanner","title":"Create a Scanner","description":"Saves a new Scanner, as Save on New Scanner does: question (required), and optionally name, inputs, look-again timing, who gets the task, due rule, destination, contact types, and enabled (on or off; there is no trial mode). Pass the same idempotency_key when retrying. An owner-level change: Sergio tells the owner after it is made.","read_only":false},{"name":"edit_scanner","title":"Edit a Scanner","description":"Changes a Scanner, as its editor on the Scanners page does: any of name, question, inputs, look-again timing, who gets the task, due rule, destination, contact types, enabled. scanner_id comes from read('scanners'). Pass the same idempotency_key when retrying. An owner-level change: Sergio tells the owner after it is made.","read_only":false},{"name":"delete_scanner","title":"Delete a Scanner","description":"Deletes a Scanner, as Delete in its editor does; the tasks it already made stay. To pause it instead, use set_scanner_on with enabled false. Pass the same idempotency_key when retrying. An owner-level change: Sergio tells the owner after it is made.","read_only":false},{"name":"create_contact_list","title":"Make a contact list","description":"Makes a contact list on the Contacts page, or answers the live one with that name. Add people to it with edit_contacts (op add_to_list). Pass the same idempotency_key when retrying.","read_only":false},{"name":"edit_contact_list","title":"Rename or archive a contact list","description":"Renames a contact list or archives it (archived: true; its people keep their other lists), as the Contacts page's list menu does. Pass the same idempotency_key when retrying.","read_only":false},{"name":"create_contact_tag","title":"Make a contact tag","description":"Makes a tag on the Contacts page, or answers the live one with that name. Tag people with edit_contacts (op add_tags). Pass the same idempotency_key when retrying.","read_only":false},{"name":"edit_contact_tag","title":"Rename or archive a contact tag","description":"Renames a Contacts tag or archives it (archived: true), as the Contacts page's tag menu does. Pass the same idempotency_key when retrying.","read_only":false},{"name":"create_campaign","title":"Build a campaign (saved as a draft)","description":"Builds a campaign as the Campaigns page's New campaign does, always saved as a draft: name, the messages (steps: the opener first, each { template, delayDays?, channel? text | email | call }), offer, audience (audience_filter, or audience_source { kind: list | view | people | filter }), caps and send window. Templates use Sergio's merge tags ({{Client First Name}}, {{User Company}}, {{Offer}}, {{O","read_only":false},{"name":"edit_campaign","title":"Edit, pause or archive a campaign","description":"Edits a campaign as its builder does (the fields you pass change; the rest stay), or pauses (status paused, pulls back its queued sends) or archives it. Turning automatic sending off (auto_send false) is open. To start or resume one, use start_campaign (your person confirms first). Held for the owner, refused with where: starting it here, turning automatic sending on, and changing the messages, au","read_only":false},{"name":"delete_campaign","title":"Delete a campaign","description":"Deletes a campaign as Delete on its card does: its queued messages are pulled back first; messages already sent stay in their threads. It cannot be undone; to stop it for now, edit_campaign with status paused. Pass the same idempotency_key when retrying.","read_only":false},{"name":"start_campaign","title":"Start a campaign (after your person confirms)","description":"Starts a draft or paused campaign on your person's order, as Start campaign does: it enrolls the people waiting and drafts their first message; starting sends nothing by itself. First call without confirm_token: nothing changes; you get a preview (every message's exact words, how many people it reaches now, the audience rules, and whether the business's Sending lets a person's messages go out) and","read_only":false},{"name":"send_campaign_messages","title":"Send a campaign's ready messages (after your person confirms)","description":"Sends a started campaign's drafted messages that are ready, on your person's order, as Send in its Ready to send does, as Manual sends under the business's Sending setting, spread over the campaign's send window. First call without confirm_token: nothing is sent; you get a preview (each person and the exact finished text they get, up to 50 at a time) and a confirm_token. Show your person the previ","read_only":false},{"name":"start_history_import","title":"Import message history from a connected inbox","description":"Starts importing the past messages of a connected inbox into Sergio, as Import history on Data sources does: source openphone (Quo) or gmail, or transcripts; days back (default 90). The account must already be connected (connecting is the owner's, in Settings). A second start while one is running returns that job; it carries on in the background. Nothing is sent. Pass the same idempotency_key when","read_only":false},{"name":"cancel_import","title":"Cancel a running import","description":"Cancels a running import (message history or a spreadsheet), as Cancel in the import drawer does; what it already brought in stays. job_id comes from start_history_import or the import list. Pass the same idempotency_key when retrying.","read_only":false},{"name":"record_tools_access","title":"Record the business's other tools","description":"Records the tools the business uses today and whether Serviche was given access to each, as Get started's Your tools step does: action pick (tools: [{ id } or { name }]), none, mark (tool, provided, note) or unmark (tool). Nothing leaves Sergio. Pass the same idempotency_key when retrying. An owner-level change: Sergio tells the owner after it is made.","read_only":false},{"name":"declare_lead_sources","title":"Say where leads come from","description":"Records where the business gets its leads (keys from the setup guide list, for example thumbtack, google_lsa, yelp, website, other; other needs its words), as Get started's lead sources step does. An answer only: it opens and sends nothing. Pass the same idempotency_key when retrying. An owner-level change: Sergio tells the owner after it is made.","read_only":false},{"name":"approve_follow_up_style","title":"Approve the lead journeys drafted from follow-up answers","description":"Records the owner's approval of the lead journeys drafted from how the business follows up today, as Get started's follow-up step does. The journeys must already be saved as the answers draw them (answers: firstChannel, speed, followUpChannel, tries, overDays, giveUpDays; sources: the journeys approved, as lead sources such as site_thumbtack or web_form; Get started's lead sources map to them). Sa","read_only":false},{"name":"set_flow_archived","title":"Archive or un-archive a flow","description":"Archives a flow as its Archive on the Automations page does (archived true): it leaves the flow pickers and the router but is kept, and runs in progress are unaffected. archived false un-archives it. flow_id comes from read('flows'); archive several by calling once per flow. Pass the same idempotency_key when retrying.","read_only":false},{"name":"set_flow_on","title":"Turn a flow on or off","description":"Turns a flow on or off, as its On switch on the Automations page does. Turning it on runs the same publish check (a refusal says what is missing); turning it off ends its runs in progress. flow_id comes from read('flows'). Pass the same idempotency_key when retrying.","read_only":false},{"name":"edit_flow","title":"Rename a flow or change its description","description":"Changes a flow's name or description, as its editor on the Automations page does. Send only what changes. Its steps and how it starts are set in the editor (how it starts: set_flow_start). flow_id comes from read('flows'). Pass the same idempotency_key when retrying.","read_only":false},{"name":"set_staff_availability","title":"Set a field worker's availability for a date","description":"Sets one field worker's availability for a date, or a date range (end_date, up to 92 days): a day off (day_off: true), one shift (available_from + available_until, HH:MM), or split shifts (windows). It replaces that day's override; hours equal to the weekly default clear it. Nothing is sent to anyone. Returns the override ids and any booking conflicts the change creates, for a person to resolve. P","read_only":false},{"name":"create_task","title":"Create a task","description":"Adds a task to the team's work queue, optionally tied to a client or conversation and due at a time (ISO 8601). Pass the same idempotency_key when retrying; a repeat returns the original task.","read_only":false},{"name":"complete_task","title":"Complete a task","description":"Marks a task done, recorded as completed by this seat. A flow-step task also completes its step, as the check box does. Pass the same idempotency_key when retrying; a repeat returns the task, reports what the original call applied, and changes nothing if the task changed since.","read_only":false},{"name":"skip_task","title":"Dismiss a task as not needed","description":"Dismisses a task as not needed (terminal, distinct from done). A client check-in needs a skip_reason. Pass the same idempotency_key when retrying; a repeat returns the task, reports what the original call applied, and changes nothing if the task changed since.","read_only":false},{"name":"reopen_task","title":"Reopen a task","description":"Reopens a done or dismissed task, clearing its completion. reopen_reason says briefly why (required, it rides the audit row). A lead follow-up (pursuit) task is refused: reopening it can queue a message, so a person does it. Pass the same idempotency_key when retrying; a repeat returns the task, reports what the original call applied, and changes nothing if the task changed since.","read_only":false},{"name":"snooze_task","title":"Move a task's due time","description":"Moves a task's due time (ISO 8601 with offset). A flow-step task shifts its later steps by the same gap, as in the app. Pass the same idempotency_key when retrying; a repeat returns the task, reports what the original call applied, and changes nothing if the task changed since.","read_only":false},{"name":"assign_task","title":"Assign a task","description":"Assigns a task to a team member (their member id from read('team_members') or whoami), or unassigns it with null. Pass the same idempotency_key when retrying; a repeat returns the task, reports what the original call applied, and changes nothing if the task changed since.","read_only":false},{"name":"update_task","title":"Edit a task","description":"Edits a task as a person can on its row: title, description (details), due_date (ISO 8601 with offset, or null to clear), priority, client_id or conversation_id (null unlinks). Send only the fields to change. A flow-step task shifts its later steps when its due time moves, as in the app. Pass the same idempotency_key when retrying; a repeat returns the task, reports what the original call applied,","read_only":false},{"name":"delete_task","title":"Delete a task","description":"Deletes a task outright, as the task menu's Delete does. It cannot be undone; to say a task is not needed, use skip_task instead. Deleting a Scanner's task tells that Scanner it was wrong. Pass the same idempotency_key when retrying; a repeat returns the first delete's answer.","read_only":false}],"server_info":{"name":"sergio","title":"Sergio","version":"1.0.2","websiteUrl":"https://sergio.serviche.com","icons":[{"src":"https://sergio.serviche.com/brand/sergio-app-icon-192.png","mimeType":"image/png","sizes":["192x192"]},{"src":"https://sergio.serviche.com/brand/sergio-app-icon-512.png","mimeType":"image/png","sizes":["512x512"]}]},"category":"productivity","tags":["sales","marketing","data"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-11-07","stars":0,"badges":["new"],"sponsor":null,"page":"https://agentsindex.org/agents/com-serviche-sergio/"}