stackgate.ai
Browse workflows

Marketing and revenue operations teams

Lead qualification handoff with Typeform, HubSpot, Gmail, and Slack

Pull new Typeform lead responses, enrich or create HubSpot contacts, draft Gmail follow-ups, and alert the team in Slack.

Outcome: A qualified lead brief with CRM updates and a draft outreach message ready for approval

Integrations in this workflow

Typeform
HubSpot
Gmail
Slack

The problem

Lead forms live in Typeform while CRM follow-up happens in HubSpot, outreach drafts sit in Gmail, and the team expects Slack alerts. Copying response fields by hand loses context and slows qualification.

Example prompt

Using the private gateway, list recent Typeform forms and pull insights for our lead form. Find new responses that look like qualified leads, search HubSpot for matching contacts, create or update the contact if needed, draft a Gmail follow-up for my review, and post a short summary to #leads in Slack — do not send email or Slack until I approve.

Gateway tool bundle

Use namespaced tools on the private gateway (personal workspace) or business gateway (company workspace):

Typeform (read-first)

  • typeform__forms-public_list_forms → typeform__forms-public_get_form
  • typeform__insights-public_discover → typeform__insights-public_list for response analysis
  • typeform__workspaces-list_workspaces when you need to scope by workspace
  • Enable write tools in Typeform preferences only if agents should edit forms or contacts upstream

HubSpot

  • hubspot__search_contacts → hubspot__get_contact
  • hubspot__create_contact / hubspot__update_contact after explicit approval
  • hubspot__create_note to log qualification context

Gmail

  • gmail__list_messages → gmail__get_message for prior threads
  • gmail__send_message — draft or send only after approval

Slack

  • slack__list_channels → slack__send_channel_message for lead alerts

Start with list-services-tool or describe-service-tool to confirm which integrations are connected.

Token scope recommendations

  • Prefer read-first Typeform access (default after connect) plus HubSpot/Gmail/Slack scopes your team already uses.
  • Keep Typeform mutating tools disabled unless form builders need AI edits.
  • Scope API tokens to the gateways and integrations in use rather than *.

Safety notes

  • Typeform responses and HubSpot contacts often include PII — paste redacted summaries into public Slack channels.
  • Do not auto-send Gmail or Slack messages without an explicit human approval step in the prompt.
  • Recent Typeform responses can lag ~30 minutes on some upstream reads; prefer insights tools for trends.

Connect via private gateway

Activate the integrations above, create an API token scoped to mcp:private-gateway, then add this config to your MCP client.

Config file: ~/.cursor/mcp.json

{
    "mcpServers": {
        "stackgate-private-gateway": {
            "url": "https://stackgate.ai/mcp/private",
            "headers": {
                "Authorization": "Bearer YOUR_API_TOKEN"
            }
        }
    }
}