Backend workflows (also called API workflows) are server-side workflows that you can schedule/trigger in your application and/or expose to be triggered from an external application or system through an API request. They run independently of any page, which means that they do not affect on-page performance for users.
Coming soon!
Listed below is each backend workflow from Casper with an explanation of it’s behavior.
This workflow is triggered when a new prompt is created and adds the Prompt to selected Categories. A prompt must be added to the corresponding Category entry in order for it to be shown on the front-end.
This workflow is triggered in other API workflows to consume credits on an account when an output is generated.
This workflow is triggered when a new account is created in order to add Free Plan credits to a user’s account each month. It is also triggered when a Stripe subscription is cancelled.
This workflow is triggered when a new account subscribes to the power plan and handles adding plan credits each month.
This workflow is triggered when a new account subscribes to the power plan and handles adding plan credits each month.
This is where you will configure your Stripe webhook for subscription updates and deletions. It takes in the provided Stripe subscription status and apply whichever plan credit consumption workflows are necessary.
This workflow is triggered when a custom prompt generation is completed in the Document editor. It then adds the response to the document if the document is empty, and appends it to the end if the document already has content.