The status of the feature request you'd like to monitor.

We use this to differentiate between paying customers & free triallers. Should be the string "true" or "false".

Your unique identifier for the end user. Usually not equal to the account.id, unless all your customers are individuals.

When the account was created. Dates should be serialised in the form yyyy-MM-ddTHH:mm:ss.SSSZ.

The monthly value of the account to you. We use this to help prioritise feature requests. Usually, but not always, a financial value, but feel free to use your own definition of value. Should be a number formatted to two decimal places.

The account name, usually a company name.

When the end user was created. Dates should be serialised in the form yyyy-MM-ddTHH:mm:ss.SSSZ.

The account return URL. We link to this URL to let your customer return from Receptive to your app. This may be different for each of your customer accounts.

Currently only accepts the value "endUser".

Pendo Feedback is a platform that helps SaaS companies manage product feedback and requests from their customers and team.

Pendo Feedback

The ID for the user, team, or workspace that you would like to get update notifications for. If blank, will be for the owner of the API key used to connect Zapier.

The ID for the user who's teammates should trigger the update.

Action items from private topics may contain sensitive data, so be careful where you send them.

The user id who's teams should be monitored. If blank, the API Key owner will be used.

When not using an email address, the integration provider to use when looking up a user.

The user id of the user's linked account on the integration provider.

Unique identifier used for de-duplication of suggestions.

Where to users are taken when they open the suggestion.

What action caused this suggestion to be generated.

Display text for the integration provider that should be used to display this suggestion.

Lower-case identifier that is used to group suggestions and perform analysis.

If specified, the Range user who should receive the suggestion. If blank, the owner of the API Key will receive the suggestion.

The Range user to attribute the interaction to, if blank will default to the API token owner.

Unique identifier within the source system. (source_id + provider) should be unique within the workspace.

Short, lowercase string which identifies the attachment provider. e.g. "github", "calendar", "dropbox". Attachments will be collated by provider.

Display name for the provider. e.g. "GitHub", "Dropbox Paper", "Google Calendar"

For types FILE and DOCUMENT, a set of subtypes are available.

Longer form field associated with the attachment.

A URL that allows direct navigation to the attachment

A logic parent for the attachment, for example a project, folder, or collection

A URL to directly navigate to the parent.

Range is an app that takes the work out of daily team check-ins by running virtual stand-ups and connecting all your tools so you can stay in sync, and feel more like a team.

Range

Activate this integration to automatically record request status changes in Pendo Feedback as interactions in your Range check-ins.

Pendo Feedback + Range

Record Range interactions from new request status changes in Pendo Feedback

Supported triggers and actions

New Comment on Request

Request Status Changed

New Check-In

New Meeting Action

Record Interaction

Find User

New Request

List Meetings

New Check-In by Teammate

Joined Team

User Info

About Pendo Feedback

Related categories

About Range

Related categories

Related Zap Templates

Related Zap Templates