Provides integration with Outreach for sales engagement resources, including prospects, accounts and users. Use template-driven reads, writes and provider actions to synchronize Outreach data with other systems.
0.0.0.3 - Provides template-driven queries and mutations with automatic paging and normalized mutation responses.
| Property |
Type |
Description |
ClientId |
String |
OAuth application client identifier. |
ClientSecret |
Masked |
OAuth application client secret. |
Scopes |
String |
Space-separated application scopes. Defaults to prospects.read accounts.read users.read. Select scopes for every operation you need. |
AccessToken |
Masked |
OAuth access token populated during authorization; an existing token may also be supplied. |
RefreshToken |
Masked |
OAuth refresh token used for automatic renewal. |
OAuthState |
Masked |
Managed during authorization. Start authorization again if this value is lost. |
TokenIssuedAt |
DateTime |
Managed token issuance timestamp used to control renewal. |
- Register an Outreach OAuth application and configure the callback URI shown by Flowgear.
- Enter
ClientId, ClientSecret and Scopes, then connect your account. Write permission does not imply read permission.
- Test the Connection using an account with
users.read permission. Account governance and application scopes both apply.
- Select a Method and operation template. Fill in
Options and connect request data for writes.
Select a Method and its template to populate the operation and its supported fields.
Reads resources with automatic cursor paging. Use Filter only for a template that declares a POST search body.
| Parameter |
Type |
Description |
Connection |
Connection |
Outreach Connection profile. |
OperationId |
String |
Operation identifier populated by the selected template. |
Options |
Object |
Route and query values required by the selected operation. |
Filter |
Object |
Optional body for a documented POST search. Ordinary query filtering is supplied through the selected Options fields. |
| Return |
Type |
Description |
Response |
Array |
Provider records without added mutation status fields. |
Creates resources or executes the selected POST action.
| Parameter |
Type |
Description |
Connection |
Connection |
Outreach Connection profile. |
OperationId |
String |
Operation identifier populated by the selected template. |
Items |
Array |
Complete request bodies, one item per provider request. |
Options |
Object |
Route and query values required by the selected operation. |
| Return |
Type |
Description |
Response |
Array |
Provider results with Flowgear.IsSuccess, Flowgear.Message, and a detached copy of the input in Flowgear.Request. |
Updates the resource selected by the operation and route.
| Parameter |
Type |
Description |
Connection |
Connection |
Outreach Connection profile. |
OperationId |
String |
Operation identifier populated by the selected template. |
Items |
Array |
Complete request bodies, one item per provider request. |
Options |
Object |
Route and query values required by the selected operation. |
| Return |
Type |
Description |
Response |
Array |
Provider results with Flowgear.IsSuccess, Flowgear.Message, and a detached copy of the input in Flowgear.Request. |
Deletes explicitly selected resources. Supply an empty object in Items for a bodyless delete.
| Parameter |
Type |
Description |
Connection |
Connection |
Outreach Connection profile. |
OperationId |
String |
Operation identifier populated by the selected template. |
Items |
Array |
Complete request bodies, one item per provider request. |
Options |
Object |
Route and query values required by the selected operation. |
| Return |
Type |
Description |
Response |
Array |
Provider results with Flowgear.IsSuccess, Flowgear.Message, and a detached copy of the input in Flowgear.Request. |
- Queries emit individual
data resources, preserving IDs, attributes and relationships. Requested related resources appear as JSON text in each row's included field. Transport paging links and metadata are not output records.
- Query paging is automatic. Use
Options.filter as JSON text, for example {"firstName":"Sally"}, when offered by the template. Legacy bracket-filter semantics apply.
- A sole object wrapper such as
data may be projected out of the template and restored in the request. Preserve sibling wrappers when the template exposes them.
- Each mutation item is a complete request body. Invocation-level
Options apply to all items; use a separate invocation for a different route. An empty input stream sends no requests.
- Validation and the first read or write complete while the Node invocation is awaited. Later pages and items run as the output is consumed. Startup errors fail the invocation; later handled write failures return unsuccessful rows. Check mutation success before dependent work.
- Automatic token renewal preserves rotated refresh tokens and prevents rapid repeated renewal within 60 seconds of token issuance.
- Known string and integer lists use CSV where the template specifies it. Quote values containing commas, quotes or newlines, and double embedded quotes. Empty text represents an empty list;
"" represents one empty string. Integer lists do not accept added whitespace or fractions. Structured object arrays retain their child fields.
- Open-ended maps, missing item definitions and deeply recursive values appear as explicitly labelled JSON text fields.
- Tenant-specific custom-object schema discovery, webhook listeners, S2S key authentication, asynchronous bulk-job polling and binary media operations are not provided. Asynchronous actions return acceptance acknowledgements, not completion guarantees.
- New filter syntax and sparse fieldsets are not exposed.