Integration
Connect Paperless to Tinify.dev
When something happens in Paperless, your agent does the next thing in Tinify.dev. Describe it and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Paperless and Tinify.dev to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Paperless can start in Tinify.dev
When Document updated in Paperless
then Compress image in Tinify.dev
When New document created in Paperless
then Convert image in Tinify.dev
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Paperless and Tinify.dev
Triggers and actions 2 triggers · 9 actions
Trigger
Document updatedFires when a document is updated (e.g. name changed). Backed by the document.updated webhook event.
Trigger
New document createdFires when a new document is created. Backed by the document.created webhook event.
Action
Create Document (From Template)Creates a new Paperless document from an existing template, optionally filling in recipients, form-field defaults and variables, and optionally sending it right away.
Action
Delete DocumentPermanently delete a document by ID.
Action
Get DocumentRetrieves a single Paperless document by its id.
Action
Get TemplateRetrieves a single Paperless template by its id.
Action
List TemplatesList all templates the API key's integration has access to, used to pick a template_id before creating a document.
Action
Update DocumentUpdates an existing Paperless document: rename it, set its recipients, form field defaults and variables, or send it by setting its state to dispatched.
Action
Compress imageCompresses one image with Tinify.dev and returns a download link to the optimized result, valid for two hours. If compression would make the file larger, the original is kept and optimized is false.
Action
Convert imageConverts one image to AVIF, WebP, JPEG or PNG and returns a download link for the converted file (the link expires after two hours).
Action
Resize imageCreate a resized version (scale/fit/cover/thumb) of a previously compressed image. POST to the output URL from a Compress image call with a resize object {method,width,height}; returns the resized, compressed image.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Paperless
Paperless to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Paperless to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Paperless to StripeStripe is a payment processing platform for online businesses.
Paperless to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Paperless to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Paperless to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into Tinify.dev
HubSpot to Tinify.devHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to Tinify.devSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to Tinify.devSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to Tinify.devGoogle Sheets
Gmail to Tinify.devGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Tinify.devGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Paperless and Tinify.dev, answered
What can start an automation from Paperless?
Any of Paperless's 2 triggers in the catalog, including Document updated and New document created. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Tinify.dev when something happens in Paperless?
Any of Tinify.dev's 3 actions, including Compress image, Convert image and Resize image. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Tinify.dev to Paperless?
Tinify.dev has no triggers in the catalog today, so automations start in Paperless. If you need the other direction, ask: your agent reads Tinify.dev's API documentation and adds it.
Do I have to build a connector for Paperless or Tinify.dev?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.