Run Jira “Create Issue” from GitLab “Push”
TriggerGitLab · Push
ActionJira · Create Issue
Choose either direction, select popular real Trigger and Action definitions, and open a preconfigured Workflow draft.
Your selected Trigger and Action are carried into FastHook. Connect accounts, review field mapping, and activate only when the draft is ready.
Popular Workflows
Each template fixes a useful starting Trigger and Action. You can change both operations inside the Workflow draft.
TriggerGitLab · Push
ActionJira · Create Issue
TriggerJira · Issue Created
ActionGitLab · Create Issue
TriggerGitLab · Tag Push
ActionJira · Update Issue
Two-way automation
The public builder uses popular operations as a focused starting point. The technical references contain all 46 Triggers and 12 Actions available across this pair.
GitLab → Jira
Use GitLab “Push” as the Trigger, then map its output into Jira “Create Issue”.
Jira → GitLab
Use Jira “Issue Created” as the Trigger, then map its output into GitLab “Create Issue”.
24 Triggers · 6 Actions
Trigger from GitLab projects and groups and automate issues, merge requests, comments, and pipelines.
22 Triggers · 6 Actions
Start from Jira issue, comment, sprint, version, and property events and automate issue operations.
Start in either app and change direction without leaving the public integration page.
Use focused popular operations here; the complete provider catalogs remain in the technical documentation.
Connect accounts, confirm resources and schema-aware mapping, then activate explicitly.
Yes. Choose one of the popular GitLab Triggers on this page and pair it with a Jira Action. FastHook creates a draft so you can connect accounts and review mapping before activation.
Yes. Switch the direction in the builder, then select a Jira Trigger and a GitLab Action.
Yes. The public builder sets the starting values. You can change the operation, account, resource, and field mapping inside the FastHook Workflow before activation.
FastHook uses the Trigger output schema and Action input schema to propose compatible fields. Review ambiguous or provider-specific values in the draft before the first run.