Skip to content

Microsoft Teams

Connect WPsigner with Microsoft Teams to receive rich signing notifications as Adaptive Cards in your team channels.

Use Cases

Section titled “Use Cases”
ScenarioDescription
Team visibilityKeep your entire team informed about document signing progress in a shared channel
Manager oversightLet managers track who has signed and who is still pending without leaving Teams
Sales workflowsNotify the sales channel the moment a contract is fully executed
HR onboardingAlert HR when a new hire completes their employment agreement
Compliance trackingMaintain a real-time audit trail of signing events in a dedicated compliance channel
Quick actionUse Adaptive Card buttons to jump directly to the document management page

Prerequisites

Section titled “Prerequisites”
  • A Microsoft Teams workspace
  • Permission to add connectors to a channel
  • WPsigner v2.1.0 or later

Compatibility

Section titled “Compatibility”
ComponentMinimum VersionRecommended
WPsigner2.1.0Latest
WordPress5.86.4+
PHP7.48.1+
Microsoft TeamsAny current planMicrosoft 365 Business
Adaptive Cards1.21.2
TLS1.21.3
PHP Extensionscurl, jsoncurl, json, openssl

Setup Guide

Section titled “Setup Guide”

1. Open Microsoft Teams

Section titled “1. Open Microsoft Teams”

Navigate to the channel where you want to receive document signing notifications.

2. Add Incoming Webhook

Section titled “2. Add Incoming Webhook”
  1. Click the … menu next to the channel name
  2. Select Connectors (or Manage channel → Connectors)
  3. Find Incoming Webhook and click Configure

3. Name Your Webhook

Section titled “3. Name Your Webhook”
  1. Enter “WPsigner” as the name
  2. Optionally upload a custom icon
  3. Click Create
  4. Copy the webhook URL — you’ll need it in the next step

4. Configure WPsigner

Section titled “4. Configure WPsigner”
  1. Go to WPsigner → Integrations
  2. Click Microsoft Teams
  3. Paste the Webhook URL
  4. Enter a Channel Name label (for your reference)
  5. Click Test Connection — check your Teams channel for a confirmation card
  6. Toggle Enable on
  7. Click Save Settings

Notification Events

Section titled “Notification Events”
EventTriggerCard Content
Signing RequestSigner added to documentDocument name, signer details, View button
Document SignedSigner completes signatureWho signed, progress count (e.g., 2/3)
All CompleteAll signers finishedAll signer names, Download button

Adaptive Cards

Section titled “Adaptive Cards”

WPsigner sends notifications as Adaptive Cards v1.2, which render natively in Microsoft Teams with:

  • Bold titles with status indicators
  • FactSet blocks with structured key-value data
  • Action buttons (OpenUrl) linking to document management pages

Developer Hooks

Section titled “Developer Hooks”

WPsigner fires the following WordPress action hooks during the signing lifecycle. You can use these to extend the Teams integration or build custom notification logic.

HookTriggerParameters
wps_signer_createdA signer is assigned to a document$signer_id, $document_id
wps_after_document_signedA signer completes their signature$signer_id, $document_id
wps_document_completedAll signers have signed the document$document_id
add_action( 'wps_document_completed', function( $document_id ) {
    // Custom logic when all signers have completed
    $document = wps_get_document( $document_id );
    // e.g., notify a different Teams channel or update a CRM
});

Security

Section titled “Security”
MeasureDetails
Webhook URLEncrypted at rest (AES-256-GCM)
Domain validationMust be on *.webhook.office.com
AJAX SecurityNonce + capability check + rate limiting
Rate Limiting5 tests/min, 10 saves/min per user
Payload SizeEnforced 28KB maximum
API Rate Limit4 requests/second (Teams enforced)

Troubleshooting

Section titled “Troubleshooting”

”Invalid webhook URL”

Section titled “”Invalid webhook URL””
  • URL must start with https:// and be on the webhook.office.com domain
  • Re-copy from Teams — URLs expire if the connector is deleted

No card appears in channel

Section titled “No card appears in channel”
  • Check you’re testing in the correct channel
  • Verify the webhook connector is still active

Card looks plain (no formatting)

Section titled “Card looks plain (no formatting)”
  • Adaptive Cards require Teams desktop or web client
  • Mobile clients may render cards with reduced formatting

Comparison

Section titled “Comparison”
FeatureTeamsSlackTelegramTwilio SMS
FormatAdaptive CardsBlock KitHTMLPlain text
AuthWebhook URLWebhook URLBot TokenAPI Key
CostFreeFreeFreePer message
Action buttonsYes (OpenUrl)Yes (Block actions)Yes (Inline keyboard)No
Progress trackingYes (FactSet)Yes (Sections)Yes (HTML)No

Next Steps

Section titled “Next Steps”