Before You Start
- You need to be an account administrator in Integrate.io ETL. Service hooks are defined at the account level.
- In Microsoft Teams, you need permission to add a workflow to the channel that should receive the notifications.
- Use a standard channel. Workflows can’t post to private channels.
- Use a Workflows webhook URL. Office 365 connector “Incoming Webhook” URLs (
webhook.office.com) were retired by Microsoft and are rejected.
Get a Webhook URL in Microsoft Teams
1
In Microsoft Teams, open the channel that should receive notifications.
2
Select More options (…) next to the channel name, then select Workflows.
3
Choose the Send webhook alerts to a channel template, then follow the prompts and save the workflow.
4
Copy the webhook link the workflow shows when it is saved. You will paste it into Integrate.io ETL in the next section.
Create the Microsoft Teams Hook
1
Click your avatar, then click Account settings.
2
Click Service Hooks from the left pane menu.
3
Click + new hook.
4
In the list, choose Microsoft Teams.
5
Fill in the fields:
6
Select the events you want to be notified about:
- All Job Notifications: All events below.
- Job Submitted: Job was submitted by user or schedule for execution.
- Job Started: Job execution started.
- Job Stopped: Job stopped by user.
- Job Completed: Job completed successfully.
- Job Failed: Job completed with failure.
- All Cluster Notifications: All events below.
- Cluster Requested: Cluster creation requested by user or schedule.
- Cluster Available: Cluster is available and jobs can be run on it.
- Cluster Terminated: Cluster is terminated.
- Cluster Idled: No activity on the cluster for a specified interval.
- Cluster Error: Cluster error occurred and jobs can’t be executed on it.
- All Schedule Notifications: All events below.
- Schedule Created: Schedule was created.
- Schedule Activated: Schedule was enabled.
- Schedule Deactivated: Schedule was disabled.
- Schedule Deleted: Schedule was deleted.
- Schedule Skipped: A scheduled run was skipped and no job was created. See Service Hooks for details.
7
Optionally, limit the hook to specific packages or package groups. See Scoping hooks to packages or package groups for how filters are applied.
8
By default, the hook is created active, but you can disable it if you wish.
9
Click Create Service Hook to save your changes.
10
Trigger a ping to test the hook. A card titled Integrate.io is connected appears in the channel.
What the Cards Show
Titles are colored by outcome: failures and errors are red, completed jobs and available clusters are green, and stopped, idled, terminated, skipped, or deactivated events are amber.
Teams also adds a line under each card that names the person who created the workflow, in the form “[name] used a Workflow template to send this card”.
Teams limits a message to about 28 KB. If a job’s error message is very long, the card shortens it, and drops it entirely if needed. Use View job to read the full error.
Delivery and Retries
Integrate.io ETL does not follow redirects from the webhook URL.
FAQ
Q: Can I use an Office 365 connector “Incoming Webhook” URL? No. Microsoft retired Office 365 connectors, andwebhook.office.com URLs are rejected. Create a Workflows webhook with the Send webhook alerts to a channel template instead.
Q: Can I send notifications to more than one channel?
Yes. Create one Microsoft Teams hook per channel, each with that channel’s workflow URL. You can choose different events and package filters for each hook.
Q: I clicked ping but no card appeared. What should I check?
Open the workflow in Teams and confirm it is turned on and its run history shows the request. If the workflow was deleted or recreated, copy the new link and update the hook.
Q: Someone else may have seen our webhook URL. What should I do?
Delete the workflow in Teams, create a new one, and update the hook with the new URL. The old link stops working once the workflow is removed.