GitLab Integration

The GitLab integration for Expiration Reminder automatically creates a GitLab issue when a tracked record — such as a license, document, or certification — approaches its expiration date. Connect the two tools in Settings > Integrations, authorize your GitLab account, choose which records to monitor and how far in advance, and Expiration Reminder will file renewal issues directly into your GitLab workspace.

Before you begin

Make sure you have the following ready:

• An active Expiration Reminder account with permission to manage integrations.
• A GitLab account with permission to authorize third-party access.
• The documents, licenses, or certifications you want to monitor already added in Expiration Reminder, each with an expiration date.

How to set up the GitLab integration

1. Sign in to your Expiration Reminder account.
2. Go to Settings > Integrations.
3. Find GitLab in the list of available integrations and click Connect.
4. In the authorization window, sign in with your GitLab credentials and approve the requested access.
5. After the authorization window closes, you will be returned to the GitLab integration settings page in Expiration Reminder. Choose which categories of records should create issues and enter how many days before each expiration date an issue should be created.
6. Save your settings. The integration is now active.

What syncs, and what triggers an issue?

After setup, Expiration Reminder monitors the expiration dates of the records you selected. When a record reaches the lead time you configured, the integration creates an issue in GitLab that includes the item name and its expiration date so your team has the context to act.

You control which categories of records create issues and how far in advance, so your workspace stays focused and uncluttered.

Managing renewal issues in GitLab

Renewal issues behave like any other GitLab issue. You can assign owners, set due dates, track progress, add notes, and close them once the renewal is complete. Your team manages renewals using the GitLab workflow they already know.

Troubleshooting

• Issues aren't being created. Confirm the integration shows as connected in Settings > Integrations, and that the records you expect have a valid expiration date within your configured lead time.
• The connection failed during setup. Make sure you approved the requested GitLab permissions, then try connecting again.
• The connection stopped working. If your GitLab access changed, reconnect the integration to refresh authorization.

Frequently asked questions

Will this create duplicates?

No. Each monitored record creates an issue once as it approaches its configured lead time.

Can I choose which records create issues?

Yes. You decide which categories of records are included and how far in advance.

Is there an extra cost?

See the pricing page for details on which plans include this integration. A GitLab account is required separately.