Integration
Connect Consent Kit to Omise
When Consent Updated fires in Consent Kit, your agent runs Add customer in Omise. 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 Consent Kit and Omise 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 Consent Kit can start in Omise
When Consent Updated in Consent Kit
then Add customer in Omise
When New Consent in Consent Kit
then Add charge in Omise
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 Consent Kit and Omise
Triggers and actions 6 triggers · 44 actions
Trigger
Consent AgreedTriggers when a participant agrees to a consent in Consent Kit.
Trigger
Consent DeclinedTriggers when a participant refuses a consent in Consent Kit.
Trigger
Consent UpdatedTriggers when a Consent Kit consent is created or updated.
Trigger
Data LinkedTriggers when new data is linked to a Consent Kit participant.
Trigger
New ConsentTriggers when a participant agrees to or refuses a consent in Consent Kit.
Trigger
Participant CreatedTriggers when a participant is added to a Consent Kit study, with their email and first name.
Action
Create Data LinkLinks data stored at a URL (a recording, notes, a file) to a Consent Kit participant.
Action
Create ParticipantAdds a participant to a Consent Kit study; Consent Kit uses the email to send them the consent form.
Action
Create StudyCreates a new study inside a Consent Kit project.
Action
Delete Data LinkDeletes (unlinks) a data link from its Consent Kit participant.
Action
Delete StudyDeletes a Consent Kit study.
Action
Get ConsentReturns one Consent Kit consent by ID: whether it was agreed or refused, the permissions given, and the participant.
Action
Get PanelReturns one Consent Kit panel by its ID, including how many panellists it has.
Action
Get ParticipantReturns one Consent Kit participant by ID, optionally with their email and first name.
Action
Get ProjectReturns one Consent Kit project by its ID.
Action
Get StudyReturns one Consent Kit study by its ID.
Action
List ConsentsReturns a page of consents in your Consent Kit organisation, optionally only agreed or only refused ones.
Action
List Data LinksReturns a page of the data links in your Consent Kit organisation.
Action
List FieldsReturns the custom field definitions configured for your Consent Kit organisation, used to read panellist properties.
Action
List Panel PanellistsReturns the opted-in panellists of a Consent Kit panel, optionally with their email, name and custom field values.
Action
List PanelsReturns a page of your organisation's Consent Kit panels.
Action
List ParticipantsReturns a page of your organisation's Consent Kit participants, optionally with their email and first name.
Action
List ProjectsReturns a page of your organisation's Consent Kit projects, newest first.
Action
List StudiesReturns a page of your organisation's Consent Kit studies.
Action
Add chargeCreate a charge for an amount/currency against a card, customer, or source.
Action
Add customerCreate a customer, optionally attaching a card via token.
Action
Add recipientCreates a new transfer recipient (individual or corporation) with a destination bank account.
Action
Add refundCreate a refund on a captured charge.
Action
Add sourceCreates a payment source (PromptPay, internet banking, mobile banking, Alipay, installments, TrueMoney and other non-card methods) that can then be charged with Add charge.
Action
Add tokenCreates a single-use card token in Omise using the account's public key. Use the token to create one charge or to attach the card to a customer.
Action
Add transferCreates a transfer from your Omise balance to your own bank account or to a verified third-party recipient.
Action
Delete cardPermanently removes a saved card from an Omise customer.
Action
Delete customerDestroy a customer.
Action
Delete recipientDestroy a recipient.
Action
Get chargeRetrieves a single Omise charge by its ID.
Action
Get customerRetrieve a customer by id.
Action
Get disputeRetrieve a dispute by id.
Action
Get recipientRetrieve a recipient by id.
Action
Get refundRetrieve a refund by id.
Action
Get sourceRetrieve a payment source by id.
Action
Get tokenRetrieves a card token by its ID, including the card it represents and whether it has been used.
Action
Get transferRetrieves a single Omise transfer by its ID.
Action
List cardsReturns the list of cards saved on an Omise customer.
Action
List customersList all customers.
Action
List recipientsList all recipients.
Action
List transfersList all transfers.
Action
Update chargeUpdates the description and/or metadata of an existing Omise charge.
Action
Update customerUpdate a customer's details.
Action
Update disputeUpdate a dispute's message/status.
Action
Update recipientUpdate a recipient's details.
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 Consent Kit
Consent Kit to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Consent Kit to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Consent Kit to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Consent Kit to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Consent Kit to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Consent Kit to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Omise
HubSpot to OmiseHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to OmiseSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to OmiseSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to OmiseGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to OmiseGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to OmiseGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Consent Kit and Omise, answered
What can start an automation from Consent Kit?
Any of Consent Kit's 6 triggers in the catalog, including Consent Updated, New Consent, Participant Created and Consent Agreed. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Omise when something happens in Consent Kit?
Any of Omise's 26 actions, including Update charge, Update customer, Update dispute and Update recipient. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Omise to Consent Kit?
Omise has no triggers in the catalog today, so automations start in Consent Kit. If you need the other direction, ask: your agent reads Omise's API documentation and adds it.
Do I have to build a connector for Consent Kit or Omise?
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 Consent Kit and Omise 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.