Integration
Connect LawPay and OneSignal
When New Event fires in LawPay, your agent runs Add custom event in OneSignal, or New Notification Created in OneSignal to Get Event in LawPay. 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 OneSignal 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 and OneSignal can do together
From LawPay to OneSignal
When New Event in LawPay
then Add custom event in OneSignal
From OneSignal to LawPay
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 OneSignal
Triggers and actions 3 triggers · 28 actions
- New Event
Triggers when a new LawPay gateway event occurs, such as a transaction being authorized or completed.
- New Transaction
Triggers when a new charge, refund or credit is created in LawPay.
- Cancel Recurring Charge
Cancels a LawPay recurring charge so no further payments are collected.
- Capture Charge
Captures an authorization-only LawPay card charge so its funds settle.
- Create Charge
Charges a customer in LawPay using a saved payment method or a one-time payment token.
- Create Credit
Sends funds to a customer's card or bank account in LawPay without an original charge (the Credit feature must be enabled on the account).
- Get Current Merchant
Returns the LawPay merchant tied to the secret key, including its operating, trust and eCheck accounts.
- Get Event
Returns one LawPay gateway event, such as a transaction being authorized, with its data.
- Get Recurring Charge
Returns a LawPay recurring charge with its schedule, totals and next payment date.
- Get Transaction
Returns one LawPay charge, refund or credit by its ID, including any refunds applied to a charge.
- List Recurring Charge Occurrences
Returns the scheduled payments of a LawPay recurring charge with their due dates and status.
- Refund Charge
Refunds part or all of a LawPay charge back to the original card or bank account.
- Search Transactions
Returns LawPay transactions matching a text search, date range or account, newest first.
- Void Transaction
Voids a LawPay charge, refund or credit that has not been captured yet, releasing any hold.
- New Notification Created
Triggers when a new message (push, email or SMS) is created in your OneSignal app.
- Add custom event
Records a custom event, such as a purchase or milestone, against a OneSignal user identified by External ID or OneSignal ID.
- Add segment
Creates a segment in your OneSignal app from a set of audience filters.
- Add subscription
Adds a new email, SMS or push subscription to an existing OneSignal user, found by one of the user's aliases such as their External ID.
- Add user
Creates a OneSignal user identified by an External ID, with optional tags, profile properties and subscriptions. If the External ID already exists, the user's subscriptions are updated instead.
- Delete notification
Cancels a scheduled or currently sending OneSignal message so it stops going out.
- Delete segment
Deletes a segment from your OneSignal app. The users and subscriptions in the segment are not deleted.
- Delete user
Deletes a OneSignal user along with all of their properties, subscriptions and identity aliases.
- Get notification
Returns the details of a single OneSignal message, including its content, delivery statistics and outcomes.
- Get user
Returns a OneSignal user, including their aliases, properties (tags, country, activity dates) and subscriptions.
- List notifications
Returns the push, email and SMS messages sent from your OneSignal app, newest first, with their content and delivery stats.
- List segments
Returns all segments in your OneSignal app, with each segment's name, description, status and dates.
- List templates
Returns the message templates in your OneSignal app, optionally filtered to push, email or SMS templates.
- Send email
Sends an email message through OneSignal to email addresses, users, subscriptions or segments, using your own content or a saved template.
- Send Push Notification
Sends a push notification to your OneSignal app's subscribers, chosen by segment, filters, user alias or subscription ID. Returns the ID of the notification that was created.
- Send SMS
Sends an SMS or MMS text message through OneSignal to phone numbers, users, subscriptions or segments, and returns the new message's ID.
- Update user
Updates a OneSignal user's properties, such as tags, language, timezone, location and country, and records session activity and purchases.
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 OneSignal
HubSpot to OneSignalHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to OneSignalGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to OneSignalGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to OneSignalGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to OneSignalGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Questions
LawPay and OneSignal, 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 OneSignal when something happens in LawPay?
Any of OneSignal's 16 actions, including Send email, Send Push Notification, Send SMS and Update user. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from OneSignal to LawPay?
Yes. When something happens in OneSignal, your agent can act in LawPay too. This page covers both directions: OneSignal's triggers and LawPay's actions are listed here as well.
Do I have to build a connector for LawPay or OneSignal?
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 OneSignal 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.