Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.withampersand.com/llms.txt

Use this file to discover all available pages before exploring further.

What’s supported

Supported actions

This connector supports:
  • Read Actions, including full historic backfill. Please note that incremental reading is only supported for Insights, Topics, TopicModels, Chats, ChatMessages, Accounts, Contacts, Cases, Calls, Owners, Opportunities, Leads, Objects, TrackerProjects, TrackerIssues, and TrackerComments. For all other objects, a full read of the Four/Four instance will be done per scheduled read.
  • Proxy Actions, using the base URL https://fourfour.ai.

Supported objects

The Four/Four connector supports reading from the following objects:

Example integration

For an example manifest file of a Four/Four integration, visit our samples repo on GitHub.

Before you get started

To connect Four/Four with Ampersand, you will need a Four/Four account. Once your account is ready, you’ll need to create a Four/Four OAuth2 app and obtain the following credentials:
  • Client ID
  • Client Secret

Creating a Four/Four app

  1. Sign in to your Four/Four account as an admin user.
  2. Go to Settings > Connections > OAuth clients.
  3. Click ADD CLIENT and fill in the form.
  4. Under Redirect URI, add the Ampersand redirect URL: https://api.withampersand.com/callbacks/v1/oauth.
  5. Save your app settings.
  6. Copy the generated Client ID and Client Secret.

Add your Four/Four app info to Ampersand

  1. Log in to your Ampersand Dashboard.
  2. Select the project where you want to create a Four/Four integration. Alt text
  3. Select Provider apps.
  4. Select Four/Four from the Provider list.
  5. Enter the previously obtained Client ID in the Client ID field and the Client Secret in the Client Secret field. Alt text
  6. Click Save changes.

Using the connector

To start integrating with Four/Four:
  • Create a manifest file like the example.
  • Deploy it using the amp CLI.
  • If you are using Read Actions, create a destination.
  • Embed the InstallIntegration UI component. The UI component prompts the customer for OAuth authorization.
  • Start using the connector.
    • If your integration has Read Actions, you’ll start getting webhook messages.
    • If your integration has Proxy Actions, you can start making Proxy API calls.