Scriptera
Microsoft Teams and Salesforce automations — Development & IT
Ready-made scenarios where Microsoft Teams and Salesforce work for you (development & it): pick one — a copy appears in your account and runs on its own.
35 scenarios
- New file in a Salesforce folder — a Microsoft Teams message
- New issues in Salesforce — tasks in Microsoft Teams
- Cutting a release with a chat command
- Incident alerts — to everyone, everywhere at once
- High-priority tickets alert every channel at once
- Instant alerts for urgent events from your apps
- Auto-cleanup of old files in cloud storage — with notifications
- Automatic bug triage: priority, ticket, team alert
- Urgent tasks that don't stall
- Pre-release readiness checks — on autopilot
- Bug reports turned into proper tickets
- Data-load failure monitoring with tasks and alerts
- Repo changes from chat, in plain words
- Daily scenario backups to a code store
- New-issue triage: task, notification, reply to the author, and a logged row
- A daily access check: two-factor and stale keys
- Critical bugs from testing escalated straight to tickets and engineering chat
- Release notes, a QA task and team alerts — straight from a version tag
- Error-log watch with automatic tickets
- Failed-login detection with tickets and alerts
- Release notes from closed tasks — into oneC and Microsoft Teams on their own
- Jira epic health tracking with risk alerts
- Twice-daily double backup of your scenarios
- Weekly documentation and backup of your scenarios
- A daily backup of your scenarios — to Salesforce
- Turn security-scanner findings into tasks — no duplicates
- Scenario backups to a repo via pull request
- Incident response — ticket, alert, and report in seconds
- Release notes from closed tasks — published everywhere at once
- Change request routing: tickets, audit trail and notifications
- Route change requests by the rules — no manual triage
- Back up your scenarios to Salesforce
- Scenario backups in your Salesforce — with a report in your Microsoft Teams
- Backups of your scenarios — with a change history
- Response to a leaked access key — deactivate and lock down
