Augment support

Last updated date:

Connect, reconnect, and troubleshoot Augment without sharing credentials or customer content through support channels.

1. Before you start

  • Obtain an Augment API key and webhook capability for the intended brokerage from an authorized Augment account manager.
  • Choose live only for an approved production pilot; the test option requires a configured HTTPS provider test host.
  • Review and accept the account-wide, write-capable credential risk and the prospective-only coverage boundary before connecting.
  • Do not send Augment credentials, customer content, personal information, or private record data by email or through an ordinary support ticket.
Augment authorizationAugment's official API authorization reference.

2. Connect Augment

  1. In Seedling, open Connections and choose Augment.
  2. Connect from workspace scope as a current Seedling workspace administrator.
  3. Enter the matching live or provider-test environment, API key, optional brokerage label, and the required account-wide credential-risk acknowledgement.
  4. Seedling verifies the configured environment and webhook capability, creates only Seedling-owned subscriptions and endpoint state, and does not activate a partial setup.
  5. Allow the first Augment synchronization to finish, then verify the expected resource population and member access policy.

3. Authorization and connection problems

Augment API key rejected
Confirm the augment api key is active, was entered without surrounding whitespace, and belongs to the intended Augment account and environment.
Missing permission or resource
Restore the exact read permission or provider-side resource access described in this guide. Seedling does not substitute a broader credential or silently treat a forbidden Augment population as empty.
Wrong account or scope
Disconnect before retrying with the intended Augment identity, account, and Seedling connection scope. Seedling does not infer account ownership from a display name or email address.
No historical loads
This is the released product boundary, not a retry condition. Seedling cannot reconstruct loads that produced no supported event after activation.

4. Missing or delayed data

  1. Confirm the load produced a supported webhook event after the connection became active; pre-activation history is unavailable.
  2. Check receipt status, webhook subscription health, the exact load number, and whether the current-load refresh completed.
  3. Confirm the member has the applicable exact-connection load, tracking, carrier-issue, or workflow declared scope.
  4. Allow incremental synchronization and provider retry handling to complete. A temporary provider failure does not delete previously synchronized data.
  5. If the issue remains, contact support@tryseedling.ai with the Seedling workspace, safe timestamps, and non-sensitive provider record identifiers. Do not include credentials or record contents.

5. Rotate or replace access

Never use email or an ordinary support ticket to transfer the old or replacement credential.

  1. Create replacement augment api key for the same Augment account with the same or narrower released permissions.
  2. Replace the credential on the exact Seedling connection and repeat identity, scope, and capability verification.
  3. After Seedling confirms the replacement, revoke the old augment api key in Augment.