With a manual trigger, you can add a button at the top of the page for a selected entity (organization, person, opportunity, etc.), from which you can initiate an automatic flow. This type of automation is relevant for flows that don't need to start every time, as they are only activated manually by clicking the button.
Case - Create Pipeline and Notify Seller with a Single Click
When a customer requests paid support, the support agent can expedite the purchasing process by ordering a certain number of hours directly for the customer from the support case with just one click.
Once the support agent has specified the requested hours, an opportunity with the necessary details for the seller is automatically created, and the seller is immediately notified via a notification.
To provide the best overview, information along with a link is added to the log of both the support case and the opportunity, making it easy to navigate between them to view the history and status.
View the workflow here: VIDEO (not ready yet)
Setup
Go to utilities → automation → 
create → select the trigger type manual to set up a new workflow.
💡Tip! Provide descriptive names for each flow and all steps within the flows for an easy overview of the content and purpose.
Trigger
1. Specify in the entity type that the button should be placed on support cases
2. Choose decimal numbe as the button type, and name the button.
💡Tip! By marking the button mandatory, the workflow can only start if a decimal number is specified in the field. This way, you avoid activating flows without a real value.
Aktion - Create Opportunity
1. Click 
to insert the action create
2. Select the entity type Opportunity
3. Set the deadline for the opportunity by clicking on 
→ field → expand the list → select special → today's date.
4. Add and map the remaining fields based on the information you want to add to the new opportunity.
Aktion - Add to log
5. Click to insert the action add to logg
6. Select the entity type opportunity
7. Ensure that the entity ID is set to opportunity case/system ID
8. Use merge fields to add information from the support case to the opportunity log
Aktion - Add to log
9. Click to insert the action add to log
10. Select the entity type support case
11. Ensure that the entity ID is set to support case / system ID
12. Use merge fields to add information from the opportunity to the support case log
Action - Send notification
13. Click to insert the action send notification
14. Set the recipient to the sales responsible
15. Determine a notification title
16. Use merge fields to add information from the offer/support case to the notification.
Possible Extension to the Workflow
Set up a flow that notifies or sends an email to the support agent when the offer is won. For this flow, use the entity event type.
Other Examples of Manual Triggers
Qualify a lead and assign an account manager
When a lead is qualified, the button can be clicked to categorize the lead as A, B, or C. Here, the lead is assigned an account manager, and an activity is created for A-leads.
Forms - Help us with the correct information
When a lead needs to be qualified, an email is sent to the lead with a form to fill out the missing company and contact information.
Overdue Invoice - Notify account manager about missing payment
If a company hasn't paid its invoice, the accounting department can click a button on the order. Here, an activity is created, and an email is sent to the account manager.
Read More About
Get an introduction to webCRM's automation module, or see various cases for each of the automation types here:
Entity Time
Schedule
Entity Event
Email Event