--- title: "Peliqan Integration" description: "Peliqan is a data platform combining one-click ETL from 250+ sources, a built-in or bring-your-own data warehouse, SQL and low-code Python transformations and published APIs. Agents sync applications, manage warehouse tables and fields, run pipelines and data apps and publish API endpoints." url: https://flowrunner.ai/integrations/peliqan date_modified: 2026-09-04T19:38:13-07:00 --- # Peliqan [Analytics & Data](https://flowrunner.ai/integrations/category/analytics-data) Peliqan is a data platform combining one-click ETL from 250+ sources, a built-in or bring-your-own data warehouse, SQL and low-code Python transformations and published APIs. Agents sync applications, manage warehouse tables and fields, run pipelines and data apps and publish API endpoints. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 191 actions · API key · available [Peliqan website](https://eu.peliqan.io/) · [Platform Documentation](https://app.eu.peliqan.io/api/redoc/) · Capability data verified 2026-08-27 1. A source system reports that a large number of records were deleted at source overnight 2. List All Pipeline Runs and Get Pipeline Run Log confirm the run completed rather than failing part way 3. Get Database Table Lineage maps the tables, queries, published endpoints, and data apps built on the affected table 4. List Table Runs compares row counts against the previous run, so the size of the change is a number rather than an impression 5. Agent drafts the change set and pauses the affected schedules rather than letting a data app read mid-change 6. Agent posts the lineage, the row delta, and the named consumers to the data owner 7. The data owner decides whether Do Sync Deletes Server runs, because propagating source deletions erases warehouse history ## What This Integration Enables Peliqan makes the opposite bet from a federated query layer. It lands the data, keeps it, and hands you the things built on top: a warehouse of your own or the built-in one, SQL and low-code transformations, published API endpoints, and data apps that run on a schedule. What you get for the extra machinery is history, because the warehouse holds rows the source has since purged, and control, because the transformation is a versioned artifact rather than a query somebody typed. What you take on is the machinery itself. Pipelines fail, tokens expire, schemas drift, and a scheduled app that stops firing does not announce itself. That maintenance surface is the reason to point an agent at this connector. FlowRunner agents read pipeline runs and logs as they complete, compare row counts against the previous run, walk lineage before a change reaches a consumer, and chase an expired OAuth connection back to the person who actually holds the credential. They manage the delivery surface too, publishing an endpoint or scheduling a data app so a result reaches the people who need it. And they stop before the small set of operations that cannot be walked back, because a data platform that quietly loses history is worse than one that occasionally waits for an answer. ### Without FlowRunner **Pipelines watched by whoever notices**: A failed sync is discovered when a dashboard looks wrong, not when the run ends **Reconnects chased by email**: An expired token gets fixed by messaging whoever owns the source system and waiting **Changes made without a consumer list**: A table is altered and the endpoints and apps built on it find out by breaking ### With FlowRunner **Pipelines watched by a workflow**: Run status, logs, and row counts are read on completion and turned into a specific exception **Reconnects handled as a flow**: A reconnection invite goes to the credential holder with the context already filled in **Changes carry their blast radius**: Lineage names every downstream table, endpoint, and app before anything is touched ## Use Case Scenarios ### The broken connection that fixes itself, almost An OAuth connection to a source expires and its pipeline starts failing. The agent notices from List All Pipeline Runs rather than from a complaint, pulls Get Pipeline Run Log for the specific error, and checks List Server Activities to see when the connection last worked. Then it does the part that usually takes three days of email: Get Reauth Invite Prefill assembles the recipient and message from the original connect invite, and Create Reauth Invite sends a reconnection link to the person who actually holds that credential, which is rarely anyone on the data team. When they reconnect, Re Enable Server brings the connection back and Do Sync Server catches it up. A note lands in [Slack](https://flowrunner.ai/integrations/slack) at each step, so nobody has to ask where it got to. ### A transformation change that names its own consumers first Someone needs a column added to a modeled table. Before anything is edited, the agent calls Get Database Table Lineage to list what is built on that table, then walks the results: which published endpoints serve it, which data apps read it, which other tables derive from it. Get Table PK Candidates confirms the key that incremental loading depends on, and Type Formula Field reports what a formula field would become under the proposed change without changing it. List Table Query Versions establishes that the current definition is saved and can be returned to. Only then does Create SQL Query or Update Database Table run, followed by Run Query to check the output. The change set posts to the review sheet in [Google Sheets](https://flowrunner.ai/integrations/google-sheets) with the consumer list attached. ### Getting the answer out of the warehouse and into the work Warehouse data is only useful where the work happens. The agent publishes a query as an endpoint with Create API Endpoint so an application can read it without a database credential, and it installs a known pattern as a data app with Install Template rather than building one from scratch. Schedule Interface App sets the cadence, and Get Interface Schedule Run Status catches the schedule that has silently stopped firing. Where the source is [Stripe](https://flowrunner.ai/integrations/stripe) or [HubSpot](https://flowrunner.ai/integrations/hubspot) and the destination is a warehouse the company already runs on [Snowflake](https://flowrunner.ai/integrations/snowflake), the same connector manages both ends of the trip. Access stays honest because group membership is readable: List Group Users answers who can reach this data, and Get User Owned Resources makes an offboarding complete rather than approximate. ## Human-in-Loop Highlight Do Sync Deletes Server propagates deletions made at the source into the warehouse. It sounds like housekeeping and it is closer to a shredder. The reason a company keeps a warehouse at all is often that it holds rows the source no longer does: the contacts a CRM cleanup removed, the line items an application archived, the records a retention policy purged upstream. Running a delete sync removes exactly those, and there is no operation on this connector that puts them back. So the agent gathers and then stops. It reads Get Database Table Lineage for the downstream tables, endpoints, and apps, compares the row counts from List Table Runs against the previous run, and asks: "The CRM connection reports 14,208 rows deleted at source since the last run, 11% of the contacts table. Three data apps and one published endpoint read it, including the attribution app finance uses for quarter close. A delete sync would remove those rows here permanently. Run the delete sync, run a normal sync and keep the rows, or hold the pipeline until someone checks what the source deleted?" A person answers, and the reason they can answer well is that the agent did every piece of investigation first. The same gate covers the other doors on this connector that do not open twice: Delete Group takes every database and table inside it, and Toggle Interface Root Access removes the security filter that normally wraps a data app script. FlowRunner agents run the platform; the [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) step is where they hand back the decisions that cannot be retried. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 191 actions ### Published API Endpoints 6 - **List All API Endpoints** Lists every endpoint published from the account, which is the inventory of what other systems are already calling. - **List All API Endpoints Group** Lists the published endpoints belonging to one group, so an access review can run per team rather than per account. - **Create API Endpoint** Publishes a query as an HTTP endpoint attached to a group. This is how warehouse data reaches an application without handing out a database credential. - **Get API Endpoint** Returns one published endpoint with its configuration and the query behind it. - **Update API Endpoint** Changes an endpoint's configuration or the query it serves. Consumers keep the same URL, so the change reaches all of them at once. - **Delete API Endpoint** Removes a published endpoint. Anything still calling that URL begins failing immediately, so check the consumers first. ### Databases and Applications 8 - **List All Applications** Lists the applications, meaning the databases, that the account can reach. An application always belongs to one group, which is where access is decided. - **Get Default Data Warehouse Info** Returns the details of the account's default warehouse, which a workflow needs before it creates tables anywhere. - **Order Applications** Sets the display order of applications. Cosmetic, but it is what keeps a shared workspace navigable as the number of databases grows. - **Get Application** Returns one application with its type and group. Properties differ by type, so read it before assuming a shape. - **Update Application** Renames or reconfigures an application. The type is fixed at creation and cannot be changed here. - **Delete Application** Deletes an application and everything under it, including the tables, fields, and rows of a database. There is no partial version of this. - **Sync Application** Starts a sync for an application, pulling current data from whatever it is connected to. - **Check Sync Status Application** Reports where an application sync has reached, which is how a workflow waits for one instead of guessing at a delay. ### Container Factory 9 - **List All Deployment Types** Lists the deployment types available to the account, which is the first read when provisioning a dedicated environment. - **Data App Metrics** Returns resource usage for the account's dedicated data app environment. Use it to catch a runaway app before it becomes a bill. - **Data App Packages** Returns the stored, inherited, and installed packages for the data app environment. - **Install Data App Packages** Restarts the data app so the saved package list takes effect. The restart interrupts anything currently running. - **Save Data App Packages** Persists a package list without restarting, which lets a change be staged and applied at a chosen moment. - **Validate Data App Packages** Checks a draft package list against the environment's rules and against the public package index before anyone installs it. - **Data App Status** Returns the current deployment configuration and status of the data app environment. - **Install a Deployment** Installs a deployment into the account's environment. - **Uninstall a Deployment** Removes a deployment from the account's environment. ### Table Fields 7 - **List Database Table Fields** Lists a table's fields with their types, which is what a workflow reads before it writes anything into that table. - **Create Database Table Field** Adds a field to a table. Creating one can change other fields, and those are named in the response. - **Get Database Table Field** Returns one field with the properties its type carries. - **Update Database Table Field** Updates a field, including changing its type. A value that cannot be converted is set to null, so a type change can lose data and belongs behind review. - **Delete Database Table Field** Deletes a field and all the data in it. Primary fields cannot be deleted, because their value is what identifies the row. - **Get Field Lineage** Traces where a field's values come from and what depends on them, which is the read that turns a proposed change into a blast radius. - **Type Formula Field** Calculates what type a formula field would become if its formula changed, without changing anything. It is the dry run in front of an edit. ### Query Runs and Warehouse Queries 6 - **List Table Runs** Lists the runs recorded for a table, which is how a workflow checks that last night's refresh actually happened. - **Get Table Run** Returns one table run with its outcome, for the detail behind a failed or slow refresh. - **API Database Query Runs Runs Kill Create** Stops a running table query run. Reach for the scoped kill rather than the account wide one whenever the offending run can be identified. - **Kill All DWH Queries** Kills every running warehouse query on the account, other people's included. It is the blunt instrument, and the scoped kill is almost always the right call instead. - **List DWH Queries** Lists the warehouse queries currently running on the account, which is the evidence a person needs before anything gets killed. - **Kill Query** Kills one running warehouse query by identifier. This is the targeted version of the account wide kill. ### Federated Queries 4 - **Trino Execute** Runs a query against the federated query engine and returns the rows. - **List User Queries** Lists the query engine queries associated with the user, with filters on when they started and ended. - **Kill User Query** Kills one running user query on the query engine. - **Trino Database Table** Returns a table or view with change data capture updates applied, so a read reflects the source's latest state rather than the last full load. ### Database Schemas 8 - **List Database Schemas** Lists the schemas inside a database, which is the first step in mapping what a connection has actually landed. - **Create Database Schema** Creates a schema inside a database. - **Get Database Schema** Returns one schema object. - **Update Database Schema** Updates a schema object. - **Delete Database Schema** Deletes a schema and what it contains. - **Order Schemas** Sets the display order of schemas within a database. - **Sync Schema** Starts a sync at schema level, which is the narrower alternative to resyncing a whole connection. - **Check Sync Status Database Schema** Reports where a schema sync has reached. ### Database Tables 21 - **Create SQL Query** Creates a SQL query as a table, which is how a transformation is defined and then materialized in Peliqan. - **List Database Tables** Lists the tables in a database. This is the inventory every downstream workflow starts from. - **Create Database Table** Creates a table in a database. - **Get Table Final Query** Returns the query that is actually pushed down to the source for a table, which is what to read when a result looks nothing like the definition. - **Refresh Database Table** Refreshes a table, the operation the platform's own refresh function calls. - **Get Database Table** Returns one table with its configuration. - **Update Database Table** Updates a table's definition. - **Delete Database Table** Deletes a table. Anything reading it, including published endpoints and data apps, stops working at that moment. - **Change Table Database** Moves a table to a different database, which changes who can reach it because access is decided at group level. - **Update Table Details** Updates the descriptive details recorded against a table. - **Hide Database Table** Hides a table from the interface without deleting it, which is the reversible way to retire something. - **Get Database Table Lineage** Traces what a table is built from and what is built on it. This is the read that names the consumers before a change reaches them. - **Update Table Lineage Node Settings** Adjusts how a table appears and behaves as a node in the lineage graph. - **Order Database Tables** Sets the display order of tables within a database. - **Get Table PK Candidates** Returns the columns that could serve as a primary key, which is the check in front of setting up incremental loading or deduplication. - **List Table Query Versions** Lists the saved versions of a table's query, which is what makes a transformation change reviewable rather than final. - **Get Table Query Versions** Returns the version history for a table's query. - **Run Replicate** Runs a replication on a table that has replication enabled, copying its rows into the target. - **Run Query** Runs the query behind a table and returns the result. - **Sync Database Table** Syncs one table, which is the narrowest sync available and the cheapest way to refresh a single dataset. - **Check Sync Status Database Table** Reports where a table sync has reached. ### User Groups 22 - **List Groups** Lists the groups the user belongs to. A group owns databases, connections, and data apps, so it is the real unit of access in Peliqan. - **Create Group** Creates a group with only the creating user in it. Nothing is added to it automatically. - **List All Group Invitations** Lists every pending invitation across the account, which is the read behind an access review. - **List Group Invitations** Lists the pending invitations for one group. - **Create Group Invitation** Invites an email address into a group and sends a sign up link. This is the step that widens who can see the group's data. - **Get Group Invitation by Token** Returns an invitation matching a token, which is how a sign up flow resolves the link a recipient clicked. - **Get Group Invitation** Returns one invitation by identifier. - **Update Group Invitation** Updates a pending invitation. - **Delete Group Invitation** Withdraws a pending invitation before it is accepted. - **Accept Group Invitation** Accepts an invitation where the user's email matches the one invited. - **Reject Group Invitation** Declines an invitation. - **Order Groups** Sets the per user display order of groups. - **List Group Users** Lists the members of a group, which is the answer to who can currently reach this data. - **Add User to Group** Adds an existing user to a group, granting them everything the group owns. - **Update Group User** Changes a member's role within a group. - **Delete Group User** Removes a member from a group, revoking their access to everything it owns. - **Update Group** Updates a group's own attributes. - **Delete Group** Deletes a group along with every application, database, and table inside it. This is the widest destructive operation on the connector. - **List Group External Mappings** Lists the mappings between a group and an external identity provider's groups. - **Create Group External Mapping** Maps an external identity provider group onto a Peliqan group, so membership follows the directory rather than a manual list. - **Delete Group External Mapping** Removes an external group mapping, after which membership stops following the directory. - **List Group Non Members** Lists the account's users who are not in a group, which is the candidate list an access request is granted from. ### Data App Runs 5 - **List All Interface Runs** Lists data app runs the user can see, with filters. This is the operational history of everything built on top of the warehouse. - **Create Interface Run** Starts a run of a data app. - **Get Interface Run** Returns one data app run and its outcome. - **Update Interface Run** Updates a data app run record. - **List Interface Run Logs** Streams the logs of a run as it happens, which is what an agent watches to decide whether to escalate a failure. ### Data App Templates 4 - **List Templates** Lists the data app templates available to the account. - **Install Template** Installs a template as a working data app, which is the fastest path from a known pattern to a running one. - **List Templates Labels** Lists the labels used to categorize templates. - **Get Interface Template** Returns one template by identifier. ### Data Apps 18 - **List All Interfaces** Lists the data apps the user can see. - **List Group Interfaces** Lists the data apps belonging to one group. A data app always belongs to a single group. - **Create Interface** Creates a data app inside a group. - **Get Interface Logs** Returns the logs of a data app run. - **Reorder Interfaces** Sets the display order of data apps in the account. - **Get Interface Schedule Run Status** Reports the status of a data app's scheduled run, which is how a workflow notices a schedule that has silently stopped firing. - **Get Interface** Returns one data app with its configuration. - **Update Interface** Updates a data app, including the script it runs. - **Delete Interface** Deletes a data app. Anyone using the published version loses it at that moment. - **List Interface Owner Candidates** Lists the group members eligible to own a data app, which is the read behind an ownership handover when someone leaves. - **Publish or Unpublish Interface App** Publishes a data app so people can use it, or withdraws it. Unpublishing takes a working tool away from everyone at once, so it belongs in a change window rather than in a cleanup pass. - **Get Run Published Interface App** Returns the run of a published data app. - **Toggle Interface Root Access** Turns off the security filter that normally wraps a data app script, letting it run without that sandbox. Account owners only, and one of the operations this connector's human gate exists for. - **Schedule Interface App** Schedules a data app to run on a cadence. - **List Interface Script Versions** Lists the saved versions of a data app's script, which is what makes a script change reversible. - **Get Interface Script Versions** Returns the version history of a data app's script. - **Get Interface State** Returns a data app's stored state, the values it carries between runs. - **Update Interface State** Writes a data app's stored state. Use it to reset a stuck app rather than editing its script. ### Pipeline Runs 5 - **List All Pipeline Runs** Lists pipeline runs with filtering, sorting, and paging. This is where a workflow finds out whether last night actually worked. - **Run a Pipeline** Runs the pipeline for an existing connection, which is the on demand version of a scheduled sync. - **Get a Pipeline Run** Returns one pipeline run and its outcome. - **Kill a Pipeline Run** Stops a running pipeline. A run stopped part way leaves a partial load, so the follow up matters as much as the kill. - **Get Pipeline Run Log** Returns the log for a pipeline run, which is the evidence attached to an escalation. ### Connections 29 - **List All Servers** Lists the connections the user can reach. A connection always belongs to one group. - **Create Server** Creates a connection in the user's first group. - **List Servers** Lists the connections in a group. - **Create Server in Group** Creates a connection inside a named group, which is the version to use when placement matters. - **Get Connection Invite** Returns an invite that lets someone outside the account create a connection of a specified type. - **Create Connection Invite** Creates an invite so a customer or colleague can connect their own system without being given account access. This is how a source gets connected by the person who actually holds the credential. - **Get Server** Returns one connection with its type and status. - **Update Server** Updates a connection. The type is fixed, but properties such as the name can change. - **Delete Server** Deletes a connection and everything under it. The tables it landed go with it. - **List Server Activities** Lists the events recorded against a connection, which is the audit trail for what it has been doing. - **Get Connector Streams** Returns the tables a connection can select, read from the connector definition the connection actually runs against rather than the latest one. That distinction is what explains a stream that exists in the documentation but not in your account. - **List SaaS Server Logs** Returns the pipeline logs for a SaaS connection. - **Get Password** Returns the stored password for a connection. It exists for provisioning flows, and it is a credential read that belongs in an audited path. - **Update SaaS Server Pipeline** Changes a SaaS pipeline's settings, including what it syncs and how often. - **Update Connector File** Updates the connector definition a connection runs against, which pins or advances the version its syncs use. - **Get Connection Schema** Returns the catalog, meaning the selected tables and fields, for a pipeline. - **Set Connection Schema** Sets the catalog for a pipeline, which is how a workflow adds or drops a table from a sync without touching the credential. - **Get Connection State** Returns a pipeline's replication state, the bookmark that tells it where the last run stopped. - **Set Connection State** Writes a pipeline's replication state. Moving the bookmark backwards forces a re-read and moving it forward skips records, so this is a deliberate act rather than a cleanup step. - **Re Authorise Server** Returns the authorization link that starts a reconnect for an OAuth connection. - **Re Enable Server** Sets a disabled connection back to enabled. - **Get Reauth Invite Prefill** Returns the prefilled recipient and message for a reconnection invite, drawn from the original connect invite where one exists. - **Create Reauth Invite** Emails a reconnection invite for an OAuth connection whose token has expired. Sending to a different recipient invalidates the previous active invite, so the last one sent is the only one that works. - **Do Full Resync Server** Re-reads everything from a SaaS source. It is the operation that fixes a corrupted load and the one that will exhaust a metered source's quota, which is why it is a decision rather than a retry. - **Get Server Full Resync Status** Reports where a full resync has reached. - **List SaaS Server Runs** Lists the pipeline runs for a SaaS connection. - **Do Sync Deletes Server** Propagates deletions made at the source into the warehouse. Rows the source has purged are removed here too, which is often exactly the history the warehouse was kept for, and no operation puts them back. - **Do Sync Server** Runs a sync: all databases for a database connection, or the pipeline for a SaaS connection. - **Get Server Sync Status** Reports where a connection's sync has reached. ### Connector Types 2 - **List All Servertypes** Lists every connector type the account can use, with what each one requires. - **List Servertypes Public** Lists the publicly available connector types, which is the catalog a self serve connection flow is built from. ### Users and Accounts 21 - **Create User** Creates a user, optionally with a token, and sets up their initial group and database. - **Update Account Onboarding** Updates the account's onboarding profile. Owner only. - **Update Account** Updates the authenticated account's information. - **Update User Me** Updates the authenticated user's own details. - **Get User API Token** Returns the current user's personal API token, or nothing where none exists. - **Create User API Token** Issues a personal API token, or returns the existing one. This is the credential a workflow runs as, so its creation belongs in an audited path. - **Delete User API Token** Revokes the current user's personal API token. Anything using it stops working immediately. - **Change Password** Changes an authenticated user's password, given the current one. - **Dashboard** Returns the summary a user's landing view is built from, including their pending group invitations. - **User Me** Returns the authenticated user, which is the connection test and the check that a workflow is running as who it thinks it is. - **Update User Me Settings** Writes the per user interface settings. It is last writer wins, so send the full object after merging rather than a fragment. - **Reset Password** Sets a password using a valid reset token, without the old password. - **Send Password Reset Email** Sends a password reset link. It does not fail for an unknown address, so a success here is not evidence the account exists. - **Get Account Verification** Verifies an account against a token. - **Post Account Verification** Sends the account verification email. - **List All Users** Lists the users on the account. Owner level access, and the starting point for a periodic access review. - **Get User** Returns one user by identifier. - **Update User** Updates a user record. - **Delete User** Deletes a user. Check what they own first, because ownership does not move on its own. - **List All Groups of User** Lists the groups a user belongs to, which is the fastest answer to what one person can currently reach. - **Get User Owned Resources** Returns every connection, data app, and query a user owns. This is the read that makes an offboarding complete rather than approximate. ### Sub Accounts and Whitelabels 16 - **Get Sub Account** Returns one sub account under the partner's account. - **Update Sub Account** Updates a sub account. Only the fields sent are changed, and the webhook event list can be narrowed or set to receive everything. - **Get Sub Account Identity** Requests an identity token for a sub account owner, which lets a partner act on that account's behalf. One token exists per account at a time. - **Get Sub Account Integration Token** Requests a short lived token for a sub account user, defaulting to the owner. - **List Sub Account Targets** Lists the target warehouses available to a sub account. - **Remove Sub Account Webhook Secret** Removes a sub account's webhook signing secret, after which delivered events can no longer be verified. - **List Sub Account** Lists the sub accounts under the partner's account. - **Create Sub Account** Creates a sub account under the partner's account, which is how a partner provisions a customer. - **Trigger Dedicated App** Starts creation or removal of a dedicated data app environment for a sub account. - **Delete Dedicated App** Removes a sub account's dedicated data app environment. - **Get Sub Account Info** Returns the stored detail for a sub account. - **Partner Sub Account Login** Logs a partner directly into a sub account. Support access to a customer's data is a privileged act and belongs in an audit trail. - **List Sub Account Users** Lists the users inside a sub account. - **Create Sub Account User** Creates a user inside a sub account under the partner's account. - **Get Whitelabel** Returns one whitelabel configuration belonging to the account. - **List Account Whitelabels** Lists the whitelabel configurations linked to the account. ## Frequently Asked Questions ### What can FlowRunner do with Peliqan? FlowRunner agents can run List All API Endpoints, List All API Endpoints Group, and Create API Endpoint in Peliqan, plus 188 more actions. ### Does connecting Peliqan to FlowRunner require OAuth? No. Peliqan connects to FlowRunner with an API key, no OAuth flow required. ### Can Peliqan trigger a FlowRunner workflow automatically? Peliqan doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Peliqan?** This integration exposes Peliqan to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/peliqan. Site index: https://flowrunner.ai/llms.txt