Skip to content
English
Customer portal
  • There are no suggestions because the search field is empty.

Github Issues Integration

The GitHub Issues integration connects your Expiration Reminder account to GitHub Issues so that upcoming expiration deadlines can be turned into GitHub Issues issues automatically. Renewals appear in the workspace your team already uses, alongside the rest of your work.

Before you begin

Make sure you have the following ready:

  • An active Expiration Reminder account with permission to manage integrations.
  • A GitHub Issues 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 GitHub Issues integration
  1. Sign in to your Expiration Reminder account.
  2. Go to Settings > Integrations.
  3. Find GitHub Issues in the list of available integrations and click Connect.
  4. In the authorization window, sign in with your GitHub Issues credentials and approve the requested access.
  5. Choose which records should create issues and how many days before each expiration date a issue should be created.
  6. Save your settings. The integration is now active.
What syncs and what triggers a 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 a issue in GitHub Issues 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 GitHub Issues

Renewal issues behave like any other GitHub Issues 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 GitHub Issues 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 GitHub Issues permissions, then try connecting again.
  • The connection stopped working. If your GitHub Issues access changed, reconnect the integration to refresh authorization.
Frequently asked questions

Will this create duplicates? No. Each monitored record creates a 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? The integration is available on all Expiration Reminder plans. A GitHub Issues account is required separately.