Integration
Connect LawPay to Pdforge
When New Event fires in LawPay, your agent runs Add template in Pdforge. Describe the whole flow 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 LawPay and Pdforge to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any 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 LawPay can start in Pdforge
When New Event in LawPay
then Add template in Pdforge
When New Transaction in LawPay
then Update PDF metadata in Pdforge
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 LawPay and Pdforge
Triggers and actions 2 triggers · 25 actions
Trigger
New EventTriggers when a new LawPay gateway event occurs, such as a transaction being authorized or completed.
Trigger
New TransactionTriggers when a new charge, refund or credit is created in LawPay.
Action
Cancel Recurring ChargeCancels a LawPay recurring charge so no further payments are collected.
Action
Capture ChargeCaptures an authorization-only LawPay card charge so its funds settle.
Action
Create ChargeCharges a customer in LawPay using a saved payment method or a one-time payment token.
Action
Create CreditSends funds to a customer's card or bank account in LawPay without an original charge (the Credit feature must be enabled on the account).
Action
Get Current MerchantReturns the LawPay merchant tied to the secret key, including its operating, trust and eCheck accounts.
Action
Get EventReturns one LawPay gateway event, such as a transaction being authorized, with its data.
Action
Get Recurring ChargeReturns a LawPay recurring charge with its schedule, totals and next payment date.
Action
Get TransactionReturns one LawPay charge, refund or credit by its ID, including any refunds applied to a charge.
Action
List Recurring Charge OccurrencesReturns the scheduled payments of a LawPay recurring charge with their due dates and status.
Action
Refund ChargeRefunds part or all of a LawPay charge back to the original card or bank account.
Action
Search TransactionsReturns LawPay transactions matching a text search, date range or account, newest first.
Action
Void TransactionVoids a LawPay charge, refund or credit that has not been captured yet, releasing any hold.
Action
Add templateStarts AI creation of a new PDF template from a text prompt (and optional reference file). Creation runs asynchronously and usually takes a couple of minutes; the returned template id can be used to check its status.
Action
Compress PDFCompresses a PDF from a public URL to reduce its file size, returning a signed download URL for the compressed file.
Action
Convert HTML to PDFConverts HTML into a PDF (or PNG) synchronously and returns a temporary signed URL to the generated file. If rendering takes longer than 30 seconds, the job is queued and a request id and status URL are returned instead.
Action
Convert Markdown to PDFConvert Markdown text (headings, lists, tables, code blocks) into a styled PDF document.
Action
Generate PDF from templateGenerates a PDF (or PNG) from one of your PDF Noodle templates and waits for it to finish, returning a temporary download link.
Action
Get PDF statusRetrieve the status of a single PDF generation request, and its download link once rendering succeeds.
Action
Get templateRetrieves a template's full details, or its creation status if it is still being created with AI.
Action
Get template variablesRetrieves the variable schema for a template: every data placeholder (including nested objects and arrays) that can be supplied when generating a PDF from it.
Action
Get tool statusRetrieve the status of a PDF tool operation (merge, split, compress, markdown to PDF, metadata update) using the request id returned by an async request or a synchronous request that timed out.
Action
List templatesLists every template available in your pdf noodle account, with each template's id and display name.
Action
Merge PDFsCombine two or more publicly accessible PDF files into a single PDF, merged in the order given. Returns a temporary download link to the merged file, or a request id to check later when the merge runs in the background.
Action
Split PDFSplit a single PDF into multiple smaller PDFs by page ranges or regular intervals.
Action
Update PDF metadataUpdates the embedded metadata (title, author, subject, keywords and more) of a PDF at a public URL and returns a link to the updated file. The original PDF content is preserved.
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 LawPay
LawPay to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
LawPay to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
LawPay to MailchimpMailchimp marketing automation and email platform.
LawPay to StripeStripe is a payment processing platform for online businesses.
LawPay to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
LawPay to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Pdforge
Clockify to PdforgeClockify is a completely free time tracking software for teams.
HubSpot to PdforgeHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to PdforgeSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to PdforgeSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to PdforgeGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to PdforgeGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
LawPay and Pdforge, answered
What can start an automation from LawPay?
Any of LawPay's 2 triggers in the catalog, including New Event and New Transaction. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Pdforge when something happens in LawPay?
Any of Pdforge's 13 actions, including Update PDF metadata, Add template, Compress PDF and Convert HTML to PDF. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Pdforge to LawPay?
Pdforge has no triggers in the catalog today, so automations start in LawPay. If you need the other direction, ask: your agent reads Pdforge's API documentation and adds it.
Do I have to build a connector for LawPay or Pdforge?
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.
Can my AI client use LawPay and Pdforge without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
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.