Useful prints, on repeat.

Print on a schedule

Open a saved template and select Automations. The schedule uses the values from the template’s Print form, so set those up first.

Enter a cron expression and choose a time zone, then select Add schedule. For example, 0 7 * * * runs every day at 7:00 in the selected time zone. Review the saved trigger and keep the printer’s companion available when you expect the job.

Let another app trigger a print

On the template’s Automations tab, choose Create webhook. Copy the endpoint, secret, and generated request example before leaving the page. The secret is shown once.

Use the generated request as the reference for sending the template’s input fields. Treat the secret as a password and keep it in your integration’s secret storage. You can manage the resulting trigger from the template.

Connect an AI tool with MCP

Open Settings and find MCP server. Add the displayed server URL to your AI tool and choose Connect. Slipbridge asks you to sign in and approve the requested access.

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 revoke connected clients in Settings.

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

In Settings → Access tokens, create a token for your integration and choose its scopes. 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 token from Settings 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 Print history 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.