Template Catalog¶

Audience: Everyone / Developers · Tags: template, flow, reference

A template is a ready-made starter flow definition you can install instead of building one from scratch — pick one, install its required connectors, fill in the specifics, and activate. Seven templates exist today. Each entry below shows its id, what it does, which connectors it needs, and its full definition JSON exactly as installed.

For how to install and customize a template, see Flow Templates. For what the fields in a definition mean, see Flow Validation.

1. Webhook → Slack Message¶

id: webhook-to-slack
Description: When a webhook fires, post a message to a Slack channel.
Category: notifications
Required connectors: Slack
Good for: getting notified the moment a webhook fires.

{
  "trigger": {
    "key": "trigger",
    "connectorKey": "webhook",
    "triggerType": "webhook"
  },
  "actions": [
    {
      "key": "notify",
      "connectorKey": "slack",
      "actionType": "send_message",
      "input": {
        "channel": "C0000000",
        "text": "New event received"
      }
    }
  ]
}

2. Webhook → Teams Message¶

id: webhook-to-teams
Description: When a webhook fires, send a message to a Microsoft Teams channel.
Category: notifications
Required connectors: Teams
Good for: routing webhook events into a Teams channel your team already watches.

{
  "trigger": {
    "key": "trigger",
    "connectorKey": "webhook",
    "triggerType": "webhook"
  },
  "actions": [
    {
      "key": "notify",
      "connectorKey": "teams",
      "actionType": "send_message",
      "input": {
        "teamId": "TEAM",
        "channelId": "CHANNEL",
        "text": "New event received"
      }
    }
  ]
}

3. Webhook → HubSpot Create Contact¶

id: webhook-to-hubspot
Description: When a webhook fires, create a contact in HubSpot.
Category: crm
Required connectors: HubSpot
Good for: turning an inbound signal (a form submit, a sign-up event) directly into a CRM contact.

{
  "trigger": {
    "key": "trigger",
    "connectorKey": "webhook",
    "triggerType": "webhook"
  },
  "actions": [
    {
      "key": "create",
      "connectorKey": "hubspot",
      "actionType": "create_contact",
      "input": {
        "properties": {
          "email": "lead@example.com"
        }
      }
    }
  ]
}

4. HubSpot Lead → Slack Alert¶

id: hubspot-lead-to-slack
Description: Create a HubSpot contact then alert sales in Slack — the classic lead-alert flow.
Category: sales
Required connectors: HubSpot, Slack
Good for: making sure sales never misses a new lead.

{
  "trigger": {
    "key": "trigger",
    "connectorKey": "webhook",
    "triggerType": "webhook"
  },
  "actions": [
    {
      "key": "create",
      "connectorKey": "hubspot",
      "actionType": "create_contact",
      "input": {
        "properties": {
          "email": "lead@example.com"
        }
      }
    },
    {
      "key": "notify",
      "connectorKey": "slack",
      "actionType": "send_message",
      "input": {
        "channel": "C0000000",
        "text": "New lead created in HubSpot"
      }
    }
  ]
}

5. HubSpot Contact → Teams Message¶

id: hubspot-to-teams
Description: Create a HubSpot contact then notify a Teams channel.
Category: sales
Required connectors: HubSpot, Teams
Good for: teams that live in Microsoft Teams instead of Slack getting the same lead-alert pattern.

{
  "trigger": {
    "key": "trigger",
    "connectorKey": "webhook",
    "triggerType": "webhook"
  },
  "actions": [
    {
      "key": "create",
      "connectorKey": "hubspot",
      "actionType": "create_contact",
      "input": {
        "properties": {
          "email": "lead@example.com"
        }
      }
    },
    {
      "key": "notify",
      "connectorKey": "teams",
      "actionType": "send_message",
      "input": {
        "teamId": "TEAM",
        "channelId": "CHANNEL",
        "text": "New contact created"
      }
    }
  ]
}

6. REST → Slack Message¶

id: rest-to-slack
Description: Call a REST endpoint then post the outcome to Slack.
Category: notifications
Required connectors: REST, Slack
Good for: checking an external API (e.g. a status endpoint) and posting the result where your team will see it.

{
  "trigger": {
    "key": "trigger",
    "connectorKey": "webhook",
    "triggerType": "webhook"
  },
  "actions": [
    {
      "key": "call",
      "connectorKey": "rest_sdk",
      "actionType": "request",
      "input": {
        "url": "https://api.example.com/status",
        "method": "GET"
      }
    },
    {
      "key": "notify",
      "connectorKey": "slack",
      "actionType": "send_message",
      "input": {
        "channel": "C0000000",
        "text": "REST call complete"
      }
    }
  ]
}

7. REST → Teams Message¶

id: rest-to-teams
Description: Call a REST endpoint then notify a Teams channel.
Category: notifications
Required connectors: REST, Teams
Good for: the same REST-check-and-notify pattern, for teams standardized on Microsoft Teams.

{
  "trigger": {
    "key": "trigger",
    "connectorKey": "webhook",
    "triggerType": "webhook"
  },
  "actions": [
    {
      "key": "call",
      "connectorKey": "rest_sdk",
      "actionType": "request",
      "input": {
        "url": "https://api.example.com/status",
        "method": "GET"
      }
    },
    {
      "key": "notify",
      "connectorKey": "teams",
      "actionType": "send_message",
      "input": {
        "teamId": "TEAM",
        "channelId": "CHANNEL",
        "text": "REST call complete"
      }
    }
  ]
}

How to use a template¶

Browse this catalog or Flows → from a template in the app.
Pick one — note its required connectors.
Install any missing connectors from the Marketplace.
Replace the placeholder values (channel IDs, team/channel IDs, URLs, sample email addresses) with your own.
Validate and activate.

Every template's trigger is a webhook — after installing and activating, POST to the flow's webhook URL to fire it.

Related: Flow Templates · Creating Flows · Glossary · Flow Validation