Connections

Before connecting #

Ask the deployment administrator to install the organization’s authorized provider credentials on the server and give you a credential reference, such as primary. Enter only that reference in the console. This version has no self-service OAuth sign-in or secret upload form.

Google Calendar and Calendly support live scheduling. Resend and SMTP support plain-text outbound email. External webhooks can connect registered actions to your own server, and Custom actions supports approved named operations. Clinical system remains unavailable in this connection form. See Sending email and External webhooks & custom actions for exact setup.

Connect Google Calendar #

1. Under Connect a system, choose System: Calendar and Provider: Google Calendar.
2. Enter What your team calls it, such as Main scheduling calendar.
3. Enter the installed Credential reference. It must start with a letter and use letters, numbers, or underscores.
4. Enter the Calendar ID supplied by the administrator. Use primary only when it is correct for the authorized credential.
5. Set Default appointment length in minutes (5–480).
6. Set the Scheduling time zone using an identifier such as America/New_York.
7. Choose Verify and connect.
8. Confirm that the calendar card shows Verified connection, then test the needed scheduling action and inspect the provider’s records.

Connect Calendly #

1. Choose System: Calendar and Provider: Calendly.
2. Enter the display name and installed credential reference.
3. Enter the full Calendly event type URI supplied by the administrator; it is an API event-type URI, not the public booking-page URL.
4. Enter the Scheduling time zone.
5. Choose Verify and connect and check its result.
6. Confirm that the specific lookup, booking, or supported cancellation flow works for the authorized account.

This implementation requires the account to have appropriate Scheduling API access for booking. Calendly rescheduling needs a staff member in Calendly. Validate provider permissions and account capabilities with your administrator before promising a live workflow.

Interpret connection status #

Simulations are permitted only when an administrator enables them on a development or test server. Production and staging disallow simulated integrations.

Replace or disconnect a connection #

1. Review which actions depend on the current connection.
2. Choose Disconnect beside that connection.
3. Wait for the confirmation and check the updated card.
4. Configure and verify its replacement if needed.
5. Retest the affected workflow.