Id like an automatic (email) alert when connectors go down or need updates so we dont have to check the dashboard to know when to update

Currently, the welcome email generated follows this format: Subject: Welcome to G Suite Body: Hello, Great News. You have a new account at <Company Name>. Your username is: <username>andYour password is: <password>. People...

Our organization requires that we remove these recovery email and phone number and having these two features under the "THEN" area of a workflow would help us with our tasks enormously. Currently, we're required to logged into each separated staff...

Please add a field for Cost Center on the google sheet so we can easily view and bulk update all users in one place.

In order for them to see value in our onboarding and offboarding automations, they'll need to be able to create a new user in Salesforce the same way as we can create a new user in the rest of the applications we connect with. Since the actions f...

*Re: Okta alerts*We only have deactivation, but that kickstarts lots of deprovisioning items in Okta and subsystems. Id rather suspend than have BC do granular steps in the deprovisioning including _grace wait_ and than end with deactivation and k...

Of our 20 workflows, there's a generic set of steps we want done at the end of all the workflows. What would be easier to maintain is having one Workflow that is the boilerplate (i.e. send a slack message or create a user in a connected app) be ca...

It is inconvenient to log in to view the workflow results. If errors were included in the notification, this would help assess urgency.

This seems self evident. The slack connector should only try to run on channels that are not already archived.

I've found during our on boarding experience when testing a user thats been deleted/recreated multiple times, we begin to see multiple 'unique' users existing in separate connectors, and they don't group together when grouping all connectors. It ...