Modify a team member by ID in LaunchDarkly

What this operation does

Modify a team member by ID.

• PATCHChanges data · Team membersapp.launchdarkly.com/members/{memberId}

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which LaunchDarkly operations the program may use, and this is one of them.
3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other LaunchDarkly operations

• Create a new integration subscription of a given kindPOST · changes data
• Create a new custom rolePOST · changes data
• Create a new tokenPOST · changes data
• Invite new membersPOST · changes data
• Create a new project with the given key and namePOST · changes data
• Create a webhookPOST · changes data
• Create a new relay proxy configPOST · changes data
• Creates a new user segmentPOST · changes data

All 105 LaunchDarkly operations

Questions

Can HumDay modify a team member by id in LaunchDarkly?

Yes. This operation is published in LaunchDarkly's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Will this change my LaunchDarkly data?

Yes — this is a PATCH operation, so it changes something in LaunchDarkly. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.

Do I need to write code?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your LaunchDarkly account.

Where this came from

Read from a published API description for LaunchDarkly at launchdarkly.github.io/ld-openapi/openapi.json. The description above is the provider’s own wording, not ours. Last published 2021-07-19.