PipedreamHQ/pipedream

[ACTION] Softr - Update User & Search User

Open

#20929 opened on May 19, 2026

View on GitHub
 (0 comments) (0 reactions) (1 assignee)JavaScript (7,438 stars) (5,305 forks)batch import
actionenhancementgood first issuehelp wantedprioritizedtriaged

Description

Softr (https://www.softr.io/)

First Action: Currently actions exist for Create User & Delete User, but we need an "Update User" action — i.e. change field values on an existing user.

Note: Softr's User Management API has no update endpoint. User records that need updating live in Softr Databases, so this action should be built on the Softr Database API Update Record endpoint: PATCH https://tables-api.softr.io/api/v1/databases/{databaseId}/tables/{tableId}/records/{recordId} Docs: https://docs.softr.io/softr-api/softr-database-api/records/update-record

Action 2 — Search Users A standalone action to look up records by a field value (e.g. email) rather than record ID. This is broadly useful as its own workflow step for any Softr customer, not specific to this use case. It also pairs naturally with Update User — since Update Record needs a record ID, users would search first to resolve the ID, then pass it into Update User. Two single-purpose nodes keeps both composable for any workflow. Built on the Search Records endpoint: POST https://tables-api.softr.io/api/v1/databases/{databaseId}/tables/{tableId}/records/search Docs: https://docs.softr.io/softr-api/softr-database-api/records/search-records

Auth: Softr-Api-Key header (Personal Access Token).

Contributor guide

Tech stack
javascriptnodejsrest api
Domain
backendapi
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Familiarity with Pipedream componentsBasic REST API knowledge
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Review existing Softr actions (Create User, Delete User) in the Pipedream repository to understand the component pattern. The issue provides links to Softr's API docs for Update Record and Search Records. There is one assignee, so check if they have started work. The implementation should create two separate action components under the Softr app, following the structure of existing actions. Use the provided API endpoints and auth header.