Keep EspoCRM configuration context near extension releases
If you maintain an EspoCRM extension, a published release is a useful moment to review the CRM instance's current metadata. Notis can retrieve that metadata and summarize only the configuration context you want to inspect.
Trigger
GitHub Release State Changed
Triggers when a specific GitHub release (identified by tag name) changes. Monitors the release title, body/notes, draft flag, prerelease flag, published timestamp, target branch/commit, and the set of attached assets. The payload includes the full current release details, a list of which fields changed, and the previous values for comparison.
Action
Get Metadata
Tool to retrieve metadata information from espocrm. use when you need to discover system configuration, user details, acl, and translations right after authentication.
Why this helps
Extension release notes and the CRM instance's live configuration are easy to review in separate places, making a manual post-release configuration check easier to forget.
- Create a repeatable metadata review cue when an extension release is published.
- Keep relevant configuration and ACL context close to the release report.
- Avoid changing CRM data or treating a metadata snapshot as a compatibility test.
Setup
Build it in a few focused steps.
- 1Connect GitHub and EspoCRM to Notis once in the portal.
- 2Create an automation and describe that, for releases of your EspoCRM extension, Notis should retrieve metadata and summarize only the configuration and ACL context you want reviewed; exclude unnecessary user details.
- 3Select the GitHub release-state trigger, ask Notis to act only when the release is published, and choose where run reports should go.
- 4Test with one published release and confirm the report contains a metadata summary, not claims of a compatibility test or any unnecessary personal data.
Questions about this workflow
Does this validate that the released extension is compatible with EspoCRM?
No. It retrieves current EspoCRM metadata, which can be reviewed alongside the release. It does not compare versions, test the extension, or change CRM configuration.
Will the report include EspoCRM user details?
The metadata action may return user details as part of its response. Instruct Notis to omit unnecessary personal details from the run report and share only the configuration context needed for review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Espocrm. A trigger fires from one place; an action lands in another.
GitHub triggers
Espocrm actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get App User
Tool to retrieve current user data including token, acl, and preferences. use after successful authentication to fetch session-specific profile.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Metadata
Tool to retrieve metadata information from espocrm. use when you need to discover system configuration, user details, acl, and translations right after authentication.
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Connect any two apps with Notis in the middle.
GitHub and Espocrm, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Espocrm.