Guides
Make
The OpenRows app for Make connects your bases to the apps Make works with: start a scenario when a record is added or changed, and create, update, get, search or delete records from any other app.
Hosted only. The Make app works with the hosted OpenRows at app.openrows.io. A self-hosted server can't be connected to it; use webhooks with Make's own Webhooks and HTTP modules, the REST API or the n8n nodes instead. The app is published and in Make's review: until Make approves it for its app directory, it shows up in Make for people who have opened its invite link.
Connect your account
- In a scenario, add an OpenRows module and select Create a connection.
- Sign in to OpenRows if you aren't already. The consent screen shows what Make asks for (reading and writing records, reading your bases' tables and fields, managing webhooks for Watch Records, and your email address) and lets you choose the workspaces or single bases it may reach.
- Select Allow. The connection appears in Make under your email address.
Make acts as you: it can only do what you can do in the bases you picked, and it loses access when you do. To disconnect it, open Settings → Integrations in OpenRows and revoke Make, or delete the connection in Make (which revokes it in OpenRows too).
Watch Records
An instant trigger: OpenRows sends each change to Make as it happens, through a webhook it registers on the base when you create the trigger's webhook in Make (and deletes when you delete that webhook). A base has at most 10 webhooks, so at most 10 Make webhooks (and Zapier triggers) can watch one base.
Pick the base and the table, then Watch: New records, or New and updated records. For updates you can pick Fields to watch to start the scenario only when one of those fields changes; new records always start it. Public form submissions and records added through the API count as new records.
Each bundle is the record as it is when Make reads it, with every field by name, plus its Record ID, Created time, the Event (record.created or record.updated), the Event ID, the Event time and, for an update, the Changed field IDs. Make reads the record from OpenRows for every delivery, so a scenario only ever gets records you can read. If the record was deleted before Make reads it, the run still succeeds: Record still exists is false, Fields and Created time are empty, and Event cells holds the values the event carried, keyed by field ID (raw, so a select holds its option's ID). Filter on Record still exists if later modules need the record.
Modules
| Module | What it does |
|---|---|
| Create a Record | Adds a record with the fields you fill in. |
| Update a Record | Changes the fields you fill in on a record (by its ID); fields you leave empty stay as they are. |
| Get a Record | Gets a record by its ID. |
| Search Records | Finds the records that match a filter formula, optionally only those in a view, sorted by fields you pick, up to the limit you set. |
| Delete a Record | Moves a record to the base's trash, where it can be restored for 30 days. |
| Make an API Call | Calls any route of the REST API v1 with your connection: enter the path after https://app.openrows.io/api/v1, for example /meta/bases. |
After you pick the base and table, Create and Update show one input per field of the table, with its type: numbers, yes/no for checkboxes, dates, and lists for multiple selects and linked records. Computed fields (formulas, lookups, rollups, counts, AI fields, created and modified times) and attachments can't be set. For a linked record field, enter the IDs of the records to link; for a user field, the person's OpenRows user ID. A select field's help lists its options.
Convert values lets OpenRows read text as the field's type where it can, for example a date written out, a select option by name or a linked record by its name. Adding a new select option this way needs permission to change the base's schema, which the Make app doesn't ask for, so pick existing options.
Limits
- Scenarios share your account's API rate limits: 5 requests a second per base and 50 per connection. A scenario that goes over them gets a rate-limit error, which Make can retry.
- Edit permissions on tables and fields apply to Make as they do to you; a refused write shows OpenRows' reason in the scenario's history.
- The app doesn't upload attachments or change a base's tables and fields yet.
- A webhook OpenRows turns off after failing for a day (or because you lost access to the base) stops Watch Records until you turn the scenario off and on again.