Auto-Clear Caches on Account Updates
When account data changes in Salesforce, stale build caches in GitHub can cause inconsistent deployments. Notis clears those caches automatically so every build starts fresh—no more mysterious failures from cached data.
Trigger
Account Created or Updated
Triggers when an Account is created or updated in Salesforce. Uses LastModifiedDate high-watermark to capture both creations and updates.
Action
Clear repository cache by key
Deletes github actions caches from a repository matching a specific `key` and an optional git `ref`, used to manage storage or clear outdated/corrupted caches; the action succeeds even if no matching caches are found to delete.
Why this helps
Stale build caches cause intermittent failures that are hard to debug, especially after account or configuration changes.
- Ensure builds don't use stale cached data after account changes
- Reduce mysterious CI/CD failures from cache inconsistencies
- Automate cache cleanup without manual intervention
- Keep builds predictable and reliable across account updates
Setup
Build it in a few focused steps.
- 1Connect Salesforce and GitHub to Notis
- 2Ask Notis: 'When an account is updated in Salesforce, clear GitHub Actions caches in [repo-name] to ensure fresh builds'
- 3Specify which account changes trigger cache clears (all updates, or specific fields)
- 4Choose your notification settings
- 5Test by updating an account in Salesforce and verify caches are cleared in GitHub
Questions about this workflow
Will this slow down my builds?
Initially, cleared caches mean the first build starts from scratch. Subsequent builds will rebuild the cache. The tradeoff is correctness over speed.
Can I clear only specific caches?
Yes. Ask Notis to clear caches by key or branch to be more targeted.
How often should I clear caches?
This automation handles it on account changes. You can also ask Notis to set up a recurring schedule.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Salesforce to GitHub. A trigger fires from one place; an action lands in another.
Salesforce triggers
GitHub actions
Account Created or Updated
Triggers when an Account is created or updated in Salesforce. Uses LastModifiedDate high-watermark to capture both creations and updates.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Contact Updated
Triggers when an existing Salesforce Contact record is modified. Emits changed fields alongside relevant timestamps.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
Record Updated (Generic SObject)
Triggers when monitored fields change on any Salesforce SObject. You specify the SObject type and which field values should be returned in the payload. The trigger uses SystemModstamp to detect changes regardless of which specific field changed.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
New Contact Trigger
Triggers when a new Contact is Created in Salesforce.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
New Lead Trigger
Triggers when a new Lead is created in Salesforce.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
New or Updated Opportunity
Triggers when a Salesforce Opportunity is created or updated.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Task Created or Completed
Triggers when a Task is created or when its status changes to Completed in Salesforce. Supports optional filtering by task Status or Subject.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Not just Salesforce and GitHub. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business GitHub.