Running an action that issues a repository_dispatch call in act?

[lejtemxviw]

Hi! I am trying out act to see whether we could use it to help us develop our internal workflows and actions, and ran into an issue I wanted to ask for feedback on: we have a workflow A that does some work, then triggers a call for a workflow B to run in a second repo via a repository_dispatch even using an action that was contributed to GH. I am assuming that, when we run this workflow A using act, it will actually contact GH and try to get that workflow B to run on that other repo, as normal - but I would rather it saved the event payload to a file, so I could run that second workflow using act after the first one completed. Is this something that act would be smart enough to do on its own - somehow catch requests to the particular URL that GH uses for repo dispatch and save them to a file, instead - or would I need to fork that action we are using to trigger the call to B so that it's smart enough to recognize whether it's running in act and handle the call differentl (by saving the event...).
Thank you!