Pause, resume, or remove an integration

For: An admin during a vendor change, an audit, a contract renewal, or an off-boarding.

You’ll accomplish: understanding the difference between pausing, disabling, and removing an integration, knowing what happens to your data and webhooks in each case, and off-boarding cleanly with an export first.

These are the three things you can do to an integration’s lifecycle, from gentlest to most permanent. The differences matter, because one of them deletes data and the others don’t.

Only admins can pause, resume, or remove an integration. (Members can connect a new one, but not change the lifecycle of an existing one. See Invite teammates and assign roles.)

---

1. The three actions, in plain terms

• Pause — Stops syncing. PropSocket stops pulling new changes from your PMS, but everything already synced stays exactly where it is. Fully reversible: resume and it picks back up. You click Pause in the integration’s header, and its status badge changes to disabled.
• Resume — Turns syncing back on. You click Resume in the header; the integration goes back to active and catches up to your PMS on the next sync.
• Delete — Takes the integration out entirely. This is the permanent one, it lives in the integration’s Settings tab (not the header), and it has data implications — read section 4 before you do it.

If your goal is “stop syncing this for a while,” you want pause, not remove. Removing is only for “we’re done with this PMS connection for good.”

2. Pause (and resume) an integration

To pause:

1. Open the integration.
2. Click Pause in the header.
3. Confirm the prompt (“Pause this integration? All syncing will stop.”). The status badge changes to disabled and scheduled syncs stop.

While paused:

• Your synced data stays put. It’s still readable in the dashboard and via the API — it just stops getting fresher. It reflects your PMS as of the last successful sync before you paused.
• Scheduled syncs don’t run, so the “last successful sync” time will get older the longer it’s paused. That’s expected, not a fault.

To resume: open the integration and click Resume in the header, then confirm the prompt (“Resume this integration? Scheduled syncs will restart.”). It returns to active and the next sync catches it up to your PMS.

Pause is the right tool during a planned PMS maintenance window, a billing review, or any time you want to deliberately freeze data without losing it.

3. What happens to webhooks when you pause

When an integration is paused, it isn’t pulling new changes, so there are no new events to send — your webhook subscriptions go quiet, but they aren’t deleted. When you resume, the subscriptions are still configured and start sending again as new changes come in. You don’t have to rebuild them.

If your downstream systems alert on “no events received,” let those teams know about a planned pause so they don’t treat the quiet as an outage.

4. Remove an integration — read this first

Removing is permanent and has consequences you can’t undo from the dashboard:

• The integration’s synced data is deleted. Removing the integration removes the property, unit, resident, and lease records that came through it. This is not a soft “marked as deleted” — it’s the connection and its data going away.
• Webhook subscriptions on that integration are removed too. Your downstream systems stop receiving events from it.
• The stored PMS credentials are deleted. PropSocket permanently deletes the credentials it held for that connection immediately when you remove the integration.

Because removal deletes data, export anything you need to keep first (section 5).

To remove: open the integration, go to the Settings tab, and under Danger Zone click Delete Integration. This opens a confirmation page that lists exactly what will be deleted — the counts of properties, units, residents, leases, sync jobs, and webhook subscriptions — and you confirm there. That itemized confirmation is intentional.

5. Off-boarding: export before you remove

If you’re leaving a PMS, switching vendors, or ending your PropSocket use, do this in order so you don’t lose anything you’ll want later:

1. Export the data you need. There’s no export button on the integration itself — exports run through the Automations section (available on the Growth plan and above). Create an automation that exports the data model you want to keep (properties, units, residents, or leases) as a CSV, scope it to the integration you’re off-boarding, and use Run Now to pull a one-time copy. See Schedule data exports with Automations for the full walkthrough. The file is delivered to an FTP/SFTP destination you configure, not downloaded to your computer, so you’ll need those destination details. If you’re on the Starter plan, don’t have destination details, or aren’t sure how to set this up, ask support and we’ll walk you through it.
2. Confirm the export landed and is readable — check that the CSV arrived at your destination and spot-check a few records.
3. Then remove the integration (section 4).

If you’re off-boarding because you’re canceling PropSocket entirely, the same order applies, and there’s a defined retention and deletion timeline for your data — ask support and see your contract’s data-handling terms for the specifics.

6. Safely re-authorizing after a credential change

You don’t need to remove and rebuild an integration just because a PMS password rotated. Re-authorizing keeps the integration, its history, and its webhooks intact:

1. Get fresh, working credentials from your PMS administrator.
2. Open the integration, go to the Settings tab, and in the Credentials card click Update. Re-enter the credentials and save — PropSocket re-encrypts them on save and confirms with “Credentials updated successfully.”
3. Run a manual sync and confirm it reaches completed.

If the new credentials don’t have access to something the old ones did, PropSocket shows an amber warning after you save, listing the enabled services that are no longer accessible. If you see it, the new credentials are missing a permission the old ones had — go back to your PMS administrator and make sure the account is authorized for those services before relying on the sync.

This is the right move when a sync started failing on authentication — see What to do when a sync fails. Removing the integration would throw away your data and webhooks for no reason; re-authorizing fixes the credentials without disturbing anything else.

---

If this didn’t work

If a pause won’t take, a resume doesn’t restart syncing, or you need help exporting before a removal, reach out before you remove anything irreversible.

Open a support ticket by emailing support@propsocket.io and include:

• Organization slug (the short name in your dashboard URL, e.g. acme-residential)
• Integration Name (shown on the integration’s page)
• What you’re trying to do (pause, resume, remove, export-then-remove)
• What you expected vs. what you saw
• A screenshot of the integration’s status

Please do not paste your PMS password or API keys into the ticket. If you’re planning a removal and want to be sure you’ve exported everything first, say so — we’d much rather help you check before the data is gone than after.