Guides

Connections

A connection is a saved, named way for your server to talk to an outside service. Set it up once, then grant it to each pack.

A connection is a saved way to talk to an outside service. It has a name. The service can be an API, like your CRM. It can be an MCP tool server. It can be a place that gets your notifications. Your server talks out to it.

A pack asks to use a connection by its name. You set up the secret key once. Then any pack you grant it to reuses it. The key is never copied into a recipe.

#Enroll a connection

Enroll means "set up and save". Open Connections and pick a provider. Or let a pack do it. A pack that needs a connection walks you through the setup while it installs.

Each connection is known by its kind and its name. So acme-hubspot and personal-hubspot are two different connections. Each one has its own grants. A grant is a yes you give ahead of time.

Your list and the Add button come first. Search by name, service, or status to find an account. The status bar shows saved sign-in problems. Open it for repair links and reminders to review access. Open Apps & APIs for more sign-in tools. Expand Authentication settings to find apps, brokers and bulk API moves.

A new API connection first asks How it signs in. Choose Recued direct OAuth, OAuth broker (Nango) or API key or token. Other ways are under Other ways to sign in. Mail and Calendar can lead you to the app or broker tools. When done, choose Return to mailbox setup for Mail. For Calendar, choose Return to calendar setup. This tab keeps the account name and form choices in memory. It does not carry passwords, app secrets or tokens.

#Repair a password account

Open the IMAP mailbox or CalDAV calendar you saved. Choose Update credentials. Enter the new password or app password. Choose Verify and save credentials. Recued checks the login first. It then saves the new password. The server, username and account name stay the same. So do the folders or calendars, saved data and sync point.

For mail with SMTP, you can change either password. Leave a field blank to keep the saved value. If SMTP has no password of its own, it uses IMAP's. No test mail is sent. A failed check keeps the saved passwords. Recued may save the passwords but fail to restart sync. If so, it asks you to restart the server.

#Browse and connect file sources

Connections → Files shows local folders and cloud file sources. Choose Connect cloud source to pick a service. Recued opens that service's setup form. Choose Browse files to open Data → Files. For local folders, find it in the folder's details. Choose Manage authentication to open the source's saved connection. A cloud file list can be out of date. That alone does not mean its sign-in has expired.

#Understand connection checks

Test connection checks whether the service replies. It shows any HTTP error too. A reply does not prove access to private data. It does not prove that all needed permissions were granted. Use the pack's read check for the data it needs. If the service cannot be reached, the key may still be valid.

#Reuse a saved OAuth app

This needs Recued 26.10.16 or later. Open Connections → Apps & APIs and add a Google or Microsoft API connection. Choose Use saved Google app or Use saved Microsoft app. Pick the saved app you want to use. You can save apps here, in Mail, or in Calendar. The choice appears when the OAuth sign-in addresses match that app's provider.

Check that the callback URL shown in this form is registered in your app. In Google, enable the API you plan to use. Review the scopes, choose Authorize, then choose Save and test. Each API connection gets its own sign-in and permissions. The app secret stays on your server. Choose Enter another app to use other app details. Use Refresh saved apps if you changed the saved app in another tab.

If the saved app's ID changes during setup, choose an app again. Do this too if you remove the app. Changing it later does not update a saved API connection's credentials. Use the connection's normal credential change flow for that.

#Save more than one OAuth app

In Connections, choose Apps & APIs. Expand Authentication settings. Choose Manage saved apps. Choose Add OAuth app. Pick Google or Microsoft. Give the app a name, such as Work or Personal. Enter its Client ID and secret, then choose Save app. The secret stays on your server. Recued never shows it again.

Your old Google and Microsoft apps stay as the default apps. Each new app has its own name and keys. Pick a saved app when you connect an API, Mail, or Calendar account. The app choice is separate from the account you sign in to.

Each saved app is one row. Open a row to see its buttons. With many apps, search by name, Client ID or account. Only eight show at first. Choose Show all for the rest.

Use Edit to change an app name or its expiry date. Use Usage and rotate secret to change its secret. Leave the secret blank to keep it. Mail and Calendar keep using their chosen app for token refresh. Changing a default app does not change other named apps. Saved API connections keep their own copy of the app keys. Use their credential change flow to replace those keys.

#Keep track of a secret's expiry date

In Connections, choose Apps & APIs. Expand Authentication settings. Choose Manage saved apps. Open the app's row, then choose Edit. If the vendor shows a date for its secret, copy it into Secret expiry date. Leave it blank if you do not know. Choose Save app. You do not need to enter the secret again.

Reminders show in Apps & APIs from 30 days before the date. They stay visible while the saved apps list is closed. The three soonest show first. Open the line below for the rest. The view updates as your local calendar day changes. A passed date does not prove that access has stopped. Recued does not look up or test this date. No date recorded means the date is unknown.

Choose Edit expiry date to fix or clear it. Use Clear expiry date to remove the date. This changes the date only. Choose Review usage and rotate secret to see the app's uses. Review the accounts and API copies before you change the secret.

When you rotate a secret, enter its new date if known. Leave the new date blank if unknown. You can also choose Clear new expiry date. A successful rotation clears the app's old date and reminder. Skipped API copies keep their old secret. Their expiry dates are not tracked here. An expiry reminder does not start sign-in or change access.

#Remove or change a saved app

Open the app's row and choose Remove, then Remove app. You cannot remove an app while Mail or Calendar uses it. You cannot change its Client ID then, either. Add a new app for a different Client ID. Microsoft Mail and Calendar must use the same app when they share one sign-in.

If you remove an app while its editor is open in another tab, refresh that tab. Its old draft cannot restore the app or replace new keys. If you save app keys in Mail or Calendar and then cancel consent, the app stays saved. You can retry sign-in without entering the secret again.

#See app usage and rotate a secret

This needs Recued 26.10.16 or later. In Connections, choose Apps & APIs. Expand Authentication settings. Choose Manage saved apps. Open the app's row, then choose Usage and rotate secret. Review its Mail, Calendar and API uses. Packs, recipes, schedules and file sources are shown when known. Missing usage is marked as unknown. Use this view to fix an app whose saved secret is missing too.

Make a new secret for that same app in the vendor console. Google’s reset stops the old secret at once. Some accounts may need a new sign-in. See Google’s reset guide. For Microsoft, add a new secret and keep the old one while you test. See Microsoft’s secret guide. Keep the Client ID the same. Paste the new secret into Recued. Add the new secret's expiry date if you know it. Leave it blank to clear the old date after the save. Confirmed API copies start checked; clear any you want to skip. Old copies with an unknown app start unchecked. Check those only after you review them. Copies that share one sign-in must stay together. Mail and Calendar using the app pick up its new secret when they renew.

#Apply a secret rotation

Choose Review rotation, then Apply secret rotation. Recued saves the app and checked copies in one step. Their names, accounts, scopes and sync state stay in place. Skipped copies keep their old secret. A failed save keeps the previous settings.

This save does not test the new secret with the vendor. For Microsoft, keep the old secret valid until renewals succeed. Then remove it in the vendor console. Update other tools that use this same app too. If the reply is lost, choose Check rotation result. It reads the saved result without repeating the change. If Recued confirms the rotation but cannot confirm its date, refresh the app. Use Edit expiry date to fix the date without changing the secret again.

#Verify a new app secret

In Manage saved apps, open the app's row and choose Verify token renewal. You can also choose it after a saved secret rotation. The first view reads local settings only. Choose which saved sign-ins to check, then choose Run renewal checks. Copies that share one sign-in stay together. The check uses the app secret saved now. It asks the vendor for a new token. A token from the cache cannot pass this check. Recued saves new tokens for normal use. It requests no new scopes.

Old secret copies and copies with no known app are left unchecked. Use Usage and rotate secret to review those copies first. Each sign-in has its own Passed, Failed, or Unconfirmed result. A refused app secret needs an app or secret fix. A refused sign-in may need reauthorization. A storage or network error leaves the result unconfirmed. If the saved app or sign-in changes, the old result is Superseded.

Checks run in the background. You can close the view. Reopen it to read the latest saved result. After a lost reply, choose Refresh renewal status. This reads saved status and does not retry the token request. A server restart leaves unfinished checks unconfirmed. It never resumes them. Finished results are kept for up to 90 days and 10,000 checks on this server.

A passed renewal proves only that the vendor issued a token and Recued saved it. Use Verify access for data reads. Renewal does not prove send or edit access. It does not start sync, run work or mark an old incident recovered.

#Review token-renewal history

Choose View saved-app history in Manage saved apps to see older checks. You can also view them in Connection incident history. Each check shows the app version, times and result for each sign-in. An excluded sign-in was not checked. An unknown result is not a pass. Superseded means the saved app or sign-in has changed since the check. If Recued cannot read the current keys, it says the comparison is unknown. Unlock Recued and refresh history to compare them again.

An older saved check may be added when history support is first enabled. Its card shows both the check time and when it was added. Its position shows when it was added, not when an earlier repair took place. Opening or refreshing history makes no vendor calls and never repeats a check. Renewal results have their own card. They do not mark an incident recovered. Checks for saved API sign-ins can appear in linked Mail and Calendar history too. This checks the sign-in. It does not read mail or calendar data. Some account or file links may be missing. The card says when its list is incomplete. Use the listed API link or all history to find that check.

#Repair a failed token renewal

Open a saved renewal result or history. Use the repair button by a failed sign-in. Review app credentials opens that saved app's usage and secret form. Review app usage helps you check copies with old or conflicting keys. Re-authorize opens the listed API, Mail or Calendar sign-in review. Check the account. Review its shared uses and needed permissions. Then approve the change.

Recued checks the saved result again. It does this before opening a repair. The app or sign-in may have changed. Recued may be unable to compare it. If so, refresh and review it again. A saved app or account may be gone. Recued will not pick another one for you.

After repair, choose Review token renewal after repair. You can also choose Review token renewal again in a saved result. This opens a new review for that saved app. It uses the current keys. Choose the sign-ins to check, then choose Run renewal checks. Opening a review does not run the check. An earlier result stays in history. Use Verify access to check data reads too. Renewal alone does not prove data access.

#Pending renewal reviews

If a check for another saved app is still in progress, Recued keeps it. Read its result or refresh its status first. When it finishes, choose the app you want to check. Recued says when it cannot open that review yet.

You can leave history while Recued reads a saved result. If you do, its late reply will not open a repair.

#Verify access after token renewal

Open a finished renewal result or its history card. Choose Verify access. This opens a new read check. It does not run a new token-renewal check. The review uses the sign-ins saved now. It lists the accounts from that saved result. Their sign-ins may have changed since then. It can include sign-ins that renewal skipped or could not check. Other uses of that app stay outside this list.

Review the API URLs and the Mail and Calendar accounts shown. Review its file sources too. The review keeps the old links to accounts and files. It says when some links are missing. For file bytes, choose a file yourself. Recued does not pick one. Choose Run checks when ready. Before that, this review makes no vendor reads.

A running check can be opened again. This reads its saved status. It does not start a new job. Reading a running job does not need a fresh review. Its saved status can still be read if older links are gone. If current keys cannot be read, the comparison stays unknown. Find finished access checks in connection history. Read results also stay in the saved app's history. They stay in each checked account's history too. Old token-renewal results are kept separate. A read does not prove send or edit access. It does not run workflows or start sync. It does not prove that an old problem is fixed.

#Open settings from a failed read

Some reads fail or have no clear result. They can show Review API authentication, Review Mail authentication, Review Calendar authentication, or Review file authentication. Find these in saved checks, history and Authentication repairs. Wait for a batch to finish, or stop it first.

The shortcut reads the saved result again. It checks that the saved sign-in is still the same. Then it opens the resource's normal sign-in review. You choose whether to sign in again or make a change. No vendor request runs when you open it. No keys are changed.

If the sign-in changed, refresh the result first. Do the same if Recued cannot read the saved keys. If the result is gone, open the resource in Connections. A file shortcut needs a known link to its saved API connection. An older server may lack that link.

Some reads need a URL or a chosen file. They may not need another sign-in. After a repair, choose Verify access for a new read review. Earlier results stay in history. Opening settings does not clear old problems or prove that sync works.

#Return to the failed read after repair

When you open settings from a saved read, a return link stays above the form. Choose Return to saved access check when ready. It opens the original result for that resource. It does not run a new check. The old result may say Superseded after the sign-in changes. That is still the old result. It does not say whether the repair worked.

Choose Review current access for this resource for a fresh review. Only that resource starts selected. You can include other failed reads too. Review the current account and URLs. Choose a file again to check its bytes. Choose Run checks when ready. Each run keeps its own result in history.

You can reload the saved-result link and read it again. If it is gone, open connection history or Authentication repairs. Start a fresh review from there.

#Compare saved checks

Open a finished recheck and choose Compare with original check. You can do this in history or after a batch has finished or stopped. From Authentication repairs, choose View saved check first. Opening a comparison reads two saved results. It starts no vendor check.

The view puts the old and new read results side by side. Each has its own start and finish time. It shows whether each result still matches the saved sign-in. Superseded means the sign-in or source has changed. Unknown means Recued could not compare the saved sign-in. If the two status reads conflict, Recued marks both Unknown. Refresh the comparison after changing a sign-in. An old pass stays an old pass. Not checked in this attempt means that read was left out.

A URL or chosen file may differ between attempts. A pass covers only the read from that attempt. The view does not prove which repair helped, or that sync works. Send, edit and workflow checks stay separate.

Choose Refresh comparison to read both saved results again. Choose Hide comparison to close the view. If an old result is gone, you can still read the newer result. Open history or start a fresh access review when needed.

#Find entries in connection history

Use Search saved history to find a name or saved ID. Choose Event type and Recorded outcome to narrow the list. The date fields use when an entry first started, in UTC. Both dates are included. Choose Apply filters to read the matches. This searches retained history, including older pages.

The page address keeps your filters. Reload the page, or use Back and Forward, to open that view again. Clear filters keeps the same account or connection. An old passed check stays an old result. It does not prove current access or that a repair helped. Applied repairs and recorded recovery have their own filters.

If no entries match, try a wider date range or clear the filters. If the server cannot use filters, update it or clear the filters. Searching history does not start vendor checks or retry failed work.

Choose Open saved check page beside a saved result. This also works for checks that passed. You can bookmark the page or reload it to read that exact result again. The link reads saved status. It does not run a new check. A running result follows the same job until it finishes.

Choose Open comparison page to keep a link to an old and new result. Reloading that page opens their comparison again. If the old result is gone, the newer result stays visible. A link for one resource also has View all results in this check.

After you choose Run checks on a check page, Recued opens its saved result. Use the same Recued server when opening a saved link. The link works while Recued keeps that result. If it is gone, open history or Authentication repairs for a fresh review.

#Retry failed or unconfirmed reads

Open a finished access check or its history card. Choose Review failed or unconfirmed reads. Only accounts with a failed or unconfirmed read are listed. Unchecked send and edit tests do not add an account. All listed accounts start selected. Clear any you want to skip. Choose at least one account.

Review the current URLs, folders and calendars. Choose a file again if you want to check file bytes. Old URLs and file choices are not kept in history. Choose Run checks when ready. Until then, no vendor reads run. An earlier file metadata read may run again to check file bytes. Passed reads on other accounts do not run again.

Each recheck has its own result. It does not replace old results. Earlier passes stay in history. They are not new proof of access. If a start reply is lost, retry keeps the same choices. Choose Review again to change them. Opening a running recheck reads its saved status. It does not start the reads again. If its old result is gone, open Authentication repairs. Start a fresh Verify access review there.

#See the latest saved access

Open Authentication repairs. Find Latest saved access on an account. Saved repair cards in history show it too. Each row uses that target's newest saved check. A retry can update one row while other rows keep their older checks. Each row shows when its own check ran. Old results keep their original times in history.

Open Check details to see the reads and their results. Superseded result means the saved sign-in or source changed. An unknown match needs review before you rely on the result. Choose View saved check to read its full saved result. This reads local status. It does not run the vendor reads again. A running check can still finish in the background.

Not checked means no read check is still kept for that target. The page says when some targets or checks could not be shown. Choose Verify access for a new resource review. Only Run checks starts vendor reads. A new file metadata check does not keep an old download pass. Choose a file again to check its bytes.

Saved problems can stay visible beside a passed read. A read does not clear an incident or prove that sync works. Sending, editing and workflows stay separate.

#Check several accounts

Open Authentication repairs and choose Verify multiple accounts. The list includes saved accounts with no recorded problems. Choose up to 16 accounts across your OAuth apps. Select Review selected accounts to see their resources. Opening this review does not contact vendors.

Enter a protected API resource URL for each API read you want checked. A blank URL stays unconfirmed. Choose a file to check its download or export. Without a file choice, Recued checks file metadata. Each resource is included once, up to 128 resources in total. Unavailable reviews are shown and do not start.

Choose Run checks to begin. Recued checks one account at a time and shows each saved result. A failed read continues to the next account. If a start or status reply is lost, the queue pauses. Choose Recover saved outcome and continue to recover the same job. This keeps the original resource choices.

Stop remaining checks stops accounts that have not started. Started jobs keep running on the server and stay in history. After stopping, Refresh saved outcomes reads their local status. It does not start new checks. Leaving or reloading stops the unstarted part of the queue. Choose Review accounts again for a new resource review. API URLs and file choices are cleared for that review.

These checks do not send mail, edit files or run workflows. They do not clear recorded incidents or prove that sync works.

#Recheck several saved reads

Open Authentication repairs, then Verify multiple accounts. Choose Recheck failed or unconfirmed reads. After a batch, you can also choose Review failed or unconfirmed reads. That shortcut selects results that still need a read check.

Choose up to 16 saved checks, then Review selected reads. The list uses the latest saved result for each resource. It skips resources whose reads all passed and checks still running. Sending and editing permissions are not retried. Missing or incomplete results are shown as unavailable. Opening or reviewing the list does not contact vendors. Recued refreshes the saved results before preparing the review. If selected results changed, review the updated selections and choose Review selected reads again.

Review Earlier saved check to see the source results. Enter API resource URLs and choose files again. Recued does not reuse old resource choices. A blank API URL stays unconfirmed. A file download check can repeat its metadata read.

Choose Run checks to start the selected reads. Each saved check gets a separate result linked to its source. Earlier passes stay in their original history entries. A failed read continues to the next saved check. Uncertain replies pause for recovery with the same request. Stop remaining checks leaves started jobs running on the server. Leaving or reloading stops checks that have not started.

#Review app permissions

In Connections, choose Apps & APIs. Expand Authentication settings. Choose Permissions and cleanup. This shows all saved sign-ins, including those through a broker. For one saved app, open Manage saved apps. Open that app's row, then choose Review permissions.

Recued lists each app and its separate sign-ins. It shows what Mail, Calendar, Files and installed workflows need. Paused schedules still count as uses. Each scope is a vendor permission, such as reading a sheet. Required scopes show which features need them. Other uses of the same app can protect a scope too.

A removed pack may leave a scope behind. Check scopes marked No longer required locally. Then choose Preview cleanup. The preview shows what to keep and which uses may be affected. It does not remove access or change your saved sign-ins. Refresh if a pack or connection changes during your review.

These are local records, not a fresh vendor check. A requested scope does not prove that the vendor granted it. Unknown grants or uses stay unknown. Other tools may still need a scope that Recued no longer needs.

#Finish Google cleanup

For a Recued direct Google Mail, Calendar or API sign-in, open its cleanup preview. For an API sign-in, save the same Google app in Apps & APIs first. Its Client ID and secret must match the API connection. Choose a protected read URL for each API connection shown. For Sheets, you can paste a private spreadsheet URL. Public files cannot prove that the new sign-in works. Choose Start guided Google cleanup. Review the accounts and connections, then choose Pause accounts and continue. Packs and recipes using a paused connection cannot access Google until recovery ends. Other Google apps, file sources and brokers may block this reset. Their uses need a safe way to reconnect first. We must be able to check the API account with its remaining scopes. Recued does not ask for more scopes just to check who signed in. An unknown account stays protected.

Open Google account access. Check the app name and Google account. Remove the app's access on Google. Other tools using the same app may lose access too. Return to Recued and confirm that you did this. Recued records your confirmation; it cannot read that Google page.

#Verify and save Google access

Choose Reconnect and verify Google account. Use the same Google account and grant the access shown. Recued checks the new grant and reads the saved source or API resource. The same URL must block a read that has no secret key. Separate grants keep separate saved sign-ins. Known copies of the same API grant share one sign-in. Repeat Reconnect and verify Google account for each one shown. Keep the Google app access in place between these sign-ins. Once all checks pass, choose Save reduced sign-in. Names and pack and recipe links stay the same. Your saved data and sync place stay intact. Later sign-ins use the new scope list. The earlier list stays in the server's cleanup history.

#Resume a saved cleanup

Open Permissions and cleanup, then choose Resume cleanup. The task stays on your server if you close the browser. Use Refresh saved status after a lost reply. This reads the saved result without repeating the change.

If Google still reports access you chose to remove, choose Repeat Google access reset. Remove the app access on Google, then confirm it again. This clears the earlier checks so each sign-in can be verified afresh.

If a pack changes during cleanup, choose Refresh cleanup review. If an API test file moved or was deleted, open Change API access checks. Choose a new private read URL, then use Refresh cleanup review. This clears the old checks. Sign in again before saving. If it now needs the access you chose to remove, cleanup must stop. Choose Stop cleanup and restore access, then sign in again. This keeps the old access; it does not claim a scope was removed. A later review refresh still keeps that access. Do this too if you want to stop after pausing accounts. You can delete an account once you finish or restore its access.

If an account fails to pause, use Retry pausing accounts. You can also refresh the review or stop cleanup and restore access. Finish pausing before signing in again.

#Understand cleanup limits

Google may revoke a whole shared sign-in at once. Mail, Calendar and packs using it can all lose access. Removing one scope can thus need a full reset and new consent. Microsoft can limit who may change a grant. Work or school accounts may need an admin. Broker apps can have fixed scopes too.

The preview does not perform these changes. Asking for fewer scopes does not prove old consent was removed. Deleting a broker connection does not prove that either. Guided Google cleanup checks a fresh grant and saves its scope list. The app-access reset on Google is a step you confirm yourself. Microsoft, broker and unsupported Google API sign-ins still use the preview and vendor review. They do not yet have this guided reset. Google file sources still need a safe way to restore access first.

#Get help with OAuth sign-in

Choose Troubleshoot OAuth in the connection or account form. It is also in saved apps and Nango broker settings. Pick the symptom closest to what you saw. The guide shows checks for your sign-in method. It can help with blocked apps, scopes, secrets and lost replies.

The guide keeps observed errors separate from what you report. A denied request can have more than one cause. Use the callback shown for that flow. Nango uses its own vendor callback. It also has an API key, separate from the vendor app secret.

Tick each check as you review it. These ticks do not prove that sign-in or API access works. Use the normal access check after any repair. If a result is still pending, check it before starting again. The guide does not change credentials or start sign-in. App-only connections show checks for token requests. They do not use a sign-in window. Changing the app or account starts a new checklist.

Choose Copy help summary to share the checks with support. It omits account IDs, secrets, raw errors and callback URLs. Keep passwords, tokens and returned sign-in links private.

#Switch the OAuth app for Mail or Calendar

This needs Recued 26.10.16 or later. Open Connections → Mail or Calendar, then open the account. Choose Manage authentication → Change OAuth app. Pick a different saved Google or Microsoft app. Review the account, permissions and callback URL. Register that callback URL on the chosen app.

Choose Authorize and verify account. Sign in to the same vendor account. Recued checks the account and its access before you can apply. An unknown or different account stops the switch.

Choose Apply OAuth app switch after the checks pass. The account name, saved data, folder choices and sync state stay in place. Sending and editing keep their old limits, even if the vendor grants more access. Microsoft Mail and Calendar switch together when they share one sign-in. Sync pauses briefly, then resumes.

If the reply is lost, choose Check result before starting again. If sync needs a restart, restart Recued and check the result. Accounts linked through Apps & APIs use Switch authentication instead. Use Manage saved apps to add an app before trying this flow.

#Switch saved apps for several Mail and Calendar accounts

Open the Mail or Calendar list in Connections. Choose Switch OAuth app for several accounts. Pick one destination saved app, then select up to 20 native accounts. The list can include both Mail and Calendar for that vendor. Accounts already using the chosen app are skipped.

Choose Review selected accounts. Recued groups collections that share a sign-in. Those collections switch together, even if you selected only one. Read the account names, kept resource choices, permissions and callback URL. Choose Authorize and verify account for each group you want to switch. Sign in to the same vendor account for each group. A different or unknown account cannot pass the check.

Choose Apply verified groups after reviewing the checks. Each group saves in one step. Names, data, selections and sync state stay in place. A failed group keeps its saved app. Other verified groups can still switch. Earlier successful switches stay applied if a later one fails. Stop remaining switches lets the current switch finish and stops the rest. Opening another account view also stops the rest after the current switch finishes. Expired reviews need a fresh sign-in.

#Check bulk saved-app switch results

Choose Check switch results after a lost reply. Reopening bulk switching in the same browser tab reads saved attempt results. It never resumes unstarted switches or repeats an apply. An earlier switch can have used a different app. That result does not count as a move to your newly selected app. Recued reads the saved result before naming its destination. The browser keeps account references and attempt IDs, without tokens or codes. Keep the view open if browser result recovery is unavailable. If sync needs a restart, restart Recued, then check the result. Choose Choose accounts again when all results are confirmed. Accounts linked through Apps & APIs use Switch authentication instead.

#Sign in through Nango

A broker is another server that holds your vendor sign-in and makes API calls for you. Nango is one such broker. You can choose it under How to connect → Managed OAuth. It works with API packs. Mail, Calendar and file sync can also use these saved connections.

First, open Connections → Apps & APIs. Expand Authentication settings. Choose Manage OAuth brokers. Set up a broker there. You can also add one while setting up a connection. Choose Add broker to open the form.

  1. Enter a Profile name. Use a name you know.
  2. Enter its Server URL. For Nango Cloud, use https://api.nango.dev. You can use your own Nango server too. It can run on another machine.
  3. Paste its Environment API key. Get it from Environment Settings → API Keys in Nango. An environment is a separate place for test or live accounts. The key chooses that place. It does not mean a local machine.
  4. If your own Nango server has a separate sign-in page, open Separate Connect UI (optional) and enter its Connect UI origin. This is the start of that page's address. Otherwise, leave it blank.
  5. Click Test and save broker.

To change its name or key, choose Edit broker. Leave the key blank to keep the saved one. Use a new key from the same Nango environment. With saved accounts, Recued checks that both keys reach the same accounts. Change the key before you revoke the old one. For a different environment, add a new broker profile. Connect its accounts again. Do this too if the old key no longer works.

Use Close brokers when you are done. Recued asks before you leave a form you have not saved. Remove profile asks you first. Your Nango accounts stay. You cannot remove a profile used by a saved connection.

#Choose a vendor app

Choose a vendor integration next. This is the app set up in Nango for that vendor. Recued picks it for a pack when exactly one app matches. With more than one, you choose.

If no app is set up, click Create vendor integration. Choose a Nango shared app, if your server offers one. Or enter your own vendor app's ID, secret and scopes. A scope is a named permission, such as reading mail. Recued sends those app credentials to Nango. It does not save them itself.

#Reuse or reauthorize an account

Recued checks for Nango accounts when you pick a vendor app. If it finds accounts, it starts with Use an existing Nango account. Pick one and click Use selected account. Then save and test the connection. A probe checks whether Recued can reach it. It does not prove that every needed permission was granted.

If there are no accounts, Recued offers Authorize a new account. You can also choose this when you need another account. Each new sign-in creates another Nango connection. After consent, save and test before starting again.

Reauthorize keeps the same Nango connection. If Recued has already requested all the needed scopes in completed sign-in flows, it reuses the account without new consent. Granted permissions stay unknown. Save and test, then check the access needed by your task. No custom Nango function or extra setup is needed.

To repair access, choose Review sign-in again. Check the request. Then choose Sign in again for new consent. This also keeps the same Nango connection. Recued checks the scope needs of all its saved connections that share that account.

#Keep scope history

Reused accounts can keep scope history from other saved Recued connections. If that history is unknown, manage consent in Nango with the same scope profile. This keeps Recued from dropping prior permissions.

If Nango hides app scopes, Recued may refuse to reauthorize a saved account. Use a key that can read those scopes, or manage its consent in Nango with the same scope profile. Finish or cancel a pending sign-in before starting another for that account.

Cancel stops the Recued sign-in flow. It does not revoke vendor consent. Close the vendor sign-in window if it stays open after cancel or success. Scope unions cover requests saved in Recued. If you change consent in Nango or another tool, keep its full scope profile there.

Shared apps may have fixed permissions. Vendor rules and requests for an admin's consent still apply. When Nango does not report granted scopes, Recued shows them as unknown.

#Change the scopes you need

Recued saves your scope needs apart from past consent. Asking for the same or less access can reuse a healthy account when its completed scope history covers all current needs. This history records past requests, not granted permissions. A vendor can still refuse access. To repair access, choose Review sign-in again, check the request, then Sign in again.

Asking for new scopes, or a mix of old and new, keeps the same Nango account. New consent requests the full tracked list, app defaults, and the scopes needed by other saved connections. A smaller request does not remove old vendor permissions. Other tools may still need them. Recued does not offer a scope downgrade.

Before new consent, Recued clears old grant proof for all connections sharing that account. Access stays in Nango. If sign-in fails or is canceled, those grants stay unknown. Recued will not claim the old scopes still apply.

If a saved connection's scope needs change during sign-in, start again. Shared apps with fixed scopes may need an app change first.

Recued keeps scope history from completed consent even if you close the form without saving. This needs Nango to report its internal account ID and creation date. It checks for completed consent when you cancel. A failed scope request is not kept for later sign-ins.

#Review requested permissions

Before you authorize, Recued shows the new scopes and those it will keep. The preview lists the connections and packs that need them. Open the full scope list to see the planned request. Why these permissions shows where your scope needs come from. If access can be reused, choose Use current authorization. No sign-in window opens.

If the request changes after review, choose Check again in the preview before you continue. The preview shows requested access. It cannot prove which scopes the vendor granted. If sign-in fails or expires, refresh the preview before you try again.

With a fixed Microsoft app profile, extra permissions may need an app change in Nango. You may need an admin's consent too. If Nango hides app scopes, Recued shows that the exact request is unknown. It keeps the app's scope profile. These app profiles may not request each listed need as a separate scope.

#Check access for a pack

Open a pack's Access tab. Under Connections, find the account you want to check. Choose Check access for this pack.

Recued shows the read checks that pack offers. For a resource check, enter its ID. The Google Sheets check also accepts a sheet URL. For Google Calendar, primary means this account's own calendar. Choose Check read access on the check you want to run.

These are the first checks:

  • Google Sheets reads a sheet ID and its tab IDs.
  • Gmail lists up to one mail ID.
  • Google Calendar reads a calendar ID or lists one event ID.
  • Outlook lists up to one mail folder ID.
  • OneDrive reads the root ID or a chosen file ID.

Other packs show that their access remains unverified. Update an older installed pack if Recued asks you to do so.

  • Passed means this account could read the chosen resource. The same request with no secret key had to refuse access.
  • Access denied means sign-in, permissions or resource sharing need review. It does not identify a missing scope.
  • Unverified means the check could not prove access. Check the resource ID, connection or vendor status, then try again.

Each result shows when it was checked. Change the resource ID to clear its old result. Refresh checks reads the pack and connection again. If either changes during a check, refresh and retry.

Choose Review permissions in Connections to open that saved connection's editor. Review the request before signing in again. No consent window opens until you choose to authorize.

These checks use GET requests. They throw away the response data. They do not change vendor data, grant scopes or run recipes. Saved secret keys may refresh as usual. A passed read proves only that read. Other actions and write permissions remain unverified.

#Account and impact preview

Before you sign in or switch, review Account and impact preview. It shows the saved account and the account you chose. Recued shows a vendor email when existing access can read it. An unknown email stays unknown. Recued does not ask for extra permissions just to find your email.

The preview lists packs, recipes, dishes, schedules, Mail, Calendar, and file sources that use the connection. A dish holds a recipe's saved settings. Some recipes can choose this account, but use another one by default. Those rows say can choose this account. Paused work stays on the list and says paused. Named API links count too. A need that names no account type is shown as a possible use.

Other local connections may share the selected Nango account. A new consent can affect their access before you save. The list covers this Recued server. Other tools may also use that account. Missing local use is shown as unknown.

After sign-in, Recued reads the actual account again. Review it before saving or choosing Verify and switch. If that read fails, choose Refresh account and impact. Recued keeps the account you just signed in to for the next review. If the account or its use changes, refresh the review. Your connection name stays the same after the switch. Mail and Calendar bindings pin their broker account. Review and reconnect those collections after switching accounts.

Account details do not prove access to all data or actions. Use a pack's read checks to test the resource you need.

#Move several connections to your own app

Set up a direct OAuth connection for the vendor API first. Authorize it with the scope needs of the connections you will move. Keep this source connection outside the group you will move.

Open Connections → Apps & APIs → Bulk authentication migration. Pick one vendor API service and up to 20 connections. Choose Recued direct OAuth, then pick the direct source connection. Choose Review direct OAuth account and permissions. Recued renews the source keys. It does not open Nango sign-in.

Give each connection a private, read-only API URL. Choose Check all selected connections and review the results. Then choose Apply verified connections. A failed row keeps Nango in place. Later rows can still switch. Each row is checked again before its saved keys change.

Names, packs, recipes, and API settings stay linked. Use the Mail and Calendar links to reconnect the listed collections. Old Nango accounts are kept. Scope needs stay tracked for each connection. These native connections share key renewal in Recued. When the vendor changes a refresh token, Recued updates the linked keys. Grants are unknown if the vendor reports no scopes. Stop migration stops later rows. It keeps prior successful switches. Use Refresh results after a lost reply. Reviews expire after 30 minutes. A restart never resumes a migration.

#Move several connections to Nango

Open Connections, then Apps & APIs. Choose Bulk authentication migration. Pick one vendor API service and up to 20 connections. Their names stay the same. Packs and recipes keep those names.

Review the current accounts and the shared permission needs. Choose a Nango broker and account, then sign in if needed. One sign-in can serve this group. Recued does not ask for extra permissions to find email.

Give each connection a read-only URL that needs sign-in. A private Google Sheets link works for Sheets. Choose Check all selected connections. This reads each resource. It does not switch a saved account yet. Review each account, local use, and check result. Then choose Apply verified connections.

A failed check leaves that connection as it is. Other verified connections can still switch. A successful switch stays applied if a later one fails. These read checks do not prove write access or all scopes. Review Mail and Calendar bindings after an account change.

Use Refresh results after a lost reply. You can reopen Recent migration reviews on this server. Opening a review never applies it. Stop migration stops later switches and keeps prior successes.

Reviews last up to 30 minutes. A server restart clears the review and never resumes it. Read the saved connections before starting again. Your browser stores no credential for this flow.

#Switch back to your own OAuth app

You can move a Nango connection back to Recued direct OAuth. Its name and API address stay the same. Packs and recipes stay linked. Your saved sign-in stays active while you review the new one.

  1. Open Connections → Apps & APIs. Find the saved connection. Choose Manage authentication.
  2. Choose Change authentication method. Pick Recued direct OAuth.
  3. Enter your app's client ID and secret, if it needs one.
  4. Use Authorize to sign in with that app. Recued fills the refresh token. You can also paste a token for that app.
  5. Choose Review direct OAuth account and permissions. Check the account, scope needs, and work that uses this connection. An email can be unknown with the access you have.
  6. Enter a private, read-only API URL. A Google Sheets link also works.
  7. Choose Verify and switch.

Recued renews the native keys and checks access with the vendor. The same URL must refuse a call with no sign-in. Failed checks keep Nango in place. A passed read does not prove write access. The old account's scope grants are cleared. Local scope needs stay tracked. If the vendor reports no scopes, its grants stay unknown. App or scope edits need a new review. Reviews expire after 30 minutes.

Check the Mail and Calendar uses in the preview. Their saved broker links need a fresh connection through your own app. The old Nango account is kept. You can remove it once no work needs it.

#Switch a saved connection to Nango

You can move an API connection from your own OAuth app or bearer token to Nango. You can also choose another Nango account or broker profile. Its name stays the same. Packs and recipes keep their bindings. The new account may see different data.

  1. In Connections → Apps & APIs, choose Edit on the saved connection.
  2. Choose Manage authentication → Change authentication method.
  3. Choose a broker and vendor app. Pick an existing account, or sign in to a new one.
  4. Review the needed permissions. Then authorize the chosen account.
  5. Enter a Read-only access check URL for a resource that needs sign-in. It must be within the saved API. For Google Sheets, paste a sheet link.
  6. Choose Verify and switch.

Recued reads that resource through the new account. It checks that the same resource refuses a call with no sign-in. It discards the response body. If the check fails, Recued keeps the saved sign-in. You can fix the check URL and retry. A passed read does not prove each scope or write permission. For a denied read, choose Review sign-in again for the chosen account. Review its request, then sign in again before retrying the access check. If this form's sign-in expires, choose Review authorization again. It checks the account you signed in to. It can reuse that account. It does not create another Nango connection. You can retry a failed review. The account choice stays.

Use Keep current authentication to leave the switch form. The saved sign-in stays active until the switch passes. Recued does not remove the old Nango account or revoke old vendor consent. New consent can change the chosen Nango account at once. Keep its full scope list if other tools use it.

#See where a Nango account is used

In Apps & APIs, open Manage OAuth brokers. Choose a broker, vendor app and Nango account. Account status and usage lists the saved API connections that use it. Each connection shows its pack, Mail, Calendar and file bindings, plus its last recorded use and API check.

Nango's sign-in status and API access are separate checks. A prior success stays current for 15 minutes. When that time ends, the view asks for a new check. This works even if you keep the page open. Choose Check API access to test the connection through its normal probe. That probe checks its configured API endpoint. It does not prove every task or scope works.

Choose Open connection to edit it or review sign-in again. The editor reads the current saved connection. It asks before discarding an unsaved draft. If it has changed since this view loaded, refresh the view first. Wait for your current action to finish. Then open it. For new consent, review the permissions. Then sign in.

Usage lists this Recued server's bindings. Other tools may use the same Nango account. A failed usage read stays an error until you retry.

#Keep Nango connection use low

Many packs can share one saved API connection. You can also reuse the same Nango account in other Recued API connections. Mail, Calendar and file sync can use a saved API connection too. These choices need no extra Nango account.

The vendor app and its permissions must fit each task. The same email address in two Nango vendor apps still means two Nango connections. Removing a Recued connection does not free its Nango slot. Use Manage OAuth brokers to remove an unused Nango account.

#Use a saved connection for Mail or Calendar

First save a managed API connection for the service. Then open Connections → Mail or Calendar, add an account, and choose Google or Microsoft. Under How to connect, choose Managed OAuth — saved API connection. Pick your saved connection and give the account a name. When only one saved connection fits, Recued picks it for you. You do not need another app ID, app secret or sign-in.

The API base URL must match the service:

Service API base URL
Gmail https://gmail.googleapis.com/gmail/v1
Google Calendar https://www.googleapis.com/calendar/v3
Outlook Mail or Calendar https://graph.microsoft.com/v1.0

Mail sending, mail changes and Calendar writes start off. Turn on only the write options you need when you add the account. These switches let Recued try a write; they do not grant new vendor access. Add the needed scopes to the API connection and sign in again there first. The vendor still checks each call. If Nango gives no scope list, permissions stay unknown.

To change these write options later, remove and add the Mail or Calendar account again with the saved API connection. This does not delete the remote Nango account. Each account's menu also links back to Apps & APIs for reconnecting its source. Remove the Mail and Calendar accounts before removing the API connection they use.

#Switch authentication for existing Mail or Calendar

Open Connections → Mail or Calendar. Select the Google or Microsoft account you want to keep. Choose Manage authentication. Then choose Change authentication method.

Pick a saved API connection for the same service. This is the source for the new sign-in. Recued direct OAuth comes first. You can also use a broker. To set up or fix the source, open Apps & APIs. Then return here.

Choose Verify account and access. Recued checks that both sign-ins use the same vendor account. It also reads your chosen folders or calendars. It sends no mail and edits no events. The review shows the email if the vendor gives it; otherwise, it says Unknown. If the account differs or cannot be proved, your saved collection stays as it is.

Review the scopes. Then choose Apply authentication switch. Recued checks the account and access again before it saves the switch.

These stay the same:

  • The collection name and its links to your work.
  • Your folder or calendar choices and stored data.
  • The sync state, its saved keys, and the backfill flag.
  • The send and write options you already chose.

The tokens stay in the saved API source. A vendor may still expire a sync cursor. The adapter will use its usual way to start sync again.

#Permissions and migration recovery

The vendor must report the grants for any send or write option you keep. Read checks do not prove that you can send mail or edit events.

An empty Microsoft mailbox or calendar needs reported full read grants too. Basic read access does not include bodies. If a native token renews or expires after your review, verify again to review its current grants.

If the reply is lost, choose Check result. Recued keeps that check across a page reload. If the switch was saved but sync needs a restart, restart the server, then check the result again. If grants are unknown, Recued can check reads but cannot prove writes. If Gmail is empty, there is no mail body to test. It then needs a vendor-reported mail read grant. Add any missing scopes to the source and sign in there first.

#Recover a Mail or Calendar sign-in switch

If you lose the reply, choose Check result. You can also reopen the review to read the saved result. Recued will not repeat the sign-in flow. A failed check keeps the old config. If the server stops during a check, you must review it again; the switch will not resume on its own.

If the switch was saved but the collection did not restart, check its status. Restart the server to resume sync.

#Find sign-ins that need repair

Open Connections. Find Authentication repairs below the tabs. The same list is on Packs. It joins account problems with your Reconnect later Pack reminders.

Use Refresh to read the saved status again. This does not call vendors, sign you in, or change your account. A token that needs its usual refresh is not a failed sign-in.

Each entry shows the known uses of that account. Some uses may be unknown; Recued says so when the list is incomplete. Choose Open connection, Open Mail, or Open Calendar to review it. For files, you can open the source to check its last sync. Use Manage saved OAuth apps to review an app or its secret date. Your own OAuth app stays the first choice. A broker is optional.

A failed file read can have more than one cause. It does not prove that more permissions will fix it. An app secret date is the date you saved, not a vendor error. The list keeps these cases clear.

Mark reviewed clears only a Pack permission reminder. It does not clear a sign-in or file-source failure. After a repair, choose Refresh. File failures clear after the source records a successful sync. If part of the status cannot be read, unlock Recued or try again.

#View connection incident history

Open Manage authentication, then choose Incident history. You can also open it from Authentication repairs. Choose Connection incident history there to view all accounts. This includes saved history for accounts you removed.

Each incident shows when the problem was first and last seen. An old alert may not have kept its last problem date. That date shows as Unknown. It lists known uses and shows how the incident ended. Awaiting access evidence means the error is no longer recorded. It still needs a later successful check for each failed use. Successful operations recorded means those checks passed. It does not prove all permissions or retry failed work.

Changing a sign-in or removing a use can close an incident too. That does not mean access recovered. The history shows the reason. A new failure gets its own incident after the prior one ends.

#View repair actions

Incident history also shows repair actions and their results. These include reauthorization, app changes, sign-in changes and secret rotation. Each bulk change keeps a result for each connection. An action can appear even if no problem was recorded first. It shows the old and new sign-in, when known. It links to open incidents known when the repair started.

Authentication updated means the local change was saved. It does not confirm that all affected work can run again. A secret change does not check vendor access. Later success appears only when all linked incidents record recovery. The operation itself must happen after the repair was saved. A later background status update alone is not enough. This does not prove which repair caused the recovery. An unfinished collection restart is shown separately. Repair failed means the saved sign-in was kept. Earlier repairs and closed consent windows may not be in this history.

Choose Refresh history to read the saved state again. Choose Load older history for more entries. These reads do not call vendors or change your sign-in. Closed incidents, finished repairs, renewal and access checks stay for up to 90 days. Up to 10,000 finished records are kept. Long entries may omit some details; the page says when it does. Events from before this history was enabled may not be available.

#Export connection history

Set Export privacy, then choose Preview export by Refresh history. Privacy mode (aliases) is the default. This opens a report. It does not save a file yet. The file uses the scope and filters shown on the page. It includes all saved rows that match. It also includes older pages you have not loaded. Choose Apply filters first to use any edits you made.

Exporting reads saved local history. It does not check vendor access or run work. A past pass does not prove access works now. It lists each step on its own. Saved repairs, read checks and new tokens stay distinct. Later success stays distinct too. The file does not say if the sign-in works now.

If the report is too large, narrow the applied filters and try again. You get all saved rows that match, or an error. It does not download a partial report. If you leave this page, the preview is cleared. If your browser cannot save the file, try a browser that allows downloads.

#Open a saved history file

In Connection incident history, use Choose history JSON. Pick a full history export or a related history bundle saved by Recued. Files with names and IDs and files with aliases both work. Exports, bundles and records with source context must use version 1. The file must fit within 8 MiB. You can also open one complete saved record, as described below.

Recued checks the file before showing it. It opens in this browser tab and is not sent to your server or a vendor. The saved fields stay as recorded. Reports also keep their export dates, privacy mode and limits. A record without source context marks missing details as unknown. A related bundle keeps its original root and source snapshot limits. Its saved records remain a subset of that snapshot. File contents can be edited, so they do not prove current access or recovery.

Use the same search, pages, fields and copy actions as an export preview. Download this preview (JSON) saves the checked JSON. A related bundle's root also offers its original bundle copy and download. Refreshing live history keeps the opened file and your place in it. The live export privacy setting does not change an opened file. If a new file replaces one you were reading, focus moves to the new preview. Fields outside that preview keep their focus and edits.

If another file fails its checks, the earlier valid file stays open. Choose the file again to retry. Clear opened history or Close preview removes it from the page. Leaving this history page also closes the file. Opening a file does not add saved history, run checks or change any accounts.

#Open pasted history JSON

In Connection incident history, open Paste history JSON. Paste the complete report into History JSON. Then choose Open pasted history. Full exports, files with aliases and related history bundles all work. They use the same checks as saved files. The JSON must fit within 8 MiB. One complete saved record also works.

The text stays in this browser tab. Editing it does not change the opened preview. Choosing Open pasted history replaces any pending file read. An older read cannot replace the pasted result or its error message. If the JSON fails its checks, the earlier valid preview stays open. Your pasted text stays in the box so you can fix it and try again. Text that is too large stays in the box. You can edit it. It is not cut down.

The preview labels pasted JSON as its source. Saved fields stay as recorded. Reports keep their saved aliases, dates and limits. A record without source context marks missing details as unknown. Search, copy and download use that checked JSON. They use it even if you later edit the text. Pasting does not add server history, run access checks or change accounts.

Clear pasted text clears the box. The opened preview stays. Clear opened history or Close preview closes the preview. Your text stays in the box. For a pasted report, focus returns to the text box. Refreshing live history keeps the text, its selection and the opened preview. Leaving this history page clears the text and preview.

#Open one saved history record

Use JSON from Copy record as JSON or Download record as JSON. Choose its file, or paste it into History JSON. For pasted text, choose Open pasted history. Incidents, repairs, access checks and token renewals all work. Keep the whole record, with its type and outcome. Both names and IDs and saved aliases work. The JSON must fit within 8 MiB.

The preview shows Saved history record or Pasted history record. It shows just that record and its saved fields. Its source report is not included. Without source context, the export date, scope, filters and retention are unknown. So are its original position and privacy setting. Aliases from separate files do not prove a link between records. Related history actions are not shown for a lone record. References stay as saved text and cannot open other records.

Search and copy work within this record. Both download actions save the complete checked record. Any source context stays as recorded. No position is guessed for its filename. A search that finds no match still keeps the full download. Editing the paste box leaves the opened record unchanged. If a new file or paste fails, the valid preview stays open. Opening a record stays in this tab and changes no accounts. It does not add server history or check current access.

#Include source context with a record

Open a record in a report or a related bundle. Select Include source context beside its copy and download actions. This option starts off. Both actions then save one record in a version 1 file. Its source date, scope, filters, privacy mode and limits are included. Other records are not. Names and aliases stay as shown. Aliases are not renumbered. Full data can include saved names and search text. Review it before sharing. Clear the option to save the bare entry again.

The source position is included only when known. A reopened related bundle knows its root's position. Other positions remain unknown. Source counts describe the source report, rather than this one-record file.

Open this file or paste its JSON in Open saved history. Source snapshot details shows its saved context. This context is a saved claim. It does not prove the source or current access. Matching aliases across files do not prove a link. Search covers the entry fields. Source details are not searched. Download this preview (JSON) keeps the checked file and its context. The record's own copy and download actions still start without context. Select the option to include it again.

A bare entry has no context to add, so the option is not shown. If adding context would exceed 8 MiB, the bare actions stay usable. Nothing is sent to a server, imported or checked with a vendor.

#Review an export preview

The preview shows its date, file size and counts of saved records. Open Report details to see its scope and applied filters. Open a record to see its saved fields and gaps. Use Next records and Previous records to read more. Large lists within a record have their own pages. Reference buttons open linked records within this preview. A record outside this snapshot is marked as absent. These reads do not call vendors or change your sign-in.

Choose Download this preview (JSON) to save that exact report. It uses the same bytes you reviewed. It does not fetch a new report. Refreshing history keeps the preview you already opened. Choose Refresh export preview to read a new snapshot instead. Changing privacy or applied filters clears the old preview. So do Close preview and leaving this page. Edits not yet applied to filters do not change it. If the download fails, you can try again from the same preview.

#Search an export preview

Type an alias, ID, name or saved reason in Search this preview. Choose Search preview or press Enter. This searches all saved records in that report. Use verification to find saved access checks. It includes fields in closed details and on later pages. It ignores case changes. Symbols count as plain text. Use up to 128 characters. Edits take effect when you search. Applied preview search shows the text used for these results. Names can match only in Names and IDs (local use) mode.

Choose Clear preview search to remove the text search. Your type and outcome filters stay in place. Match counts describe the list you see. The download still includes all records in the captured report. Search does not change its bytes or fetch new data. It stays in this preview and is not saved in the file. History refresh keeps your search and edits. A new preview starts with no preview search.

A linked record may be outside your search results. Its button explains that opening it clears your preview search. The button then opens that record in the full snapshot. If the record is absent from the snapshot, no lookup starts.

#Filter a full history report preview

Choose Record type or Recorded outcome under Filter this preview. These choices work in export previews, opened files, pasted reports and full comparison source reports. A single record keeps its field search. Both choices start at All and list the values found in the whole report. Choices stay available when a search or another filter hides those records. Recorded outcomes describe saved observations, not current vendor access.

Filters apply right away to the last text search you applied. Text you are still typing stays in the search field, with any query error. Enter on a filter keeps that draft. Search or Enter in the text field applies it. Type, outcome and text must all match. No matches leaves your choices in place. Each change starts at the first matching page, in saved order. The count separates matching records from the complete snapshot count.

Clear type and outcome filters removes both choices and keeps the text search, unfinished text and query errors. With no filters set, it keeps open details. Each preview keeps its own choices. History refresh keeps them too. A new or closed preview starts again at All. When reset removes a record that still has focus, the visible count takes focus. A newer focus choice stays in place.

#Filter report dates in UTC

Under Filter this preview, set Started from (UTC) or Started through (UTC). Both days are included. Leave either end empty for no limit. The dates use each record's original start time in UTC. Finish dates, the snapshot date and your local timezone do not change this. These controls work in full export, file, pasted and comparison source reports. A single record keeps its field search.

Your browser chooses the format shown in each date field. Recued compares the selected days in UTC. Choose Apply date range, or press Enter in a date field. Editing a date alone keeps the earlier results. Incomplete, invalid or reversed dates show an error and keep those results. The applied caption shows the dates currently used. Dates, type, outcome and applied text must all match. No matches leaves your choices in place. A changed range starts at the first matching page, in saved order.

Applying dates keeps your unfinished text and any query error. Search and type/outcome changes keep applied dates and unfinished date edits. Clear date range clears applied dates, date edits and date errors. It keeps the text search, unfinished text, type and outcome. The text and type/outcome reset buttons each keep applied dates. An unchanged range or empty date reset keeps open record details. History refresh keeps the dates and edits; a new preview starts with empty dates. Downloads still include the complete saved report.

#Follow references from a filtered report

Saved references can open a record outside these results. The button explains this before you open it. Only the search or filter choices hiding that record are cleared. Back and Forward restore the saved search, filters, complete date edits, errors and page. A saved reference clears only a date boundary that hides its target. A date field you have not edited follows that cleared boundary. A newer complete date draft stays in place. If a partly entered date cannot be restored, enter it again or clear the date range. Apply keeps the earlier results until you do. Back also restores your earlier choices after a reference needed to clear them. If no selected record remains, navigation returns to the visible count.

Downloads and copies keep their complete saved contents. Record source positions and aliases stay the same. Related bundles still use the whole captured snapshot, including hidden records. Their own filters stay separate from these report filters. Filtering fetches no more history and does not check current vendor access.

#Open a matching field

Each search result shows how many fields match. It also shows the first matching path. Open the record to read Matching fields. Use Next matches and Previous matches to see more. There are five fields per page. Each field is counted once.

Paths show the saved field and item numbers. For example, Group › Uses › Item 45 › Label names a pack label. Matches are highlighted in field names and saved text. Long values show nearby text around the first match. Other matches in that short view are highlighted too. An ellipsis means some text was left out. Long matches can also be cut short. Choose View field to see the full saved value. It opens the needed details and list pages. The field gets focus and an outline. This also works for lists inside other lists.

Your search and match page stay in place. If you page away, View field can open the field again. History refresh keeps that view and focus. A new search or privacy choice clears the old match view. Names removed by privacy mode cannot appear in these matches.

These reads stay in the captured report. They do not fetch data, check access or change the download.

#Find text in a full value

Choose View field to highlight hits in the full value. The first hit scrolls into view. The field keeps focus. The full text keeps its original characters, including accents. Matches elsewhere in that value are highlighted too.

Sometimes a saved code differs from the readable words. For example, false appears as No. If only the saved form matches, Saved value shows it. The readable value stays beside that saved form. Dates still show UTC time. If only the field name matches, unrelated values get no highlights.

Returning to the match list keeps the highlights. So does refreshing history. Opening another field clears the prior value's highlights. Paging away from a field clears its highlights too. A new search or privacy choice clears the old view. These highlights leave the saved file unchanged.

#Move between hits in a value

After View field, the opened value shows Hit 1 of N. Choose Next hit or Previous hit to move within it. The current hit has an outline and scrolls into view. The controls stay beside long values as you move. The buttons stop at the first and last hit. Keyboard focus moves to the count at each end. For one hit, both buttons are off. If only a field name matches, these controls stay hidden.

Hits next to each other count separately. Hits within one saved symbol count as one highlighted range. These counts refer to hits in this value. Field and record counts stay the same.

Returning to the match list keeps the chosen hit. So does changing match pages or refreshing history. Opening a field again starts at its first hit. Search, privacy and list changes clear the old controls. The full saved file stays unchanged.

#Export one record from live history

In Connection incident history, find the row you need. Open Export this record. Choose Copy record as JSON or Download record as JSON. Use this for incidents, repairs, access checks and token renewals. You do not need to prepare a full export. You do not need another server request.

The row uses Export privacy. It starts with Privacy mode (aliases). Names and IDs become aliases for that one record file. Each file has its own aliases. Equal aliases across files do not prove a match. Dates, providers and outcomes remain. Review the file before sharing. Choose Names and IDs (local use) to keep saved names and IDs. Keep that file for local use.

The file keeps the whole saved entry. It has its type and recorded outcome. Credentials and raw provider errors are left out. Live rows have no known source snapshot details. Its date, scope and row position are unknown. You cannot add source context. The filename uses the record type and privacy mode. You can reopen the JSON with Choose history JSON. You can also use Open pasted history. This does not check access now. It does not prove recovery.

Closing the row clears its old actions and copy text. Changing privacy does too. A successful history refresh uses the newly loaded records. Focus in an old record moves to its Export this record control. If the row is gone, focus goes to Refresh history. Newer focus stays where you put it. If a refresh fails, the old record stays. You can still export it. If the browser cannot copy, choose Select record JSON. Then copy the text yourself. If a full record exceeds 8 MiB, try aliases.

#Preview a live history record

In Connection incident history, open Export this record on a row. Choose Preview this record. History record preview shows the exact entry you can export. It works for incidents, repairs, access checks and token renewals. No new server request is needed.

The preview uses the selected Export privacy mode. It keeps the row's same JSON and filename. Search it, inspect fields, or copy and download the whole entry. A search with no match still lets you download it. Source snapshot details and other records are not included. This does not check access now or prove recovery.

History refreshes do not change this captured preview. They also keep any newer focus choice. Opening another live record replaces it. Changing export privacy clears it. Open it again for the new mode. Full exports and files you opened keep their own previews.

Close preview returns to the row's preview button if still shown. The control is brought into view too. If that button changed or closed, focus goes to the row's export control. If the row is gone, focus goes to Refresh history. Newer focus stays where you put it. If the preview fails to open, you can still copy or download the row.

#Compare two saved history reports

Open History. Go to Open saved history. Choose or paste a whole report. Use a file saved with Names and IDs (local use). Open Compare saved snapshots. Choose Use opened report as baseline. Open the second report. Choose Compare with baseline. Use two files from the same Recued server. The files stay in this browser tab.

The view matches saved types and IDs. It shows four groups:

  • Only in comparison: the second file has this record. The first file lacks it.
  • Changed saved data: matching IDs have different saved fields.
  • Only in baseline: the first file has this record. The second file lacks it.
  • Same saved data: matching IDs have the same saved fields.

A missing record does not prove recovery, deletion or lost access. The second file may hold an old event. It may have been saved later. The view flags scopes or filters that differ. It shows if the second capture time is earlier or the same. It keeps your chosen sides. These dates and limits are what each file says. This does not test access now.

Use Show records to pick a group. Use Find saved record ID to find one. Use the page buttons to browse. Inspect baseline record shows the first saved copy. Inspect comparison record shows the other saved copy. Choose Include source context to keep source details in the saved JSON. These include the record's place in its source file.

Each alias file gives names on its own. Those names cannot link records across files. Single records cover just one row. Related bundles cover just some rows. You can still open and read them. Clear baseline and comparison drops the pair. It keeps the opened file. Clear opened history clears both sources. Closing the main file preview does this too.

#Read changed saved values

Compare two saved reports as shown above. In a changed row, open a field by its name. Baseline saved value comes from the first file. Comparison saved value comes from the second file. Each side shows the row's place in its source report.

The text is saved JSON. It keeps nested lists and details. For example, false is not a missing value. Not saved in this report means that file lacks the field. This does not prove that access was lost or data was removed. It does not check access now.

Large values use less space between their parts. No value is cut off. Focus the value with Tab to scroll with the arrow keys. On a small screen, the two sides stack. You can still inspect either whole record and save its JSON. Close the field when done. The source files stay the same.

#Copy a comparison summary

Compare two saved reports, then choose Copy comparison summary. The text covers all changes in that pair. The row filter, ID search and page do not change it. It lists changed field names and each side's saved outcome. It keeps source dates, scopes, row places and limits. Rows with the same data are counted but not listed.

The text has saved IDs and scope names. Review it before you share it. It leaves out field values, app labels, file names and search text. It does not check access now or prove that a missing record was fixed. Use the source JSON for all saved fields.

Choose Download comparison summary (.txt) to save the same text as a file. Its name shows the two saved capture times, with the baseline first. It leaves out account names, IDs and source file names from the file name. The text inside still has saved IDs and scope names. Review it before sharing. This text file cannot be opened as a history JSON report. Recued shows when it asks the browser to download the file. Check your browser's downloads to confirm that it was saved. If download is blocked, retry or use Copy comparison summary.

If copy is blocked, Recued shows plain text you can select and copy. Select comparison summary selects all of that text. Use Arrow, Page, Home or End keys to scroll the focused text. If the pair is too large, save smaller reports and compare them again. Opening a new valid report or clearing the pair drops the old summary. A history refresh keeps it.

#Save and reopen a comparison pair

Compare two Names and IDs reports, then choose Save comparison pair (JSON). One file keeps both complete reports, with the baseline first. It keeps their saved values, account and app labels, IDs and source search text. Review the file before sharing it. It is for local use. The text summary above leaves out more details.

The whole pair must fit within 8 MiB. Neither side is cut off. If it is too large, keep the two source files or use smaller reports. The file name has both saved capture times, with no account names or IDs. Row filters, ID search, paging and a history refresh do not change the saved pair.

Choose that file in Open saved history, or paste its JSON there. Recued checks both reports and compares them again. It opens the saved pair in the same order, even if the second date is earlier. The main file preview shows the comparison report as saved in that pair. Download comparison report (JSON) saves just that report. Use Save comparison pair (JSON) in the results to keep both reports. Use Inspect baseline record to read a saved row from the first report. Use Inspect comparison record to read one from the other report.

The pair opens with all differences on the first page. It does not save row filters, ID searches or page choices. An invalid file keeps the earlier pair open. Clearing the baseline keeps the comparison report in the file preview. Closing that preview or clearing opened history drops both sides. Opening a pair does not check access now or verify the source server. Use reports from the same Recued server.

#Swap baseline and comparison

After comparing reports, choose Swap baseline and comparison. It works for two opened reports or a reopened pair. Recued compares the same saved data in the reverse order. It does not read the files again. Counts, saved values and source positions follow the new sides. Capture dates do not choose the order for you. The source labels in a reopened pair name its original saved sides.

Copy, text download and Save comparison pair (JSON) use the displayed order. Swap again to restore the first order. Reopening a saved pair keeps the order you saved. Each swap shows all differences on the first page and clears the ID search. It also closes any inspected record.

The new baseline stays selected when you open another report. The main file preview stays on the report you opened. Its download still saves just that source. Use opened report as baseline refers to that preview. If that report is already the baseline, open another report to compare. You can also swap the displayed pair again.

Swapping pauses while a file is being read. A failed read keeps the current pair and lets you swap again. Opening a valid report or clearing the pair drops the old result. Draft edits and a history refresh keep its order. Swapping does not check current access or change any connection.

#Open a full comparison source report

Compare two reports or reopen a saved pair. Choose Open baseline report or Open comparison report. The whole source opens in the inspector below the comparison records. Its title, source label and saved date show which report you chose. It does not read the file again or check access now.

Search and page through that source to read its saved fields. Its search and paging stay separate from the comparison view. Changing the comparison filter, ID search or page keeps the source open. A history refresh keeps it too.

Download baseline report (JSON) saves the whole baseline source. Download comparison report (JSON) saves the whole comparison source. Search and paging do not limit these downloads. Each file keeps saved values, names, IDs, app labels and source search text. Keep it for local use and review it before sharing. Use Save comparison pair (JSON) to keep both reports together.

Close the inspector to return to its source button. Opening the other source or inspecting a comparison record replaces this view. Each source opens on its first page with no search applied. The main opened-file preview stays on its own report.

Swapping or replacing the pair closes the source view. Clearing the pair or closing the main file preview closes it too. The source buttons then follow the new roles. An invalid file or a draft edit keeps the earlier source open. The saved dates, scope and limits remain source claims.

#Open a comparison record in its full source

Find a record in Compare saved snapshots. Choose Open baseline record in full source or Open comparison record in full source. Each action shows only when that source includes the record. The full report opens on that record's page. The record opens and shows its source position. You can browse other records and follow saved links. Downloads still save the whole report.

Choose Back to comparison beside the record or above the search. Your comparison keeps its filters, ID text and page. Focus returns to that row when it is still shown. If you changed the view, the row may be hidden. Recued then explains this and keeps your current view. That note clears when you inspect another record. You can also use Inspect baseline record or Inspect comparison record. Those actions open just one saved record. No action here checks current vendor access.

#Return to the previous record

Open a full history report and follow View referenced … in a record. Choose Back to previous record to return. You can find it beside the linked record or above the page controls. It opens the previous record and restores its search and page. Search text you had not yet applied comes back too. You can search or change pages before going back. If a field outside these records takes focus during your click, it keeps focus.

Each saved link adds a step to this trail. Back and Forward share the last 20 steps. If you follow more links, it drops the oldest steps and shows a note. Once those steps are gone, you cannot go back to them. Closing or replacing the preview clears the trail. The trail stays in this browser tab and is not saved in downloads.

Back builds a fresh view of that page. Nested field details and copy messages start fresh. The saved values and source context stay the same. Downloads still save the whole report. In a comparison source, Back to comparison returns to the comparison view. That view keeps its filters and page. A file with just one record has no other records to follow. These links do not check current vendor access.

#Go forward after Back

After going back, choose Forward to next record. Find it above the page controls or beside the open record. It restores the page, search and draft you left. If the record was still on that page, it opens. If you had moved away, your saved page comes back. An empty search stays empty. Focus then goes to the record count.

Search and page changes keep Forward ready. Following another saved link drops the old Forward steps. Back and Forward share 20 steps in all. Closing or replacing this preview clears both. Both build fresh views of the same saved data. Old buttons and copy replies stay retired. A field you choose outside the records keeps focus. This also holds while the record list changes. Downloads and source context keep the same saved values. No step checks current vendor access.

#Copy an incident timeline for support

Open a saved incident in a preview. Choose Support timeline, then Copy support timeline. The text shows saved events and their UTC times. It keeps that preview's privacy mode. Aliases stay the same. Names and IDs stay marked for local use. Read the text before you share it.

A full report follows saved links to find more records. It also finds those hidden by preview search. A shared repair may link two incidents. The text may include both. For an opened bundle, its main incident uses the saved links. Other incidents in that bundle copy just their own events. A single record copies only that incident. It keeps any known source details. It does not invent what is missing.

Repairs, read checks, renewal and recovery stay separate. Their order does not prove that a repair caused recovery. Some old records lack saved success times. The text says when those times are missing. This does not check access now. Use saved JSON if you need all the saved fields.

If copy fails, choose Select support timeline. Then copy the text yourself. The text must fit within 8 MiB. It makes no new server or vendor call.

#Read a single history record

Live, opened and pasted records show a short summary first. It lists the record type, saved outcome, ID and UTC dates. Privacy mode and the access-check notice stay visible. Choose Inspect record fields to read or copy the full entry. Search still looks inside closed fields. Search and clear keep the focused control in view. Choose About this record for its source, size and privacy details. These details start closed. Single records have no report counts or record-page buttons. Downloads keep the same complete JSON.

#Copy one saved record

Open a record in the history preview, then choose Copy record as JSON. You can do this without a search. It copies that whole saved entry, with its type and recorded outcome. Unopened details and later list pages are included. From a report, it keeps that report's names or aliases. From a lone record, it keeps the saved fields as opened. Saved aliases have meaning only within their source snapshot. References can point to other records outside this copy. The copy is one entry, rather than a full history export.

If your browser cannot copy, choose Select record JSON. Then use your browser's copy command on the selected text. The JSON field is read-only. Refresh keeps your selected text. You can still search, open fields and copy a single value. The full saved file stays unchanged.

#Download one saved record

Open a record in the history preview, then choose Download record as JSON. This saves one entry, with its type and recorded outcome. It contains the same data as Copy record as JSON. Unopened details and later list pages are included. It keeps the names or aliases shown in the preview. Saved aliases have meaning only within their source snapshot. References may point to other records outside this file.

From a report, the filename uses its date, record type and known source position. A reopened related bundle may not know a record's source position. If unknown, that part is left out of the name. Without source context, a lone record's filename uses only its record type. With source context, the name can use its saved date and known position. Searching the preview or refreshing history keeps that name and saved data. Recued says when the download is requested. Your browser controls the saved file. If the download cannot start, try again or choose Copy record as JSON. Use Download this preview (JSON) to save all records in the preview.

Open an incident in the history preview, then open Related history bundle. Review the record counts, missing references and saved detail limits. Choose Download related history (JSON) to save the bundle.

The bundle follows saved links between incidents, repairs and access checks. It follows links in both directions, including checks of earlier checks. A shared repair may bring other incidents and their linked records into the file. Matching an account, app or group alone does not create a link. Records stay in snapshot order and appear once each.

This uses the whole prepared snapshot, including pages you have not opened. Searching the preview does not remove linked records from the bundle. The selected privacy mode still applies. Aliases keep their snapshot meanings. The filename uses the snapshot date and the incident's original position.

The file includes its source scope, filters and retention limits. Missing references are marked. Saved incomplete-detail flags stay visible. Records excluded from the snapshot cannot be found by this action. Zero missing references does not mean the history is complete. Related records do not prove that a repair caused recovery. Current vendor access is not checked.

Refresh keeps the reviewed bundle and its saved values. A refused download can be retried. Bundles must fit within 8 MiB. You can use Download this preview (JSON) to save the source snapshot instead. Recued reports a download request; your browser controls the saved file.

Open Related history bundle, then choose Copy related history as JSON. It copies the same whole bundle as the download. The root, saved records, missing links and report limits are included. It keeps the snapshot's privacy mode and aliases. Search and open pages do not change what is copied.

If your browser blocks copying, choose Select related history JSON. Then use your browser's copy command on the selected text. The JSON is read-only. You can retry copying or use the download. Copy and download keep their own messages. Refresh keeps your place and selected text. Newer focus and edits stay in place when a pending copy ends.

The bundle must fit within 8 MiB, just like its download. If it is too large, capture a smaller history export. No more history is fetched and vendor access is not checked.

In Related history bundle, open Browse related records. This lists the exact records included in that bundle, in snapshot order. The chosen incident is marked Selected incident. Open a record to read its saved details, including its recorded outcome. Names appear only if you chose the mode that includes names and IDs. Aliases keep the same meaning as in the source snapshot.

The list shows 20 records at a time. Use Previous related records and Next related records for other pages. Long detail lists have their own page controls. The preview search stays as you left it, even for records it would hide. Refresh and closing then opening the list keep your page and open details.

Choose Return to bundle download to focus the download button. This does not start a download. Browsing does not change the file, fetch more history or check vendor access. The bundle's missing references and saved detail limits still apply.

Inside Browse related records, enter text in Search related records. Choose the search button or press Enter. Search finds saved IDs, aliases, labels, outcomes and fields inside closed details. It ignores case and matches plain text, with no special patterns. Names that were removed in alias mode cannot be found.

The count shows matching records and the total in the bundle. Page controls move through matches in their saved order. Clear related search removes the text search and keeps your type and outcome filters. It brings you back to the search field. Use up to 128 characters. A longer query leaves earlier results in place. Typing alone does not apply a new search.

Each open bundle has its own search and pages. Refresh and closing then opening the list keep your search and draft text. The main preview search stays as you left it. Even with no matches, the bundle download still saves all its records. Return to bundle download remains available. Search does not fetch more history or check current vendor access.

Inside Browse related records, choose a Record type or Recorded outcome. Both start at All. They offer the types and outcomes found in the whole bundle. Choices stay available when your search or another filter hides those records. An outcome describes a saved observation. It does not confirm current access.

Filters apply right away to your last applied text search. Text you are still typing stays in the search field until you choose Search. Pressing Enter on a filter keeps that unfinished text. Enter in the search field applies it. A query error stays in place until you fix or clear that text. Each change starts at the first page of matches, in saved order. The count also shows how many records are in the complete bundle.

Type, outcome and search must all match. If nothing matches, change a choice or clear the text. Clear type and outcome filters removes both choices and keeps the text search. It also keeps text you are still typing and any query error. With no filters set, this button leaves open details in place. When reset removes a record that still has focus, the visible count takes focus. A newer focus choice stays in place.

Each bundle keeps its own choices. Refresh and closing then opening the list keep them. Back and Forward keep your current results and filters. Saved links can still open records outside the filters. Those views name the filters used when they opened and explain the difference. Back keeps any newer choices you made in the related results.

Filtering changes the list you see. Downloads and copies keep the complete saved record, bundle or source report they describe. Original aliases and source positions stay the same. No more history is fetched and current vendor access is not checked.

After a related search, each result shows how many saved fields match. Open the record to see the field names and nearby matching text. Long values show an ellipsis where text was left out of the preview. Use Previous matches and Next matches to review more fields. At a page boundary, the focused count stays in view.

Choose View field to open the full saved value. Recued opens any closed details and the right page of a long list. Matching text is highlighted. A field name can also match on its own. Use Previous hit or Next hit for repeated text in a value. Return to matching fields brings you back to the field's result page.

Each bundle keeps its own search, highlights and return path. The main preview stays as you left it. Refresh keeps your place and draft text. Changing the related search or record page replaces those results. The downloaded files still contain their original saved records. This view does not fetch more history or check vendor access.

#Follow linked history records

Open a record inside Browse related records. Its Linked saved records section shows two kinds of link:

  • References points to another record named in this saved entry.
  • Referenced by points to a saved entry that names this record.

Choose View linked incident, View linked repair or View linked access check. The record opens inside the same bundle, even if it is outside your related search. The search stays as you left it.

Use Back to related results or Back to previous record to return. Recued restores the view you left, including its search draft, pages and open details. Focus returns to the link you followed. You can follow more links from each opened record. Back and Forward share up to 20 linked records. At the limit, use Back before following another link.

Long link lists use Previous links and Next links, 20 at a time. Missing records and references with a different record type cannot be opened. No lookup is made for them. The bundle's saved limits still apply.

Each bundle keeps its own navigation and search. Refresh and collapsing then opening the list keep your place. Return to bundle download remains available, and the files stay unchanged. Following a link does not check current vendor access or prove that a repair caused recovery.

#Go forward through linked records

After Back, choose Forward to next record. Find it above the related search or beside the linked record. It returns to the same view, with its open details. Link pages, array pages, copy text and source choices stay in place. A copy you started may finish while its view is hidden. Forward shows that result without starting another copy. Hidden views cannot run their controls.

Search and page changes in the related results keep Forward. Each linked view keeps the field search it opened with. Back keeps your current related results. If its old link is gone or inside closed details, focus goes to the count or the previous heading. The details stay closed. A field you choose outside this view keeps focus.

Following a new link after Back drops the old Forward steps. Both directions share the limit of 20 linked records. Refresh and closing then opening the list keep your place. Replacing or closing the preview clears both directions. Return to bundle download keeps the trail and starts no download. The files and saved source details stay the same. No step checks current vendor access.

Open a record in Browse related records or follow a saved link. Choose Copy record as JSON or Download record as JSON. Both use the whole saved entry, with its type and outcome. They keep the snapshot's privacy mode and aliases. The file name is the same as in the main preview. Links in this one record may point to records outside the file.

These actions keep your search, pages and open details in place. Each view keeps its own copy and download messages. If you follow a link while a copy is pending, it can still finish. Use Back to see its result. If copying fails, select the shown JSON and copy it yourself. A failed download can be tried again. The whole preview and bundle files stay unchanged. No more history is fetched, and vendor access is not checked.

#Copy a saved field value

Choose View field, then Copy saved value. This copies the whole saved value from this snapshot. The field name and buttons are left out. Privacy aliases stay aliases. Codes keep their saved spelling. Dates copy their saved number. Values shown as Yes or No copy as true or false. If the saved form differs, the copy controls show it.

If your browser cannot copy, it shows a field for manual copy. You can select its text but cannot edit it. Choose Select saved value, then use your browser's copy command. Control+A or Command+A inside the field selects that value. Selecting text alone does not copy it. Refresh keeps the manual field and your selected text.

A new field, search or privacy choice clears old copy controls. Copying leaves the full saved file unchanged.

#Return to matching fields

Choose Return to matching fields beside the opened value. It takes you back to that match's View field button. If you changed match pages, it restores the right page. Your search, draft text and opened lists stay in place. History refresh keeps this button and its focus.

Opening another field moves the return button to that field. Paging away from a field removes its return button. Choose View field again to open it with a new button. Old buttons cannot act after a search or privacy change. Returning reads the captured report and leaves the download unchanged.

#History export privacy

Privacy mode replaces names and IDs with short aliases, such as connection-1. It removes labels, messages, search text and original ID fingerprints. The same alias links known records within one file. Aliases have no meaning across files. They cannot open accounts in Recued. The file has no key that maps them back to names. Some saved references lack enough detail to link them. Those stay separate. Dates, vendors, results and gaps in the saved facts remain. Review the file before sharing. These facts may still reveal details.

For local use, choose Names and IDs (local use). Then choose Preview export and review it before downloading. This file keeps account and app names, IDs, known uses and applied search text. Both file types omit credentials and raw provider errors. The choice stays while you read this page. A new visit starts in privacy mode.

#Verify access after a repair

In Incident history, find a saved repair. Choose Verify access. You can also choose it on an account in Authentication repairs. The review reads local settings. Choose Run checks to make vendor calls. Checks use the sign-in saved now. An old repair may have used a different sign-in. Close the review before Run checks to release it. If a stale review cannot start, choose Review again.

For an API read, check the resource URL. It must need sign-in. It must use that connection's saved vendor API. For Sheets, you can paste a Google Sheets link. Leave the URL blank to keep that API read Unconfirmed. Mail and Calendar checks read the saved account. They check its chosen folders or calendars. They do not wait for sync.

For files, the base check reads file metadata. To check file bytes too, choose Choose a file. Pick a saved file. Then choose Use this file for verification. Recued does not choose a sample. The check allows up to 10 MiB. The file is not kept or sent to an AI service.

#Read access-check results

Checks run in the background. You can close the panel while they run. Choose View access check to read its saved result. You can also refresh incident history. Refresh check status reads that result. It makes no new vendor calls.

Each listed read shows Passed, Failed, or Unconfirmed. If a check renews a token, Recued must save it before the read can pass. Sending, editing and workflow execution remain unconfirmed. A successful read covers only the checked resource. It does not prove that a new app secret can refresh a token. Related Packs, recipes and schedules are listed. They are not run. Sync state, failed jobs and incident recovery stay separate.

Superseded means the saved sign-in or source changed after the check. If Recued is locked, it may be unable to compare saved sign-ins. Unlock it and refresh before relying on an earlier result. A check interrupted by a server restart stays unconfirmed. Choose Review new checks to run a fresh check.

#Get alerts about connection problems

Recued reads saved status once a minute on your server. This works when the app is closed too. It makes no calls to vendors for this check. Has a sign-in or access check been refused? Recued can alert you on the next check. Other access or setup errors must last for 15 minutes first. Their cause may still be unknown. A network error may need time. A new sign-in may not fix it.

Alerts appear in Notifications. They use the channels you turned on in Settings → Notifications. They show known uses of the account and a repair link. Open it to review the saved account or source. For a sign-in problem, choose Manage authentication. The same error on the same account does not keep sending alerts. The cause may be unknown at first. If a later check proves access was refused, Recued alerts you once more.

For an app secret date, Recued warns at 30 days and 7 days. It warns when the date is reached too. Set a nearer date and it starts with that warning. These checks use the date on your server's clock. You enter this date. It does not prove the vendor stopped access. Change or clear it to end the old reminder.

#Resolve a connection alert

After a repair, each failed use needs a later check or sync that works. Only then can Recued send a notice that it worked again. New secret keys, an old sync, or missing status is not enough. A test that only reaches a public API root is not enough. For an API, each failed request needs a check of that same resource. A call to a different resource is not enough. Remove an account to end its alert. This does not claim it works again. Old alerts stay in your history. An alert may fail to reach a channel outside Recued. Use the repair list to see the saved status now.

The checks pause while the vault is locked or the server is paused. An alert does not change authentication or repeat failed jobs.

#Switch a cloud file source's sign-in

Open Data → Files and choose the cloud source you want to keep. Choose Manage authentication, then Change authentication method. You can also open its saved connection in Connections → Apps & APIs. Choose Manage authentication, then Change authentication method there.

This works for Google Drive, Dropbox, Box, OneDrive, and SharePoint. Choose Verify this file and continue after selecting a saved file, or choose Continue with metadata only. Recued then checks the account and metadata. The existing source must work. Large sources can take longer to check.

Direct OAuth is the first choice. Choose a saved OAuth app or enter your own app, then sign in with the same account. You can also choose Managed OAuth, a broker profile, and its account. You can reuse a saved Nango account or sign in there. The reverse switch from Nango to direct OAuth works here too.

#Review a file-source sign-in switch

Review the account, permissions, file count, and saved location. Recued compares complete metadata listings from both sign-ins. A different or unknown account, missing file access, or an incomplete list blocks the switch. Metadata-only checks do not download file bytes or prove download permissions. Write permissions remain separate.

Choose Verify and switch to apply. Your source ID and connection name stay the same. Recued keeps your mirrored records and links from your work. It keeps the import scope, drive or folder choice, and sync cursor. The next sync uses the new sign-in. A vendor may still expire a cursor; the adapter uses its usual reset path.

If files change during review, reopen Switch authentication to check the original source again. A review lasts 30 minutes. If a check fails, the old sign-in stays active. If a reply is lost, use the saved credential result to check what happened. That status check does not repeat sign-in or apply the switch again.

Local folders, S3 keys, and Notion tokens keep their own setup flows.

#Verify a file download or export

When starting a file source's sign-in switch, choose a file yourself. Search the saved files by name or path, then choose Verify this file and continue. Recued never picks a sample for you. If a file is missing, sync the source first. If it is too large or cannot be exported, the list shows why.

Recued checks the file with the current sign-in first. Then you choose a new sign-in. It must pass the same check during review and before the switch. Downloads must return the same bytes. Google Docs, Sheets, and Slides use the same DOCX, XLSX, and PPTX exports as normal file reads. Exports must match the file and format. Their bytes can differ with each read.

Each check allows up to 10 MiB and 60 seconds. The check uses the bytes in memory. Recued does not add them to your records or save an attachment. It does not send them to AI. The preview shows the file's name and path, if known. It shows the format and check result.

If a check fails or cannot prove access, your old sign-in stays. A public file cannot prove sign-in access. Choose a private file. If the file changes, reopen the switch and check it again. Turning off the remote file-fetch capability also blocks this switch.

Continue with metadata only is an explicit choice. Its preview says that download/export access was not checked. A passed file check covers that file and format. It does not prove access to every file or writes.

#Use a saved connection for file sync

File sources and remote file reads can use a managed API connection for Google Drive, OneDrive, SharePoint, Box, Dropbox or Notion. Choose that saved connection in the usual source form. Recued uses the same file readers as with direct credentials. Your packs and recipes need no changes. S3 keeps its access key setup.

#Remove a Nango account

Removing a Recued connection keeps its Nango account. To delete that account too, use Manage OAuth brokers. Choose its integration; Recued loads its accounts. Select an existing account and open Delete this account from Nango. Remove its Recued connections first, then type the account ID to confirm. Every other tool using that Nango account loses access too. The vendor may keep its consent until you revoke it there.

#HubSpot: a key or your own app

HubSpot gives you two ways in. You pick one under How to connect.

A Service Key is the easy way, and it suits most people. You make a key in HubSpot and paste it into the form. It is under Development → Keys → Service keys. You need to be a Super Admin there, or have Developer tools access. There is no app to make and no sign-in. So it works from any address, 127.0.0.1 too. When you save, Recued tries the key. So a wrong key shows at once.

When you make the key, tick the scopes the form lists. They let packs read your records and change them, and every change still goes through Recued's approvals. For a key that only reads, skip the second group. When you save, Recued also reads which scopes the key has. If a pack needs one the key lacks, the pack's page names it under Connections. Add that scope to the key in HubSpot. Then click Test connection on the connection, so Recued reads it again. HubSpot suggests a new key every six months. Paste it into the same connection.

Your own app is the hard way. HubSpot makes new apps only with its command-line tool. That needs sandbox access, which only paid HubSpot plans have. So on a free account, use a Service Key. With an app, you sign in through it.

#Apps sign in through a callback

Direct Salesforce OAuth takes your own app, a Connected App. It also has a sandbox switch.

An app sends each sign-in back to a callback address. Recued shows the right one on the form. It depends on where you open Recued:

  • On app.recued.com, it is https://app.recued.com/oauth-callback. That page only hands the code on to your server.
  • At your server's own HTTPS address, it is /oauth/complete there. The vendor sends the sign-in straight to your server. So under Settings → Server → Exposure, the /oauth/complete row must be Public.
  • At localhost on the server, your server's own page takes it. The start-up log prints 127.0.0.1, but HubSpot will not take a callback at a number. So open http://localhost:7717/webclient to connect. Is that address new to your browser? Pair it once, like a new device. You connect once. After that, the connection works from any address.

The first two need an address the internet reaches your server at. A Pro address counts, and so does your own domain once Recued has checked it. Reachability shows how to get one.

For your own OAuth app, your server does the token swap and stores the tokens. A managed OAuth connection uses its chosen broker instead.

After you sign in, Recued checks what the provider really allowed. For a HubSpot app, it checks the granted scopes. For Salesforce, it probes which objects it can see. Is something missing? You see a warning on the capability that needs it. A capability is one thing a pack can do. Nothing is hidden.

#Where credentials live

A credential is a secret, like a key or a token. Direct credentials stay on your server. Only the connection executor uses it, and only at the moment of a call. A recipe can read the non-secret fields of a connection. The secret key never goes into recipe data or step outputs.

With managed OAuth, the broker keeps the vendor credentials and sees the API requests and replies. Its API key stays encrypted on your Recued server. You choose the broker; Recued Cloud does not hold those credentials or route those calls.

#What connections power

  • CRM records in the warehouse. Your server checks them against the vendor and fixes differences. Webhooks or streaming make that faster.
  • Outgoing notifications. For example, sending email to many people through one named target.
  • MCP tool servers that your recipes can call.

#Sending mail

A mail account says whether it can send. The server checks that at the moment it sends, and refuses a send from an account that cannot. A guard also refuses mail a recipe sends from an address to that same address, so it cannot loop. Your own notifications are the one exception. An email notification connection with no recipient sends them to the mailbox it sends from, so one mailbox is enough. Recued marks each one as its own, so nothing that watches that mailbox reacts to it. You can answer by replying from the same mailbox. Outgoing mail goes from your server straight to your mail provider. It never goes through Recued's cloud.

#Choosing a mailbox

Each mailbox is a connection of its own, under the name you gave it. Some recipes ask which mailbox to use. Their settings show a list of your mailboxes, so you pick one instead of typing its name. A recipe that sends lists only the mailboxes that can send. When just one fits, the list starts on it, and saving keeps it. Calendars work the same way.

#Lifecycle

A recipe names no connection. Each pack keeps a list of connections, and its recipes use the one you chose, else the pack's default. Before you delete a connection, Recued says where each pack's runs go next. Grants attach to installed packs. So you can change what a pack may do without setting up the secret key again.

Recued Docs

Search documentation

Start typing to search the documentation.