@Kamil Logically you can have one trigger type per function.
In this case if your function is triggered from blob action then you can consider adding an additional parameter [OrchestrationClient] DurableOrchestrationClient orchestrationClient which gives you the ability to start new orchestrations to further orchestrate how your function will be executed
and deligate the work to the activity functions. You may want to look into the the durable function patterns https://learn.microsoft.com/en-us/azure/azure-functions/durable/durable-functions-overview?tabs=csharp#application-patterns for your requirement.
This is how you can set up Orchestration :https://learn.microsoft.com/en-us/sandbox/functions-recipes/durable-setup
https://pacodelacruzag.wordpress.com/2018/04/17/azure-durable-functions-approval-workflow-with-sendgrid/ - explains the steps to implement blobtrigger with Durabale function.
Suggestion: If you are working with small blob files, then you can go ahead with this approach, otherwise, ideally, you should use Event Grid trigger which starts the orchestration. Then in the orchestration, you can use an input binding to fetch the blob ( depending on the requirement), get the blob in an activity function
Please let me know if this helps and answers your query.