Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Heartbeat connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using `@activepieces/piece-heartbeat@0.2.0` and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

Heartbeat Integration & Workflow Automation

Connector

Heartbeat

Monitoring and alerting made easy

Get Started Talk to an Expert

Categorycommunication

Authenticationcustom

Objects2 supported

Actions2 supported

Technical ReferenceView technical reference

Overview

What you can do with Heartbeat.

Connected capability

Monitoring and alerting made easy

Technical Reference

Heartbeat

Monitoring and alerting made easy

View technical reference

Similar connectors

Continue exploring.

View all connectors

AI Answer

AI Answer connector package maintained by Flows360 CDK.View details

Azure Communication Services

Communication services from Microsoft AzureView details

Bland AI

AI phone calling platform for outbound and conversational voice workflows.View details

Bluesky

Bluesky connector package maintained by Flows360 CDK.View details

Next step

Connect Heartbeat through Flows360.

Talk through the connector, the systems around it and the outcome you need.

Get Started Talk to an Expert

Find the right connection faster.

What you can do with Heartbeat.

Connected capability

Heartbeat

Continue exploring.

Connect Heartbeat through Flows360.