Turn overdue Bitbucket pull request follow-ups into Salesforce tasks
Set a recurring check to surface pull requests that need a human follow-up. Notis can create Salesforce tasks from the context you provide and tell you what it completed.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Create task
Creates a new task in salesforce to track activities, to-dos, and follow-ups related to contacts, leads, or other records.
Why this helps
Pull requests awaiting decisions can disappear from view while the team is focused on customer work.
- Put follow-up work into the CRM workflow
- Reduce repeated manual checks across tools
- See created tasks in a Notis run report
Setup
Build it in a few focused steps.
- 1Connect Bitbucket and Salesforce once in the Notis portal.
- 2Create an automation in Automations, New Automation, with a name and prompt.
- 3In one instruction, describe which supplied open pull requests need a Salesforce follow-up task and what the task should say.
- 4Pick a recurring schedule trigger and choose where run reports should go.
- 5Test with one real example of an open pull request and confirm the task details.
Questions about this workflow
Can Notis see all open pull requests automatically?
Only if Bitbucket context is available to the automation run. Supply the relevant pull request data or arrange for it to be available; do not assume an unlisted Bitbucket trigger exists.
What makes a pull request overdue?
Define the rule in your instruction or provide the age or due-date context. Notis cannot infer a missing baseline or history.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bitbucket to Salesforce. A trigger fires from one place; an action lands in another.
Bitbucket triggers
Salesforce actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Salesforce Account
Deprecated: creates a new salesforce account using a json post request, requiring 'name'; specific fields (e.g., custom, dunsnumber) may have org-level prerequisites.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add contact to campaign
Adds a contact to a campaign by creating a campaignmember record, allowing you to track campaign engagement.
Add lead to campaign
Adds a lead to a campaign by creating a campaignmember record, allowing you to track campaign engagement.
Add product to opportunity
Adds a product (line item) to an opportunity. the product must exist in a pricebook entry that's associated with the opportunity's pricebook.
Apply lead assignment rules
Applies configured lead assignment rules to a specific lead, automatically routing it to the appropriate owner based on your organization's rules.
Associate contact to account
Associates a contact with an account by updating the contact's accountid field.
Clone opportunity with products
Clones an opportunity and optionally its products (line items). creates a new opportunity with the same field values and products as the original.
Clone record
Creates a copy of an existing salesforce record by reading its data, removing system fields, and creating a new record. optionally apply field updates to the clone.
Connect any two apps with Notis in the middle.
Bitbucket and Salesforce, 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 Salesforce.