Update Stripe Connector
Audience:
Low-code EngineersSkill Prerequisites:
Actions,Tokens,Connectors
Changes an existing Stripe connector. The action finds the connector by its ID and saves a new title and secret key.
The update replaces the connector's details. An empty field clears the saved value, so pass every value you want to keep.
note
This action requires the Stripe feature to be licensed.
Typical Use Cases
- Save a new secret key after you roll the key in Stripe
- Switch a connector from a test key to a live key
- Let users edit their saved Stripe account from a form
Don't use it to
- Create a connector. Use Add Stripe Connector instead.
- Check that the new key works. The action saves it without contacting Stripe.
- Update a connector of another type. Use Update Connector instead.
Related Actions
| Action Name | Description |
|---|---|
| Add Stripe Connector | Creates a Stripe connector and returns its ID. |
| Get Connector | Reads the details of a connector. |
| Delete Connector | Removes a connector. |
| Update Connector | Changes a connector of any type. |
Input Parameter Reference
| Parameter | Description | Supports Tokens | Default | Required |
|---|---|---|---|---|
| Entry Id | The ID (GUID) of the connector to change, for example [StripeConnectorId]. | Yes | empty string | Yes |
| Entry title | The new name of the connector. It always replaces the current name, so an empty value clears it. | Yes | empty string | No |
| Secret Key | The Stripe secret API key. Saved encrypted. Use ****** to keep the saved key. An empty value clears it. | Yes | empty string | No |
Considerations
- Everything is replaced. The title and key are saved as entered. To keep the saved key without knowing it, pass
******. - The Entry Id must exist. An empty value fails with
Data was not saved due to an invalid EntryId!. An ID that isn't found fails withRequested connector, with id '...', does not exist.A value that isn't a GUID also fails. - The connector type isn't checked. The action changes whatever connector the ID points to. If the ID belongs to another type of connector, that connector's fields are cleared. Make sure it's a Stripe connector.
- The key isn't tested. You'll only find out that a key is wrong when a Stripe action runs.
- Keep secrets out of the action. The editor shows
Secret Keyas plain text. Pass the key through a token instead of typing it into the action.
Examples
tip
To understand how to use the below examples, please see Running Examples.
1. Save a new Stripe key
This action updates the connector with ID [StripeConnectorId] with a new secret key from a form.
{
"Title": "Update Stripe Connector",
"ActionType": "cs.stripe.update",
"Description": "Save the new Stripe secret key",
"Parameters": {
"EntryId": "[StripeConnectorId]",
"EntryName": "Stripe - [CompanyName]",
"SecretKey": "[StripeSecretKey]"
}
}
2. Rename a connector and keep its key
This action renames the connector and keeps the saved key by passing ******.
{
"Title": "Update Stripe Connector",
"ActionType": "cs.stripe.update",
"Description": "Rename the Stripe connector",
"Parameters": {
"EntryId": "[StripeConnectorId]",
"EntryName": "Stripe - [NewCompanyName]",
"SecretKey": "******"
}
}
Revised 09/26/2026