Select
PostgreSQL Plugin – Select
Summary (SEO Meta Description):
The PostgreSQL Select action in WeHub retrieves rows from a PostgreSQL database table.
Supports filtering, ordering, limits, and schema-based mapping for seamless data queries in workflows.
Overview
The Select action allows workflows to query data from a PostgreSQL database table.
It supports conditions, ordering, limits, and offsets to fetch structured data efficiently.
This action is commonly used to fetch rows for processing, reporting, or validating workflow data.
Typical Use Cases:
- Fetch patient records from a clinical database
- Retrieve financial transactions with filters and sorting
- Load reference data for enrichment in workflows
- Paginate large queries using limit and offset
⚙️ Action: Select
Configuration Options:
| Field | Type | Description |
|---|---|---|
| Label | String | Custom name for the action. |
| Select Connection | Enum | Choose or create a PostgreSQL connection. |
| Table Name | Enum | Select the table to query from. |
| Columns | List | Specify which columns to return (default: *). |
| Condition | String | SQL WHERE condition to filter rows. |
| Order | String | ORDER BY clause for sorting results. |
| Limit | Number | Limit number of rows returned. |
| Offset | Number | Skip a number of rows (for pagination). |
| Inputs (Manual) | Mixed | Map input parameters manually with types (NUMBER, STRING, BOOLEAN, etc.). |
| Inputs Schema | Schema | Use schema-based mapping for query inputs. |
| Outputs Schema | Schema | Map query results into a defined schema. |
FAQ
Q: Can I run parameterized queries with Select?
A: Yes. Use Manual Inputs or Schema mapping to safely parameterize queries.
Q: Does Select support large datasets?
A: Yes, but it’s recommended to use Limit and Offset for pagination.
Q: Can I join multiple tables?
A: No. The Select action is limited to a single table. Use the Custom Action for complex queries.
Keywords: WeHub PostgreSQL Plugin, PostgreSQL Select, Database Query Workflow, SQL Integration in WeHub