Share via

Receptful (Preview)

  • Reference

Receptful visitor management software helps bring stability to your front desk, know who’s in your office, and takes repetitive tasks like guest check-in notifications off of your team’s plate. Whether all you need is a digital logbook to track who enters your workplace, or would like to notify your employees when a guest has arrived, Receptful makes it possible. The Receptful connector makes it possible to integrate visitor data into your services.

This connector is available in the following products and regions:

Service Class Regions
Logic Apps Standard All Logic Apps regions except the following:
     -   Azure Government regions
     -   Azure China regions
     -   US Department of Defense (DoD)
Power Automate Premium All Power Automate regions except the following:
     -   US Government (GCC)
     -   US Government (GCC High)
     -   China Cloud operated by 21Vianet
     -   US Department of Defense (DoD)
Power Apps Premium All Power Apps regions except the following:
     -   US Government (GCC)
     -   US Government (GCC High)
     -   China Cloud operated by 21Vianet
     -   US Department of Defense (DoD)
Contact
Name Receptful Support
Email support@receptful.com
Connector Metadata
Publisher Los Trigos, Inc
Website https://www.receptful.com
Privacy policy https://www.receptful.com/privacy
Categories Productivity

Receptful Connector

The Receptful Connector provides triggers for all events regarding visitors. This is meant as a means to create any sort of integrations based off of your visitors interactions.

Prerequisites

You will need the following to proceed:

  • A Receptful account
  • Permission to create an API key

API Key

The API key will need to be generated in the Receptful portal. The API key for the connector will need to be in the following format:

Bearer API_KEY

Visit Events

The connector will emit triggers to a Power Automate flow with the following events:

  • checked_in - when a visitor checks in.
  • checked_out - Triggered when a visitor checks out.
  • delivered - Triggered hen a package is delivered.
  • discarded - Triggered when a visit record is soft deleted.
  • incinerated - Triggered when a visit record is permanently deleted.

Visit Event Conditions

When configuring a trigger, you will be able to set filters for when you want the workflow to be triggered. These conditions will be anded together, so make sure the result of the conditions is valid.

You can filter by:

  • Button
  • Configuration
  • Location
  • Region

Creating a connection

The connector supports the following authentication types:
Default Parameters for creating connection. All regions Not shareable

Default

Applicable: All regions

Parameters for creating connection.

This is not shareable connection. If the power app is shared with another user, another user will be prompted to create new connection explicitly.

Name Type Description Required
API Key securestring The API Key for this api True

Throttling Limits

Name Calls Renewal Period
API calls per connection 100 60 seconds

Triggers

Create a Webhook for Visit events

Registers a visit event webhook.

Create a Webhook for Visit events

Operation ID:
VisitEvents

Registers a visit event webhook.

Parameters

Name Key Required Type Description
Event
 event True string

What type of visit event do you want to trigger the webhook.
Region
 region_id string

Only trigger webhooks for visits with this region.
Location
 location_id string

Only trigger webhooks for visits with this location.
Button
 button_id string

Only trigger webhooks for visits with this button.
Configuration
 config_id string

Only trigger webhooks for visits with this configuration.

Returns

The outputs of this operation are dynamic.