Integration
Connect DecisionRules and PostgreSQL
When New Rules fires in DecisionRules, your agent runs Add Row in PostgreSQL, or New or Updated Row in PostgreSQL to Add folder in DecisionRules. 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 DecisionRules and PostgreSQL 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 DecisionRules and PostgreSQL can do together
From DecisionRules to PostgreSQL
When New Rules in DecisionRules
then Add Row in PostgreSQL
When New Rules in DecisionRules
then Update Row in PostgreSQL
From PostgreSQL to DecisionRules
When New or Updated Row in PostgreSQL
then Add folder in DecisionRules
When New Row in PostgreSQL
then Add rule in DecisionRules
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 DecisionRules and PostgreSQL
Triggers and actions 5 triggers · 16 actions
Trigger
New RulesFires once for each new rule or rule flow added to the DecisionRules space.
Action
Add folderCreate a folder under a node.
Action
Add ruleCreate a rule in a space.
Action
Add rule versionCreate a new version of a rule.
Action
Add tags to ruleAdd tags to a rule.
Action
Delete ruleDelete a rule or rule version.
Action
Get ruleGets the latest version of a rule by its ID or alias, regardless of publication status.
Action
List foldersGet the root folder tree.
Action
List rulesList rules in a space.
Action
Update ruleUpdate a rule version.
Action
Update rule statusPublish/pending/archive a rule version.
Trigger
New or Updated RowTriggers when a new row is added or modified.
Trigger
New or Updated Row (Custom Query)Fires for each new or changed row returned by a SELECT statement you write against the connected PostgreSQL database.
Trigger
New RowTriggers when you add a new row.
Trigger
New TableFires when a new table appears in the connected PostgreSQL database.
Action
Add RowAdds a new row.
Action
Delete RowDelete the rows in a table whose chosen column equals a value.
Action
Find RowFinds a row in a table via a lookup column.
Action
Find Rows via Custom QueryRuns a SELECT statement you write against the connected PostgreSQL database and returns every row it matches.
Action
Find Row via Custom QueryRuns a SELECT statement you write against the connected PostgreSQL database and returns the first row it matches.
Action
Update RowUpdates an existing row.
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 DecisionRules
DecisionRules to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
DecisionRules to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
DecisionRules to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
DecisionRules to Google SheetsGoogle Sheets
DecisionRules to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
DecisionRules to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into PostgreSQL
Form Io to PostgreSQLForm-builder platform that auto-generates REST APIs for form submissions, data validation, and workflow...
Google Sheets to PostgreSQLGoogle Sheets
Google Calendar to PostgreSQLGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to PostgreSQLGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to PostgreSQLMailchimp marketing automation and email platform.
Stripe to PostgreSQLStripe is a payment processing platform for online businesses.
Questions
DecisionRules and PostgreSQL, answered
What can start an automation from DecisionRules?
Any of DecisionRules's 1 trigger in the catalog, including New Rules. Describe the moment in plain language and your agent picks the right one.
What can your agent do in PostgreSQL when something happens in DecisionRules?
Any of PostgreSQL's 6 actions, including Update Row, Add Row, Find Row and Find Rows via Custom Query. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from PostgreSQL to DecisionRules?
Yes. When something happens in PostgreSQL, your agent can act in DecisionRules too. This page covers both directions: PostgreSQL's triggers and DecisionRules's actions are listed here as well.
Do I have to build a connector for DecisionRules or PostgreSQL?
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.