Local services & SaaS
Setmore
Bookings, customers and staff calendars in your Setmore account.
15 endpoints
GoReminders has a REST API for appointments and customers, but none for blasts, two-way texts, templates or booking requests, and no MCP server (checked 13 Nov 2026). Cotlet runs a hosted GoReminders MCP server with 15 tools that ChatGPT and Claude use in your own account. Every text, blast and booking change waits for your OK.
15 tools Read and write
GoReminders publishes a REST API at api.goreminders.com/api/v1 with an OpenAPI reference. It creates, edits and deletes appointments, customers, staff, services, locations and labels, reads messages and sets up webhooks. It has no endpoints for blasts, sending texts, templates, sequences or booking requests, and no GoReminders MCP server was verified.
| What you need | GoReminders API | By hand | Cotlet |
|---|---|---|---|
| Ask ChatGPT or Claude to do the work | No MCP server verified | Copy and paste | Hosted MCP server |
| Appointments and customers | Create, edit, delete | One at a time | Same, after your OK |
| Blasts, texts with pay links, booking requests | No endpoints | Messages and Booking tabs | 15 tools, writes after your OK |
| Run from n8n or a script | Your own code, basic auth | Manual only | REST, same key |
Checked 13 Nov 2026. Sources: GoReminders API docs · GoReminders API reference · Help: API & Documentation · GoReminders integrations · Help: How to Manage Add-Ons · Help: Confirmation and reschedule notices · Help: Manually confirm, reschedule or cancel · Help: Approve a Booking Request · Help: Send a Message Blast · Help: Payments without appointments · Help: Message Sequences · Help: Follow-Up Messages · Help: Mark an appointment as a no-show · Help: Group appointments
Once, in a browser we host for you.
One address in its settings.
It drafts the answers, you approve the texts.
Your agent works in your own signed-in Cloud Browser. Texts, blasts and anything your clients see wait for your OK. Who can see your session
Sign in to GoReminders in a Cloud Browser. Open goreminders.com/login in your Cotlet Cloud Browser and log in with your own GoReminders account.
Add the Cotlet address. Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent.
Let the agent in. Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console.
GoReminders runs on the shared address https://cotlet.dev/mcp/v1, next to every other app you turn on, so one connector serves them all. Turned GoReminders on after connecting? Refresh the connector and the 15 GoReminders tools show up.
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY" // ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
} # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY" MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: goreminders_read One tool per owner workflow in the GoReminders Help Center, with the articles of one workflow merged. Tools with an `action` only read on `list` and `get`; the other actions write and ask first.
The appointments your reminders run on. Saving or moving one schedules reminders by itself.
Returns appointments in calendar order with customer, service, staff, location, label and status. GoReminders shows a yellow checkmark when the client confirmed, a red exclamation mark for a reschedule request and a black one for a cancel; this tool returns those as `status`. Nothing is changed.
MCP callgoreminders_read → list_appointments
REST endpointGET https://cotlet.dev/api/v1/goreminders/appointments
| Name | Type | Description |
|---|---|---|
| from string | string | ISO date to start from. Defaults to today. |
| to string | string | ISO date to end on. Defaults to seven days after `from`. |
| status string | string | Optional filter: `confirmed`, `reschedule_requested`, `canceled` or `no_reply`. |
{
"from": "2026-11-14",
"to": "2026-11-14",
"appointments": [
{
"time": "09:00",
"customer": "Example Client",
"service": "Deep tissue, 60 min",
"staff": "Jordan",
"status": "confirmed"
},
{
"time": "11:00",
"customer": "Sample Customer",
"service": "Swedish, 90 min",
"staff": "Jordan",
"status": "reschedule_requested"
},
{
"time": "14:00",
"customer": "Demo Guest",
"service": "Deep tissue, 60 min",
"staff": "Alex",
"status": "no_reply"
}
]
} Saving the appointment schedules its reminders by itself, so it reaches the client. A group appointment holds up to 100 clients and counts each one toward your monthly appointment limit; an appointment with reminder type `none` does not count. Each repeat of a recurring series gets its own reminders. By default you confirm each call; you can switch that off for this tool.
MCP callgoreminders_write → create_appointment
REST endpointPOST https://cotlet.dev/api/v1/goreminders/appointments
| Name | Type | Description |
|---|---|---|
| customer string required | string | Customer name, or a customer group for a group appointment. A new name is saved to your customer list. |
| start string required | string | ISO date and time. GoReminders accepts it up to 1 minute before the start. |
| length_minutes number | number | Defaults to the service or account default length. |
| reminder_type string | string | `text`, `email`, `both` or `none`. `none` blocks off time and sends nothing. |
| messages string | string | Message template or message sequence name. Defaults to the Main Template. |
| service string | string | Service from Settings > Services. |
| staff string | string | Staff member from Settings > Staff. |
| location string | string | Location from Settings > Locations. |
| repeat string | string | Optional: frequency for a recurring series, for example `weekly`. |
| repeat_times number | number | Optional: number of times to repeat. |
| notes string | string | Internal notes, never shown to the client. |
{
"customer": "Example Client",
"start": "2026-11-21T09:00",
"service": "Deep tissue, 60 min",
"staff": "Jordan",
"reminder_type": "text",
"messages": "Two-day and same-day",
"repeat": "weekly",
"repeat_times": 4
} {
"customer": "Example Client",
"start": "2026-11-21T09:00",
"service": "Deep tissue, 60 min",
"staff": "Jordan",
"messages": "Two-day and same-day",
"reminder_type": "text",
"repeat": "weekly",
"repeat_times": 4,
"saved": true
} A new date or time sends a new reminder on your reminder schedule. A label such as No-show is internal; a label set to stop reminders and follow-ups stops them for that appointment. A deleted appointment cannot be brought back by the agent. By default you confirm each call; you can switch that off for this tool.
MCP callgoreminders_write → update_appointment
REST endpointPATCH https://cotlet.dev/api/v1/goreminders/appointment
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `update`, `add_customer`, `remove_customer`, `delete`. `list` and `get` only read. |
| appointment string required | string | Customer and start time of the appointment, as list_appointments returns it. |
| fields object | object | For `update`: start, length_minutes, service, staff, location, label or notes. |
| customer string | string | For `add_customer` and `remove_customer` on a group appointment. |
{
"action": "action",
"appointment": "appointment"
} {
"appointment": "Sample Customer, 2026-11-14 11:00",
"start": "2026-11-15T10:00",
"new_reminder": true,
"saved": true
} The same status a client sets by replying C, R or X. GoReminders sends the client no notice when you change it by hand. Canceled stops the remaining reminders, and every appointment still counts toward your monthly limit whatever its status. By default you confirm each call; you can switch that off for this tool.
MCP callgoreminders_write → set_appointment_status
REST endpointPUT https://cotlet.dev/api/v1/goreminders/appointment-status
| Name | Type | Description |
|---|---|---|
| appointment string required | string | Customer and start time, as list_appointments returns it. |
| status string required | string | One of `confirmed`, `reschedule_requested`, `canceled`. |
{
"appointment": "appointment",
"status": "status"
} {
"appointment": "Demo Guest, 2026-11-14 14:00",
"status": "confirmed",
"saved": true
} Replies, one-to-one texts with pay or file links, and blasts to groups. Sending needs the matching add-on.
Newest first. Use it each morning to find reschedule requests and questions that need an answer. It changes nothing and runs without asking.
MCP callgoreminders_read → list_messages
REST endpointGET https://cotlet.dev/api/v1/goreminders/messages
| Name | Type | Description |
|---|---|---|
| customer string | string | Only messages with this customer. |
| replies_only boolean | boolean | Only replies from customers, including C, R and X answers to reminders. |
| since string | string | ISO date and time; only newer messages. |
{
"messages": [
{
"customer": "Sample Customer",
"at": "2026-11-13T18:42",
"direction": "in",
"text": "R"
},
{
"customer": "Example Client",
"at": "2026-11-13T17:05",
"direction": "in",
"text": "C"
}
]
} Two-way messaging is a GoReminders add-on. A pay link needs payment processing set up in GoReminders. The message goes out from your dedicated GoReminders number or email and cannot be recalled. By default you confirm each call; you can switch that off for this tool.
MCP callgoreminders_write → send_message
REST endpointPOST https://cotlet.dev/api/v1/goreminders/messages
| Name | Type | Description |
|---|---|---|
| customer string required | string | Existing customer, or a new name with a phone or email. |
| text string required | string | The message. |
| pay_amount number | number | Optional: adds a pay link for this amount (Add Pay Link). |
| invoice_label string | string | With `pay_amount`: the Invoice Label the client sees. |
| file string | string | Optional: a file from manage_files to share as a link. |
{
"customer": "customer",
"text": "text"
} {
"customer": "Sample Customer",
"text": "No problem, would Saturday at 10 work? Deposit link below.",
"pay_link": {
"amount": 40,
"invoice_label": "Deposit, Swedish 90 min"
},
"sent": true
} Message Blasts are an add-on, and GoReminders asks for some business information before the first one. Recipients do not see each other, and they can reply as they do to reminders. `preview` returns the blast as it will go out; `send` reaches every recipient at once. By default you confirm each call; you can switch that off for this tool.
MCP callgoreminders_write → send_message_blast
REST endpointPOST https://cotlet.dev/api/v1/goreminders/message-blasts
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `preview`, `send`. `list` and `get` only read. |
| name string | string | Blast Name, for `preview` and `send`. |
| send_to string | string | Customer group or customers. |
| text string | string | Text version of the message. |
| email string | string | Email version; defaults to the text. |
| duplicate_of string | string | Optional: a previous blast to copy, as Duplicate does. |
{
"action": "action"
} {
"blasts": [
{
"name": "Holiday gift cards",
"sent_to": "Monthly members",
"recipients": 42,
"replies": 7
},
{
"name": "December hours",
"sent_to": "All customers",
"recipients": 318,
"replies": 12
},
{
"name": "New hot stone service",
"sent_to": "Monthly members",
"recipients": 42,
"replies": 9
}
]
} Files are private by default. `share` makes a public link anyone with it can open; send it with send_message. By default you confirm each call; you can switch that off for this tool.
MCP callgoreminders_write → manage_files
REST endpointPOST https://cotlet.dev/api/v1/goreminders/files/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `upload`, `share`. `list` and `get` only read. |
| appointment string | string | Appointment to attach to. |
| customer string | string | Customer to attach to, without an appointment. |
| file_url string | string | For `upload`: a link the Cloud Browser can download the file from. |
| file string | string | For `share`: the file to share. |
{
"action": "action"
} {
"customer": "Example Client",
"file": "Intake form.pdf",
"share_link": "https://files.example.com/s/abc123",
"shared": true
} What reminders say and when they go out, including follow-ups after the visit.
Every future reminder that uses the template carries the change, so edits wait for your OK. GoReminders adds the reply C, R or X instructions to reminders unless you turned them off in Settings > Reminders. Trial accounts cannot put links in templates until GoReminders approves them. By default you confirm each call; you can switch that off for this tool.
MCP callgoreminders_write → manage_message_templates
REST endpointPOST https://cotlet.dev/api/v1/goreminders/message-templates/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`, `update`, `delete`. `list` and `get` only read. |
| template string | string | Template name; `Main Template` is the default. |
| sms string | string | SMS/Text version, with template tags such as {{First Name}}, {{Day Name}}, {{Date}}, {{Time}}, {{Service}}, {{Location}} or {{Booking Link}}. |
| email string | string | Email version. |
| new_name string | string | For `update`: rename the template. |
{
"action": "action"
} {
"template": "Two-day reminder",
"sms": "Hi {{First Name}}, see you {{Day Name}}, {{Date}} at {{Time}} for your {{Service}}.",
"saved": true
} Follow-up messages are an add-on; they suit review requests and rebooking nudges, and never carry the confirm or reschedule instructions. A deleted sequence cannot be undone. By default you confirm each call; you can switch that off for this tool.
MCP callgoreminders_write → manage_message_sequences
REST endpointPOST https://cotlet.dev/api/v1/goreminders/message-sequences/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `update`, `delete`. `list` and `get` only read. |
| sequence string | string | Sequence Name, the one you pick in the Message(s) field of an appointment. |
| reminders array | array | For `create` and `update`: each reminder's schedule (immediately, or a number of hours or days before) and its message template. |
| follow_ups array | array | Optional: up to two follow-up messages, each with a template and a delay from 1 hour to 3 years after the appointment. |
{
"action": "action"
} {
"sequence": "Two-day and same-day",
"reminders": [
{
"when": "2 days before",
"template": "Two-day reminder"
},
{
"when": "3 hours before",
"template": "Same-day reminder"
}
],
"follow_ups": [
{
"when": "1 day after",
"template": "Review request"
}
],
"saved": true
} Requests clients send through your Booking Form, and the form's hours, style and links.
Requests come in when your Booking Style is Appointment Request. `list` returns each customer with the times they asked for. `confirm` picks one, saves the appointment and starts its reminders, so the client hears from you. By default you confirm each call; you can switch that off for this tool.
MCP callgoreminders_write → manage_booking_requests
REST endpointPOST https://cotlet.dev/api/v1/goreminders/booking-requests/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `confirm`. `list` and `get` only read. |
| customer string | string | For `confirm`: the customer who sent the request. |
| slot string | string | For `confirm`: one of the requested dates and times, ISO. |
| messages string | string | For `confirm`: message template or sequence for the reminders. |
{
"action": "action"
} {
"requests": [
{
"customer": "New Client",
"service": "Swedish, 90 min",
"requested": [
"2026-11-18T10:00",
"2026-11-19T15:00"
]
}
]
} `link` builds the Booking Form URL with the ?date= and prefill parameters GoReminders documents. A length shorter than the time selector interval leaves gaps between bookings. Client Self-Scheduling is an add-on. Hours and style change what every client can book, so `update` waits for your OK. By default you confirm each call; you can switch that off for this tool.
MCP callgoreminders_write → manage_booking_settings
REST endpointPOST https://cotlet.dev/api/v1/goreminders/booking-settings/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `get`, `update`, `link`. `list` and `get` only read. |
| fields object | object | For `update`: booking_enabled, booking_style (`instant_book` or `appointment_request`), open_hours per day with breaks, time_selector_interval and default_length. |
| date string | string | For `link`: optional ISO date and time to preselect. |
| customer string | string | For `link`: optional customer whose name, email and phone are prefilled. |
{
"action": "action"
} {
"booking_enabled": true,
"booking_style": "appointment_request",
"time_selector_interval": 60,
"default_length": 45,
"link": "https://example.goreminders.com/book?date=20261118T1000"
} Customers, groups, and the services, staff, locations and labels appointments use.
`get` also returns the customer's past and upcoming appointments. Setting reminder type to `none` and clearing phone and email is how GoReminders stops a contact from messaging you. A deleted customer cannot be restored. By default you confirm each call; you can switch that off for this tool.
MCP callgoreminders_write → manage_customers
REST endpointPOST https://cotlet.dev/api/v1/goreminders/customers/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `get`, `create`, `update`, `import`, `delete`. `list` and `get` only read. |
| customer string | string | Name, email or phone, for `get`, `update` and `delete`. |
| fields object | object | For `create` and `update`: name (required on create), email, phone, time_zone, reminder_type (`email`, `text`, `both`, `none`), notes and your custom fields. |
| csv_url string | string | For `import`: a CSV with the headers First Name, Last Name, Email, Phone. |
| group string | string | For `import`: optional customer group to import into. |
{
"action": "action"
} {
"customer": "Example Client",
"email": "client@example.com",
"phone": "+1 555 0100",
"reminder_type": "text",
"upcoming": 2,
"past": 9
} Groups are what group appointments and message blasts are sent to. Changing a group reaches no one by itself, but the next blast to it does. By default you confirm each call; you can switch that off for this tool.
MCP callgoreminders_write → manage_customer_groups
REST endpointPOST https://cotlet.dev/api/v1/goreminders/customer-groups/manage
| Name | Type | Description |
|---|---|---|
| action string required | string | One of `list`, `create`, `add`, `remove`. `list` and `get` only read. |
| group string | string | Group name. |
| customers array | array | For `create`, `add` and `remove`: customer names. |
{
"action": "action"
} {
"group": "Monthly members",
"customers": 42,
"saved": true
} Services and staff can show on your Booking Form, and their template tags reach clients in reminders. Labels are internal only. By default you confirm each call; you can switch that off for this tool.
MCP callgoreminders_write → manage_setup_items
REST endpointPOST https://cotlet.dev/api/v1/goreminders/setup-items/manage
| Name | Type | Description |
|---|---|---|
| kind string required | string | One of `service`, `staff`, `location`, `label`. |
| action string required | string | One of `list`, `create`, `update`, `delete`. `list` and `get` only read. |
| name string | string | Name of the item. |
| fields object | object | Service: default length. Staff: email, phone and whether confirmation notices and SMS replies are forwarded to them. Location: internal label and the text clients see. Label: whether it stops reminders and follow-ups. |
{
"kind": "kind",
"action": "action"
} {
"kind": "service",
"name": "Hot stone, 75 min",
"fields": {
"default_length": 75
},
"saved": true
} Your logged-in GoReminders browser profile, AES-256-GCM encrypted, in Finland. Never your password.
The 15 GoReminders tools. The session cookie stays in the Cloud Browser.
What your GoReminders login sees. A team login with limited permissions gives the agent the same limits.
Billing, add-ons, the monthly appointment limit, payment processing setup, team users and API users.
You log in again yourself, in the same Cloud Browser.
Disable GoReminders for agents, reset the browser, or change your GoReminders password.
You type your GoReminders password yourself; the agent only uses the session that login leaves. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results).
When GoReminders moves a button or renames a settings page, Cotlet updates the GoReminders server, and your prompts and REST calls keep working as they are.
Add-ons decide what the agent can do: with Message Blasts or 2-Way Messaging removed on your Billing page, those tools have nothing to send with.
If GoReminders logs you out, one click in the Cotlet console reopens the Cloud Browser so you can log in again.
| Action | How to put it right |
|---|---|
| Appointment moved or status set | Call update_appointment or set_appointment_status again with the earlier values; a moved time sends a new reminder |
| Template or sequence edited | Save the earlier text with manage_message_templates; a deleted sequence cannot be undone |
| Text or blast sent | Already with your clients: send a correction |
| Customer or appointment deleted | GoReminders cannot restore it; create it again |
13 of the 15 tools ask first: by default you confirm each call, and you can switch that off per tool. list_appointments and list_messages only read and run at once.
{
"name": "create_appointment",
"arguments": {
"customer": "Example Client",
"start": "2026-11-21T09:00",
"service": "Deep tissue, 60 min",
"staff": "Jordan",
"reminder_type": "text",
"messages": "Two-day and same-day",
"repeat": "weekly",
"repeat_times": 4
}
} curl -X POST https://cotlet.dev/api/v1/goreminders/appointments \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"customer":"Example Client","start":"2026-11-21T09:00","service":"Deep tissue, 60 min","staff":"Jordan","reminder_type":"text","messages":"Two-day and same-day","repeat":"weekly","repeat_times":4}' {
"customer": "Example Client",
"start": "2026-11-21T09:00",
"service": "Deep tissue, 60 min",
"staff": "Jordan",
"messages": "Two-day and same-day",
"reminder_type": "text",
"repeat": "weekly",
"repeat_times": 4,
"saved": true
} The example books four weekly deep tissue sessions with the Two-day and same-day sequence; each one counts toward your monthly appointment limit. A cron job or n8n flow can make the same call over REST at /api/v1/goreminders with the same key and price, in JSON. Failed calls are free.
About $23 a monthfor a small studio with a busy inbox, 4,000 credits. Your GoReminders plan and add-ons stay as they are.
| Job | Calls | Credits |
|---|---|---|
| Morning replies: read, offer a time, move | 5 × 20 | 1,000 |
| Booking requests checked and confirmed | 2 × 20 | 400 |
| Appointments entered from calls | 1 × 40 | 400 |
| No-show labels at closing | 1 × 20 | 200 |
| Statuses set by hand | 1 × 20 | 200 |
| Deposit texts with a pay link | 1 × 22 | 220 |
| Blast preview and send | 2 × 4 | 80 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 250 calls | 4,000 |
The smallest pack, 5,000 credits for $29, covers this month. More staff and more replies mean more calls.
Credit packs are one-time purchases, not a subscription. The month above is our own example, not measured customer usage.
| Credits | Price, one time | Calls at 10 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 500 | $5.80 |
| 15,000 | $79 | 1,500 | $5.27 |
| 32,000 | $149 | 3,200 | $4.66 |
| 60,000 | $249 | 6,000 | $4.15 |
Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.
| Option | What it does | Where it stops |
|---|---|---|
| GoReminders API | Appointments, customers, staff, services, locations, labels, reading messages, webhooks. | No blasts, sending texts, templates, sequences or booking requests; you write and host the code. |
| Zapier app | Moves GoReminders data to and from other apps on triggers. | No agent decides or writes anything in GoReminders. |
| Calendar feeds | Shows GoReminders appointments in Google Calendar, Outlook or iPhone. | One way: GoReminders does not import from outside calendars. |
| By hand | Work the Messages, Booking and Calendar tabs yourself. | Only while someone is at the desk. |
If you only need appointments or customers in sync with other software, the GoReminders API does that and costs nothing extra: use it. Cotlet fits when ChatGPT, Claude or a script should also answer texts, send blasts, edit reminders or confirm booking requests, with nothing to host.
Cotlet belongs to Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273), in business since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the GoReminders tools go to contact@cotlet.dev.
Sign up free at https://cotlet.dev/signup?app=goreminders, turn on GoReminders under Integrations in the console and log in at https://www.goreminders.com/login in your Cloud Browser. Then connect your AI agent and ask it about tomorrow's appointments. The trial needs no card.
GoReminders has a REST API at api.goreminders.com/api/v1 for appointments, customers, staff, services, locations, labels, reading messages and webhooks; you create an API user under Settings > Integrations > GoReminders API, and appointment creates and edits are capped at 200% of your plan's monthly appointment limit (checked 13 Nov 2026). It has no endpoints for message blasts, sending two-way texts, templates, sequences or booking requests, and no GoReminders MCP server was verified. Cotlet does not use that API: it works in your own signed-in GoReminders account.
Yes. They are ordinary GoReminders appointments: each one counts, a group appointment counts once per client in it, and status does not change that. An appointment with reminder type None, used to block off time, does not count.
The tools use what your account has. GoReminders sells 2-Way Messaging, Message Blasts, Follow-Up Messages, Client Self-Scheduling and Reviews as add-ons on the Billing page, so send_message, send_message_blast, follow-ups in manage_message_sequences and booking requests work only with the matching add-on.
The ones GoReminders sends SMS to. Its help center lists the United States, Canada, United Kingdom, Australia, Hong Kong, Czechia, Denmark, Estonia, Latvia, Lithuania and the Netherlands. Texts go out from your dedicated GoReminders number.
Only in how it is called. Both carry the same 15 tools, inputs, answers, API key and price. Agents use MCP; scripts and n8n HTTP steps use REST. This is Cotlet's REST API, not the GoReminders API.
No. Cotlet is independent and not affiliated with GoReminders.
Free 7-day trial with 2,000 credits, no card needed.
May we use Google Analytics to see which pages help people? It sets cookies only if you accept. No ads, and we never sell data. Cookie policy