Skip to content

Messaging · Direct connection · Pro

Penny’s caller details reach the Microsoft Teams channel your office watches.

An existing customer wants a call about an estimate. Penny sends the summary and captured details through your Teams workflow, giving the office a card it can use to make the callback.

14 days of Pro included. No credit card.

The fields your office receives

Source fieldDestination
Event typeAdaptive Card heading
Call summaryCard text
Captured intake detailsLabelled facts in the card
Direction
Penny sends the card to the Teams Workflows webhook you configure for the destination channel or chat.
When it happens
After the relevant call event is processed. Teams handles the card’s delivery through the receiving workflow.

The connection posts notifications; Penny does not monitor Teams replies. A card does not mean a team member has accepted responsibility for the caller. Decide who watches the destination and follows up.

Set up the connection

  1. 1

    Create the receiving workflow

    In Teams Workflows, use the webhook-request trigger and configure the action that posts an Adaptive Card to the intended destination. Follow your Microsoft organization’s approval requirements.

  2. 2

    Check ownership and access

    Workflows belong to their owners. Add an appropriate co-owner for continuity and check who can view the destination. Configure the webhook authentication as required for Penny’s incoming request.

  3. 3

    Enter the workflow URL in Penny

    Open Microsoft Teams in Penny’s Integrations settings and save the generated webhook URL. Use the current Workflows setup described by Microsoft.

  4. 4

    Review a test card

    Leave a test message with Penny and check the resulting card. Verify the heading, summary, and captured details, then confirm who in the office will handle these notifications.

Required fields used to prepare intake for a connection
Prepare the intake your Microsoft Teams workflow needs. This is Penny’s existing required-fields control with sample data; the destination record is illustrated separately below.

Illustrative Microsoft Teams card

Heading
New message
Summary
Existing customer asks the office to call about an estimate
Preferred callback
Afternoon, as reported by caller
Customer name
Sample Caller
Sample Teams card: the caller’s request reaches the channel assigned to follow up.

Check the first result

Confirm that a test card posts successfully and that a second workflow owner can maintain the connection. Review the workflow’s run history if Teams has not posted the card.

Questions about this connection

Who should own the Teams workflow?

Assign an owner and an appropriate co-owner who can maintain the receiving workflow. Confirm the destination’s membership and test that it keeps working under your organization’s access rules.

How do I know the connection is ready?

Confirm that a test card posts successfully and that a second workflow owner can maintain the connection. Review the workflow’s run history if Teams has not posted the card.

Provider reference

Browse all connections