Connect FSRevs to Make

The native FSRevs Make app can start a scenario from selected FSRevs activity, synchronize Customers, and send Review Requests or Custom Forms. It uses the same Integration API, permissions, identity rules, and sending protections as the FSRevs Zapier app.

Before connecting, complete the integration prerequisites. The connection owner needs API Access and access to the Locations and resources the scenario will use.

Connect your workspace

1. In FSRevs, open Integrations.
2. Choose Create Reusable Make Connection.
3. Copy the complete one-time Connection Key, including the numeric prefix and | character.
4. In Make, add an FSRevs module and choose Add next to Connection.
5. Enter the short workspace name from the beginning of your FSRevs URL. For https://acme.fsrevs.com, enter acme.
6. Paste the complete Connection Key and save the connection.
7. Close the FSRevs key dialog only after Make accepts the connection.

The Connection Key is shown once

FSRevs cannot display the plaintext key again. If it is lost or exposed, replace the Make Connection credential under Integrations → API Access, then reconnect affected scenarios. Replacing the key stops triggers created by the old key. Events during the reconnect gap are not automatically replayed.

One Make Connection can be reused across scenarios. It remains limited by its owner’s current FSRevs permissions, API Access, workspace features, sending settings, quotas, and safety limits.

Available instant triggers

Make trigger	When it runs	Scope
Watch Custom Form Submissions	A permitted Custom Form is completed	All or selected Custom Forms
Watch New Customers	An FSRevs Customer is created	All currently readable Customers
Watch Customer Updates	A public Customer field changes	All currently readable Customers
Watch Review Requests Sent or Prepared	FSRevs queues delivery or prepares a message in a sender’s app	All or selected Review Flows
Watch New Review Responses	A Review Request is completed for the first time	All or selected Review Flows
Watch New Review Feedback	Written feedback is first recorded	All or selected Review Flows
Watch Review Destination Visits	A customer continues to a review destination	All or selected Review Flows

Make registers and removes the corresponding FSRevs webhook automatically. Choosing All includes eligible resources added later. Choosing selected resources limits delivery to those choices.

FSRevs may deliver the same webhook activity more than once. Repeated delivery keeps the same FSRevs Event ID; use that ID to prevent repeated downstream work. A trigger observes future matching events and does not import earlier activity when connected.

Trigger output includes immutable event information and the current resource that the connection may still read. A trigger stops rather than exposing a deleted or newly unauthorized resource.

For Watch Customer Updates, a public field means a field exposed through the authorized integration, not a publicly visible Customer profile. Watch Review Requests Sent or Prepared confirms queued FSRevs delivery or preparation in a team member’s app; neither proves delivery to the recipient. A Review Destination Visit records a handoff, not a confirmed posted review.

Test a trigger before activating the scenario

1. Connect the instant trigger and choose the intended Forms or Review Flows.
2. Put the scenario in its listening or test state.
3. Create one new matching activity in FSRevs, such as completing the selected Form with test details.
4. Inspect the resulting event and the mapped fields before enabling later actions.

If a later module sends a message, use a destination you control. Check the first-automation verification steps before activating repeated runs.

Create or update a Customer

Use Create or Update a Customer to synchronize Customer data without creating a request or sending a message.

For ongoing synchronization, map a stable source/account name and the source system’s stable Customer ID. Keep that pair unchanged so later executions update the same Customer. Map the source’s last-updated time when available to prevent an older delayed update from overwriting newer data.

FSRevs canonicalizes the source at the API boundary and returns the canonical value. Make sends the mapped value without maintaining a separate identity rule.

For one-off intake without a durable source ID, leave both source identity fields blank and provide an exact email address or phone number. Name alone cannot identify a Customer.

Send a Review Request

Select Location (used for sending) and a Review Flow, then explicitly map an email address, mobile number, or both. The Review Flow selector may ask for Location to find Review Flows because Make’s popup search does not inherit the outer field. That nested Location filters the search only; it does not change the sending Location, and the two values must agree.

Send a Custom Form

Select Location (used for sending) and an eligible Custom Form. The Form selector may ask for Location to filter Custom Forms; that nested value filters the popup search only and does not change the sending Location. A location-specific Form must agree with the sending Location, while an eligible global Form remains valid. IDs may still be mapped manually. Explicitly map an email address, mobile number, or both.

Running a send module sends a real message

Make’s module testing and scenario execution use the mapped destination. Use only approved destinations you control, and review every scenario before activating it.

The guided send modules do not expose sender overrides, provider selection, message templates, or duplicate-protection bypasses.

Make an API Call

Use Make an API Call for an authorized FSRevs V1 operation that does not have a dedicated module.

• Enter a relative path beginning with /v1/, such as /v1/connection.
• The module always uses the workspace and host from the saved FSRevs Connection.
• Absolute URLs and requests to another host are not accepted.
• The same connection abilities, permissions, throttles, and validation apply.

See the Integration API reference for supported operations and request bodies.

Understand retries and failures

• Validation, permission, missing-resource, quota, and sending-safety conflicts stop the current operation.
• FSRevs rate limits tell Make when the operation can be retried.
• Reconnecting does not fix API Access that an FSRevs administrator disabled.
• A timeout can be ambiguous: FSRevs may have accepted the operation before Make lost the response.
• Each write module has an optional advanced Operation ID. Map the same UUID when a resumed or deliberately retried execution must represent the same logical operation. A separate manual rerun is normally a new operation.
• Before repeating a sending action after a timeout, check FSRevs activity. Recent-send protection may stop a separate execution from contacting the same destination again.

Troubleshoot the connection

Make cannot connect
Confirm that Workspace contains only the short workspace name and that Connection Key contains the complete show-once value. Replace a revoked or exposed Make Connection in FSRevs.

A Connection Key was replaced or revoked

The old key no longer works and triggers created with it are stopped. Reconnect Make and reattach the intended instant triggers so Make creates fresh subscriptions. Events from the disconnected period are not backfilled.

A Location, Review Flow, or Custom Form is missing
Choices are bounded and searchable. Search by name, or map the resource ID when appropriate. The connection owner must currently be allowed to use the resource.

A trigger stopped
Confirm that the Make scenario and its attached FSRevs webhook still exist, the connection remains current, and the referenced resource is still readable.

A send was rejected as recent
Do not blindly retry. The earlier operation may already have been accepted. Check FSRevs activity first.

Related pages

• Integrations — Getting Started
• Customer Identity and Sending
• Create and verify webhooks
• Other Automation Platforms