User guide

Slack

You need:

Permission to install apps in your Slack workspace.

The node can:

Post to a channel, edit a posted message, read recent messages.

1. Click Connect on the Slack card and approve the workspace.
2. In Slack, open the channel the agent should post to, right-click it, copy the link, and take the last part of it. That is the Channel ID.
3. Paste it into the node's Channel ID field in the agent builder.

For a private channel, type /invite @GeniSights in the channel first, or the post will fail.

Notion

You need:

Access to the Notion pages or databases the agent should use.

The node can:

Create a page in a database, update a page, fetch a page.

1. Click Connect on the Notion card.
2. On the consent screen, select every database the agent will write to. Anything you leave out stays invisible to it.
3. Copy the Database ID from the database URL (the 32-character id before ?v=) into the node's Database ID field.

To add a database later, disconnect and reconnect, and select it this time. Sharing it after connecting does not take effect.

Asana

You need:

An Asana account with access to the project.

The node can:

Create a task, update a task's notes, fetch a task.

1. Click Connect on the Asana card and approve.
2. Open the project in Asana and copy the long number from its URL. That is the Project GID.
3. Paste it into the node's Project GID field.

Webflow

You need:

A Webflow site on a paid site plan, with CMS collections.

The node can:

Create and update CMS collection items.

1. Click Connect on the Webflow card and authorise the site the agent should write to.
2. In the Webflow designer, open the collection's settings and copy the Collection ID.
3. Paste it into the node's Collection ID field.
4. Set the node's Payload to JSON in the shape Webflow expects, for example {"fieldData": {"name": "...", "slug": "..."}}.

Google Sheets

You need:

A Google account that can edit the spreadsheet.

The node can:

Add a row, update a range, read cells back.

1. Click Connect on the Google Sheets card and approve access on Google's consent screen.
2. Open your spreadsheet and copy the long id in its URL, between /d/ and /edit. That is the Spreadsheet ID.
3. Paste it into the node's Spreadsheet ID field. Create adds a row to the first tab.
4. To update or read cells, put the range (for example Sheet1!A2:C2) in the node's Item ID.

WordPress

You need:

A WordPress user who can publish posts.

The node can:

Create a draft post, update a post, fetch a post.

1. In WordPress, go to Users -> Profile and scroll to Application Passwords.
2. Enter a name such as GeniSights and click Add New Application Password. Copy the value. It is shown once, and it is not your login password.
3. In GeniSights, click Connect and paste the site URL, your WordPress username and that password.
4. On the node, leave Post type blank for posts, or set it to pages.

The same connection is shared with Publishing integrations. Connecting on one page connects it on both.

Shopify

You need:

Shopify admin access to create a custom app.

The node can:

Create a draft blog article, update an article, fetch an article.

1. In Shopify admin, open Settings -> Apps and sales channels -> Develop apps and create an app.
2. Give it the read_content and write_content Admin API scopes, then install it.
3. Reveal the Admin API access token (it starts with shpat_) and copy it. It is shown once.
4. In GeniSights, click Connect and paste your .myshopify.com store domain and the token.
5. On the node, set Blog ID to the last number in the blog's admin URL (.../blogs/123456789).

Articles are always created as drafts, so nothing goes live until a person publishes it.

Custom Website

You need:

An HTTPS endpoint on your site (or the hosted-blog receiver) that accepts published articles.

The node can:

Send an article to your site. Create only; it cannot update or fetch.

1. Set up the endpoint that will receive articles. The receiver kit in the project's integrations folder shows how to verify the signature.
2. Choose a signing secret of at least 16 characters and store it where your endpoint can read it.
3. In GeniSights, click Connect and paste the Publish URL and the same signing secret.
4. GeniSights sends a signed test request. You see Connected once your endpoint accepts it.

Every request body is signed with the secret, so your site can reject anything that did not come from GeniSights.

Contentful

You need:

A Contentful space where you can create tokens.

The node can:

Create, update and fetch entries.

1. Open Settings -> API keys -> Content management tokens -> Create personal access token. Copy it. It is shown once.
2. Note the Space ID from Settings -> General settings, and the environment name, usually master.
3. In GeniSights, click Connect and paste all three.
4. On the node, set the Content type ID and give the Payload as JSON, for example {"fields": {"title": {"en-US": "..."}}}.

Sanity

You need:

Admin access to the Sanity project.

The node can:

Create a document, patch a document, fetch a document.

1. Go to sanity.io/manage and open the project.
2. Open API -> Tokens -> Add API token. Give it Editor permissions. A Viewer token reads fine, but every write fails.
3. Copy the token. Note the Project ID on the same page and the dataset name, usually production.
4. In GeniSights, click Connect and paste all three.
5. On the node, set Document type to the schema type new documents should use.

Directus

You need:

A Directus instance and a user who can write to the collection.

The node can:

Create, update and fetch items in any collection.

1. In Directus, open User Directory and choose the user the agent will act as.
2. In that user's page, generate a static Token, then save the user.
3. In GeniSights, click Connect and paste the instance URL and the token.
4. On the node, set Collection to the collection's name.

Payload

You need:

A Payload CMS instance with API keys enabled on the users collection.

The node can:

Create, update and fetch documents in a collection.

1. In the Payload admin panel, open the user the agent will act as and turn on Enable API Key.
2. Copy the generated key.
3. In GeniSights, click Connect and paste the instance URL, the API key, and the auth collection slug (usually users).
4. On the node, set Collection slug to the collection to write into.

Drupal

You need:

A Drupal site with the JSON:API and Basic Auth core modules enabled, and an account that can author the content type.

The node can:

Create, update and fetch nodes.

1. Nothing to create. Use the username and password of an existing Drupal account with permission to author the content.
2. Ask whoever runs the site to enable the JSON:API and Basic Auth core modules, and to allow write operations under Configuration -> Web services -> JSON:API.
3. In GeniSights, click Connect and paste the site URL, username and password.
4. On the node, set Content type to its machine name, for example article.

Gong

You need:

A Gong admin to generate API access.

The node can:

Fetch calls and transcripts. Read only.

1. In Gong, go to Company Settings -> Ecosystem -> API and create an access key. This needs a Gong admin.
2. Copy the access key and the access key secret.
3. In GeniSights, click Connect and paste both.

Gong's API does not accept writes, so the node only offers Fetch.

G2

You need:

A paid G2 data subscription.

The node can:

Fetch review and buyer-intent data. Read only.

1. In My.G2, open Integrations -> API and copy your API token.
2. In GeniSights, click Connect and paste the token.
3. On the node, set Resource to what you want to read, for example ahoy-events or survey-responses.

PartnerStack

You need:

A PartnerStack account with access to API keys.

The node can:

Create and fetch partners and partnerships.

1. In PartnerStack, open Settings -> Integrations -> API keys.
2. Copy the public key and the secret key.
3. In GeniSights, click Connect and paste both.
4. On the node, set Resource to partnerships or partners.

Gamma

You need:

A Gamma Pro plan.

The node can:

Generate a deck or document from text, and fetch it. There is no update.

1. In Gamma, open Settings -> API access and create an API key.
2. In GeniSights, click Connect and paste the key.
3. On the node, set Format to presentation, document or social. It defaults to presentation.

X (Twitter)

You need:

The X account you want to post from.

The node can:

Post the node's payload as a post from the connected account.

1. Click Connect on the X card (here or under Publishing integrations) and approve on X's own page.
2. You are returned to GeniSights with the account shown as Connected. There is nothing to type.

The connection is shared. Connecting on either page connects it on both.

Facebook Page

You need:

A Facebook Page you administer.

The node can:

Post the node's payload to the connected Page.

1. Click Connect on the Facebook card and approve on Facebook's page.
2. Back in GeniSights, click Choose Page and pick the Page to post to.

Until a Page is chosen the card shows that a Page still needs to be selected.

Reddit

You need:

The Reddit account you want to post from.

The node can:

Queue the payload as a post. Nothing goes live until a person approves it.

1. Click Connect on the Reddit card and approve on Reddit's page.
2. When an agent queues a post, it appears under Pending Reddit posts on Publishing integrations.
3. Approve it there to publish, or reject it.

Frame.io

You need:

A Frame.io developer token.

The node can:

Stores the credential only. The node cannot create, update or fetch yet.

1. Open developer.frame.io -> Developer Tokens and create a token.
2. In GeniSights, click Connect and paste it.
3. To act on Frame.io today, use the Call API node against api.frame.io with the same token.

Frame.io V4 addresses everything by account and workspace id, which the node's single Target field cannot express.

Adobe Experience Manager

You need:

An AEM author instance and an access token.

The node can:

Stores the credential only. The node cannot create, update or fetch yet.

1. In the Adobe Developer Console, create a Technical account under Integrations and exchange it for an access token.
2. In GeniSights, click Connect and paste the author instance URL and the token.
3. To act on AEM today, use the Call API node against your instance.

AEM's authoring APIs differ per deployment, so there is no single mapping the node can make safely.

Basehub

You need:

A Basehub repo and a read/write token.

The node can:

Stores the credential only. The node cannot create, update or fetch yet.

1. In Basehub, open Repo -> Settings -> API tokens and create a read/write token.
2. In GeniSights, click Connect and paste it.
3. To act on Basehub today, use the Call API node to POST a GraphQL document.

Basehub is GraphQL-only, which the node's REST-shaped verbs cannot express.

Noble

You need:

API credentials from your Noble contact.

The node can:

Stores the credential only. The node cannot create, update or fetch yet.

1. Nothing to create. Use the API base URL and API token Noble gave you.
2. In GeniSights, click Connect and paste both.
3. To act on Noble today, use the Call API node against that base URL.

Noble publishes no public API reference, so no operation mapping could be verified.