Marketplace

Use “Figma comment reply closure watcher timeout” in Recued. Low-frequency timeout role for the connected service. It moves a limited batch of expired rows from active to timedout, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

Use “Help Scout conversation reply closure watcher timeout” in Recued. Low-frequency timeout role for the connected service. It moves a limited batch of expired rows from active to timedout, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

Use “Intercom conversation reply closure watcher timeout” in Recued. Low-frequency timeout role for the connected service. It moves a limited batch of expired rows from active to timedout, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

Use “Front conversation reply reopen watcher timeout” in Recued. Low-frequency timeout role for the connected service. It moves a limited batch of expired rows from active to timedout, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

Use “PandaDoc document closure watcher timeout” in Recued. Low-frequency timeout role for the connected service. It moves a limited batch of expired rows from active to timedout, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

Use “DocuSign envelope closure watcher timeout” in Recued. Low-frequency timeout role for the connected service. It moves a limited batch of expired rows from active to timedout, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

Use “Google Drive file comment closure watcher timeout” in Recued. Low-frequency timeout role for the connected service. It moves a limited batch of expired rows from active to timedout, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

Use “Confluence inline comment reply closure watcher timeout” in Recued. Low-frequency timeout role for the connected service. It moves a limited batch of expired rows from active to timedout, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

Use “GitHub issue closure watcher timeout” in Recued. Low-frequency timeout role for the connected service. It moves a limited batch of expired rows from active to timedout, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

Use “Jira issue closure watcher timeout” in Recued. Low-frequency timeout role for the connected service. It moves a limited batch of expired rows from active to timedout, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

Use “Linear issue closure watcher timeout” in Recued. Low-frequency timeout role for the connected service. It moves a limited batch of expired rows from active to timedout, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

Use “GitHub issue comment closure watcher timeout” in Recued. Low-frequency timeout role for the connected service. It moves a limited batch of expired rows from active to timedout, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

Use “Jira issue comment closure watcher timeout” in Recued. Low-frequency timeout role for the connected service. It moves a limited batch of expired rows from active to timedout, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

Use “Linear issue comment closure watcher timeout” in Recued. Low-frequency timeout role for the connected service. It moves a limited batch of expired rows from active to timedout, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

Use “GitLab issue note closure watcher timeout” in Recued. Low-frequency timeout role for the connected service. It moves a limited batch of expired rows from active to timedout, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

Use “monday.com item update closure watcher timeout” in Recued. Low-frequency timeout role for the connected service. It moves a limited batch of expired rows from active to timedout, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

Use “Notion page comment closure watcher timeout” in Recued. Low-frequency timeout role for the connected service. It moves a limited batch of expired rows from active to timedout, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

Use “Azure DevOps pull request comment closure watcher timeout” in Recued. Low-frequency timeout role for the connected service. It moves a limited batch of expired rows from active to timedout, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

Use “Bitbucket pull request comment closure watcher timeout” in Recued. Low-frequency timeout role for the connected service. It moves a limited batch of expired rows from active to timedout, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

Use “Smartsheet row discussion closure watcher timeout” in Recued. Low-frequency timeout role for the connected service. It moves a limited batch of expired rows from active to timedout, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

Use “Asana task closure watcher timeout” in Recued. Low-frequency timeout role for the connected service. It moves a limited batch of expired rows from active to timedout, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

Use “ClickUp task closure watcher timeout” in Recued. Low-frequency timeout role for the connected service. It moves a limited batch of expired rows from active to timedout, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

Use “Gusto supported benefit directory” in Recued. It provides a focused, read-only view and leaves data in the connected service unchanged.

Use “Ashby survey form directory” in Recued. It provides a focused, read-only view and leaves data in the connected service unchanged.

Use “SurveyMonkey survey response digest” in Recued. It provides a scheduled, read-only SurveyMonkey response digest.

Use “Ashby survey submission directory” in Recued. It provides a focused, read-only view and leaves data in the connected service unchanged.

Use “Suspend a Neon compute endpoint” in Recued. It runs the Neon compute suspend workflow for one endpoint with approval before changes are made.

Use “Suspend an Okta user” in Recued. It runs the Okta user suspension for one user with approval before changes are made.

Use “Swap tier on subscription change” in Recued. When a Stripe subscription this server sold changes, converge the customer onto the tier their entitlements now say they hold.

Use “Sync a Microsoft Intune device” in Recued. It runs the Microsoft Intune device sync workflow for one managed device with approval before changes are made.

Use “MongoDB Atlas system status” in Recued. It provides a focused, read-only view and leaves data in the connected service unchanged.

Use “Coda table row brief” in Recued. It provides a read-only review brief for one Coda table.

Use “Samsara tag directory” in Recued. It provides a focused, read-only view and leaves data in the connected service unchanged.

Use “Statsig List Tags” in Recued. It provides a focused, read-only view and leaves data in the connected service unchanged.

Use “Ashby take-home assignment directory” in Recued. It provides a focused, read-only view and leaves data in the connected service unchanged.

Use “Statsig List Target Apps” in Recued. It provides a focused, read-only view and leaves data in the connected service unchanged.

Use “Asana task closure watcher” in Recued. It checks saved items on a schedule and updates them when the connected service reports a final status.

Use “ClickUp task closure watcher” in Recued. It checks saved items on a schedule and updates them when the connected service reports a final status.

Use “Google Task closure watcher” in Recued. It checks saved items on a schedule and updates them when the connected service reports a final status.

Use “Planner task closure watcher” in Recued. It checks saved items on a schedule and updates them when the connected service reports a final status.

Use “Todoist task closure watcher” in Recued. It checks saved items on a schedule and updates them when the connected service reports a final status.

Use “Asana task comment closure watcher” in Recued. It checks saved items on a schedule and updates them when the connected service reports a final status.

Use “ClickUp task comment closure watcher” in Recued. It checks saved items on a schedule and updates them when the connected service reports a final status.

Use “Todoist task comment closure watcher” in Recued. It checks saved items on a schedule and updates them when the connected service reports a final status.

Use “Coder AI task inventory” in Recued. It provides a focused, read-only view and leaves data in the connected service unchanged.

Use “Asana task and project brief” in Recued. It provides a read-only review brief for one Asana task and project.

Use “Todoist task and project brief” in Recued. It provides a read-only review brief for one Todoist task and project.

Use “ClickUp task review brief” in Recued. It provides a read-only review brief for one ClickUp task.