Useful prints, on repeat.

Schedule a template or connect the tools you already use to your printer.

In this guide

Print on a schedule

Open a template from Templates and scroll to Automations, below the print controls. Automations print the published version, so publish the template in the studio first.

Fill in the fields under Fill it in the way you want them on every print, then choose Add a schedule. The schedule saves those values and prints with them each time.

Pick how often it repeats: Every day, Weekdays, Weekends, or Once a week on the day you choose. Then set the time. The line above the buttons reads it back, such as “Every weekday at 7:00 AM”, with the time zone and printer. Choose Save schedule.

The time zone starts as your browser’s. To change it, open Advanced. Advanced also has Use a cron expression instead for other days, like Monday, Wednesday, and Friday. Use a fixed minute and hour, * for the day of month and month, and weekday numbers with Sunday as 0. For example, 30 6 * * 1,3,5 prints at 6:30 on those three days.

Keep the printer’s companion running and its computer awake when you expect the print.

Let another app trigger a print

Under the template’s Automations, choose Add a webhook. Slipbridge shows the endpoint, a secret, and a cURL example that sends the values in Fill it in. Copy the secret before you choose I’ve saved it. For your safety, it is shown only once.

The other app sends a POST request with the template’s fields as JSON, and the secret as a Bearer token:

Terminal
curl --request POST \
  --url 'YOUR_WEBHOOK_ENDPOINT' \
  --header 'Authorization: Bearer YOUR_WEBHOOK_SECRET' \
  --header 'Content-Type: application/json' \
  --data '{"title":"Order 1042","table":7}'

Any JSON with the template’s fields works. The example on the template page uses your real endpoint and fields. Treat the secret as a password and keep it in your integration’s secret storage. If the app might retry a request, send an Idempotency-Key header so a retry does not print twice.

Pause, change, or remove

Each schedule and webhook is a row under Automations. Schedules show the next and last print. Webhooks show their endpoint and when they were last used.

Use the switch on a row to pause or resume it. A paused automation keeps its settings and prints nothing. A resumed schedule continues at its next time; prints missed while it was paused are not made up.

The menu on each row has the rest:

  • Change schedule picks a new time, days, or time zone. To update what it prints, also check Also print with the values in Fill it in now.
  • Copy endpoint copies a webhook’s URL.
  • New secret replaces a lost or leaked webhook secret. The new one is shown once. The old one keeps working for 10 more minutes so you can update the app that sends to it.
  • Remove stops it right away, and a removed webhook’s endpoint stops working. Prints it already made stay in Prints.

Connect an AI tool with MCP

Read the complete AI agents and MCP setup guide →

Open Agents and copy the setup message into your agent. It can follow the linked instructions to help you connect. Slipbridge asks you to sign in and approve the requested access in your browser.

A connected agent can manage the same schedules and webhooks. Ask in your own words: “Print my Morning Brief every weekday at 7.” A schedule keeps printing without asking, so your agent should confirm the time, days, time zone, and field values with you first. If it leaves the fields out, the schedule prints the template’s published sample.

ToolWhat it does
list_automationsList schedules and webhooks in plain words, whether each is on or paused, and the next print.
create_schedulePrint a published template at a set time on every day, weekdays, weekends, or chosen days.
update_scheduleChange a schedule’s time, days, time zone, or field values. A paused schedule stays paused.
set_automation_enabledPause or resume a schedule or webhook.
remove_automationRemove a schedule or webhook for good.
create_webhookAdd a webhook and return its endpoint. You make its secret on the template page.
rotate_webhook_secretLink you to the template page to make a new secret. It changes nothing itself.

Webhook secrets never pass through the conversation. A new webhook from your agent has no secret yet, so nothing can print through it. Your agent links you to the template page instead. Find the webhook under Automations, choose New secret, and copy it once. A secret left in chat history could keep printing even after you disconnect the agent.

The production endpoint is https://app.slipbridge.com/mcp. Use the URL shown in your own workspace if you run a different instance. You can review and disconnect connected agents on the Agents page.

You can also create a scoped MCP access token if your tool supports token authentication. Keep it private and give the integration only the permissions it needs.

Use the HTTP API

On the Agents page, under Other ways in, create an access key for your integration and choose what it can do. The available permissions cover print jobs, printers, templates, and device management.

Copy the token when it is created; it is shown only once. Use the workspace API under https://app.slipbridge.com/api/v1. Revoke a key from the Agents page when an integration no longer needs access.

For command-line printing directly from your computer, the Slipbridge CLI works independently of the web API and needs no workspace account for local jobs.

Follow the resulting jobs

Automated prints appear in the same Prints as manual prints. Open a job to inspect its status and destination. The companion must be running to deliver queued web jobs to the printer.

If the job does not arrive, start with the connection troubleshooting guide.