Connect Sally with Power Automate
By connecting Sally with Power Automate, you can automatically trigger flows whenever Sally events occur - for example, when a meeting summary is created. This allows you to continue automation in Microsoft 365 without manual steps.
If you’re new to webhooks, we recommend reading our full Webhook Guide, which explains in detail what they are and how they work.
Quick Navigation
1. Create a webhook in Sally
To send events from Sally to Power Automate, you first need to create a webhook inside Sally.
Steps:
- Open Settings in Sally from the left sidebar.
Go to Settings in Sally
- Navigate to Integrations and click "+ Add Integration".
Add a new integration
- From the list of integrations, choose Webhook and click "Create Webhook".
Select Webhook and create one
- Fill in the webhook details:
- Name: A clear label (e.g., Power Automate Connector).
- Trigger: Choose when the webhook should fire (e.g., Summary for appointment has been created).
- Organization Webhook: Decide whether it applies only to your meetings or to the entire organization.
- Webhook URL: Leave this empty for now — you’ll paste the URL from Power Automate later.
- Version: Always select 3 (Newest).
At the bottom of the form, Sally provides an example HTTP Body (JSON). Copy this JSON right away - you will need it later when configuring the schema in Power Automate.
Fill in the webhook form in Sally
- Click Create. Your webhook will now appear under "Your personal integrations".
Webhook successfully created in Sally
✅ At this point, Sally is ready to send events. Next, we’ll move on to Power Automate and configure a flow that listens for these webhook calls.
2. Set up the flow in Power Automate
Now that Sally is ready to send data, let’s create a flow in Power Automate that will listen to incoming webhooks and act on them.
Steps:
- In Power Automate, click Create and choose "Automated cloud flow".
Start with a new Automated cloud flow
- Enter a descriptive Flow name (e.g., Sally – Send email). Then click Skip to manually select a trigger.
Give your flow a clear name and skip trigger selection
- In the new flow, click "Add a trigger".
Add the trigger to your flow
- Search for HTTP and select "When an HTTP request is received".
Choose the HTTP request trigger
- Under "Request Body JSON Schema", click "Use sample payload to generate schema".
Use the copied JSON to generate the schema
- Paste the HTTP Body JSON you copied from Sally and click Done. This automatically generates the schema Power Automate will use to parse incoming Sally events.
Paste the JSON body from Sally
- Now you can adjust permissions (e.g., Who can trigger the flow) if needed.
Schema successfully generated
By pasting the JSON from Sally, you tell Power Automate the structure of incoming data. This makes it possible to use dynamic fields like summary, tasks, or decisions in later flow steps.
- Next, add a new Action to the flow.
Continue by adding your first action
ChatGPT:
- For this example, we used Send an email notification (V3) to send the meeting information by email — but of course, you can use any other action as well, e.g. creating a Planner task, posting a message in Teams, or adding a new row to an Excel file.
Choose Send an email notification (V3)
Configure the action details:
- To / Recipient: Define where the output should go (e.g., an email address, Teams channel, Planner, or another service).
- Subject / Title: Add a descriptive label like Tasks Meeting.
- Body / Content: Provide a short message or content (later you can insert dynamic fields coming from Sally).
Set recipient, subject, and body of the email
- Finally, click Save to store your flow.
Don’t forget to save your flow
✅ Your flow is now set up with a webhook trigger and a first action. In the next step, we’ll test the integration and confirm that data from Sally arrives correctly in Power Automate.
2.1. Test and debug the integration
Use Sally Logs to confirm that events reach Power Automate and to debug issues.
Steps:
- In Sally, open Settings → Integrations.
- Under "Your personal integrations", find your webhook (e.g., Power Automate Connector) and click Logs.
Access the integration logs in Sally
- Once your selected trigger fires, the executions appear here. Click Details on any row to inspect the payload and response.
View webhook executions and statuses
Each log entry shows:
- Execution time – when Sally sent the event
- Target endpoint – the Power Automate webhook URL
- HTTP status – response from Power Automate (e.g.,
202 Accepted
)
Use logs to confirm delivery, inspect payloads, and debug errors.
If something doesn’t work in Power Automate, check the Sally logs first to ensure the event was sent correctly.
3. Use ready-made Templates
Instead of building a flow from scratch, you can also use ready-made Power Automate templates provided by Sally.
These templates are available as ZIP files you can download in Sally and import directly into Power Automate.
This way, you save time and get started faster — just adapt the imported flow to your needs.
Steps:
- In Sally, go to Settings.
Open the Settings in Sally
- Go to Integrations. Under “Your personal integrations”, click on “+ Add Integration.”
View available templates for Power Automate
-
Select the template you want (e.g., Add the meeting summary to a HubSpot contact) and click Download Template.
This will download a ZIP file containing all necessary configuration files (including the JSON definitions).
You’ll import this ZIP into Power Automate in the next step.
Download the template ZIP file
- In Power Automate, go to My flows → Import → Import Package (Legacy).
Choose Import Package (Legacy) in Power Automate
- Click Upload to upload the ZIP file you downloaded from Sally.
Upload the downloaded template package
- Review the package details and click Import.
Review the flow package before importing
- Your new flow will now appear under My flows.
See the imported flow under My flows
✅ With templates, you can skip manual setup and get a working integration instantly. Just adjust the details (e.g., target system, fields) to fit your specific use case.