You are here:
Coda Connector (Beta)
Connect to an external Coda account. Perform tasks like retrieving documents or managing pages. Use Coda as a data target (action).
Required Editions
| View supported editions. |
| This feature requires the MuleSoft for Flow: Integration add-on. Professional Edition requires the API access add-on. To purchase, contact your Salesforce account executive. |
| MuleSoft for Flow: Integration features used with Agentforce require the Foundations or Agentforce 1 edition. To purchase these editions, contact your Salesforce account executive. |
Connections
To connect to a system, whether it's a data source or a data target, create a connection with that system's standard connection or with an existing external named credential. You can connect to multiple systems within a flow and reuse each connection. You can create connections in the Integrations tab or in Flow Builder.
Standard Connection
This system uses Bearer authentication.
Bearer authentication sends a header named Authorization with a value of Bearer and a token with every request.
This system requires this credential information for its connections.
| FIELD | DESCRIPTION |
|---|---|
| Connection Name | Enter a unique connection name that helps you remember the details of this connection. Salesforce hides the credentials after you create the connection. Reuse connections as needed. Anyone with the Manage Integration Connections permission can see and use all connections in the org. |
| Token | Enter the bearer token to use to authenticate the requests. For information about how to create the bearer token, refer to the external system's documentation. |
| URL | Enter the URL of your instance. |
Named Credential Connection
Select a pre-existing named credential from Setup to use for your external system connections.
Before connecting to your external system with a named credential, first create or use an existing authenticated named credential and external credential that is enabled for your users.
To ensure a successful connection for use in a flow, use only one principal for each named credential.
- Use the same name for the named credential and its related objects, such as the external credential and external authentication identity providers. Labels for these objects can differ.
- Assign the user creating the connection the required user permission for the principal. Without this permission, the connection test fails and the connection remains inactive.
When you create a connection with an existing named credential, note these behaviors:
- Manage the named credential’s read-only details in Setup, not the Integrations tab. On the Integrations tab, you can only edit the connection's Connection Name and Description.
- Perform reconnections for the named credential in Setup. The Reconnect button isn’t visible on the Details page.
- Delete associated named credentials in Setup. Deleting a connection doesn't remove the credential.
Actions
An action performs a specific task or operation within a target system. Use actions to automate tasks across different systems without manual intervention, based on conditions set in the flow. For more information about actions, refer to Create a Flow with a Connector as an Action.
These Coda actions are available in Flow Builder.
- Add Custom Doc Domain
- Add Go Link
- Begin Page Content Export
- Change User Role
- Delete Custom Doc Domain
- Delete Doc
- Delete Page
- Delete Permission
- Delete Row
- Delete Rows
- Get Acl Settings
- Get Doc
- Get Folder
- Get Page
- Get Page Content Export Status
- Get Sharing Metadata
- List Categories
- List Controls
- List Custom Doc Domains
- List Docs
- List Formulas
- List Pages
- List Tables
- List Workspace Members
- List Workspace Role Activity
- Publish Doc
- Push Button
- Search Principals
- Unpublish Doc
- Update Acl Settings
- Update Custom Doc Domain
- Update Doc
- Update Page
- Whoami
For information about specific limitations for connections and third-party connectors, see MuleSoft for Flow: Integration Limits & Considerations.
