Merge Request
Emit an event when a merge request is created or changed.
Ready-made Workflow
Notify a Slack channel when a new GitLab merge request is opened. Help reviewers notice incoming work with the title, merge request number, project, author, branches and source link. Connect GitLab and Slack, choose the source project using the standard resource browser and select a Slack channel where FastHook can post. The Actions filter is prefilled with open; edits, approvals, merges and closures do not post another creation alert. Wait for the Trigger to show Connected after activation before opening a test merge request. Only new webhook events are processed, not existing merge requests. The fictional example contains German characters. Messages use plain text with link previews disabled. Descriptions, code and attachments are not copied. This is a one-way notification, not a review-status sync. Project members still need GitLab access to open the source link; title and branch names become visible to channel members. Manual reruns can send another message.
What gets copied
FastHook recreates every Step, route, field mapping, and setting with new IDs in your workspace.
Emit an event when a merge request is created or changed.
Send text, Block Kit content, attachments, or a thread reply to a channel.
Before activation
Connect your own GitLab account and review the provider settings used by this Workflow.
Connect your own Slack account and review the provider settings used by this Workflow.
Questions
No. FastHook creates a disconnected Draft. Connect your own GitLab, Slack accounts before activation.
Yes. The copied Workflow is an editable Draft. Review every Step, input, mapping, and route before you activate it.
FastHook recreates the Trigger configuration, Action Steps, routes, and mappings with new IDs. Provider accounts, credentials, and secrets are never copied.
Only after you connect the required accounts, finish the configuration, and explicitly activate the Draft.