Update index.mdx

Author: clairekinde11

src/content/docs/workflows/about-workflows/index.mdx

@@ -13,17 +13,9 @@ In Kinde, workflows exist to give you (almost) unlimited power over how Kinde wo
 
 Develop code in your own repo, and push it to a Kinde workflow, where we execute it in ways that you define, triggered by Kinde events.
 
-Currently, you can use the following triggers:
+See the [Triggers](/workflows/example-workflows/workflow-user-post-auth/) section for the whole list of triggers.
 
-- [user:pre_registration](/workflows/example-workflows/pre-user-registration-workflow/) - when a user attempts to register an account.
-- [user:post_authentication](/workflows/example-workflows/workflow-user-post-auth/) fires after the user has completed single factor authentication (e.g. email + password or Google), and before authorization.
-- [m2m:token_generation](/workflows/example-workflows/m2m-token-generation-workflow/) - when a request to the token endpoint is made with an M2M application.
-- [user:new_password_provided](/workflows/example-workflows/new-password-provided-workflow/) - when a user requests to create or reset a password.
-- [user:existing_password_provided](/workflows/example-workflows/existing-password-provided-workflow/) - when a user hasn’t signed in, but they have requested to sign in and given their current password.
-- [user:token_generation](/workflows/example-workflows/user-token-generation/) - An ID or access token is generated after authentication or refresh token request.
-- [user:pre_mfa](/workflows/example-workflows/pre-mfa-workflow/) - where the user has completed single factor authentication (e.g. email + password or Google) and determined which organization (if any) they are trying to access. This trigger is only available to customers on a Kinde Scale plan.
-
-We will add more triggers (and allow you to create your own) as we develop the feature.
+We will add more (and allow you to create your own) as we develop the feature.
 
 ## When to use a workflow