Reo.dev: Reo Get Activity Types

List the valid Reo.dev activity sources (GitHub, docs, website, product, Slack, LinkedIn) and the activity types allowed for each.

Tool ID: reo_get_activity_types

Run this action

Use the TypeScript SDK for one call. Use ctx.tools.execute(...) inside a Play for durable calls, scheduled calls, or CSV processing.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'reo_get_activity_types',
  {},
);

console.log(result.toolResponse.raw);

CLI

deepline run reo_get_activity_types --input '{}'

Example response

The SDK returns this shape at result.toolResponse.raw. The example values illustrate the response.

{
  "data": {
    "data": [
      {
        "activity_source": "GITHUB",
        "label": "example",
        "activity_types": [
          {}
        ]
      }
    ],
    "request_id": "request_123"
  }
}

Use deepline describe reo_get_activity_types --json for the latest machine-readable contract.

Input reference

Overview Master API to refer `activity_type` and `activity_source`. Returns every valid activity source and the activity types allowed for each, for use as filters in Get Account Activities and Get Developer Activities. ### Path Parameters None. ### Errors | Code | When it happens | Response body | |---|---|---| | 400 | `X-API-KEY` header missing or empty | `{"error":"Missing API Key"}` | | 403 | Invalid API key, or a write API key used on this host | `{"error":"Invalid API Key."}` | ### ENUMs | Field | Value | Meaning | |---|---|---| | activity_source | `GITHUB` | GitHub | | activity_source | `DOCUMENT` | Documentation | | activity_source | `WEBSITE` | Website | | activity_source | `PRODUCT_JS` | Product (JS tracking) | | activity_source | `CODE_INTERACTIONS` | Code interactions | | activity_source | `SLACK` | Slack | | activity_source | `LINKEDIN` | LinkedIn | | See the live schema below for the complete notes.

This action requires no input fields.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.data`	`array`	No	—	Result records.
`result.data.data[].activity_source`	`"GITHUB" \| "DOCUMENT" \| "WEBSITE" \| "PRODUCT_JS" \| "CODE_INTERACTIONS" \| "SLACK" \| "LINKEDIN" \| "PRODUCT_API"`	No	—	Channel the activity came from. See ENUMs. - `GITHUB`: GitHub - `DOCUMENT`: Documentation - `WEBSITE`: Website - `PRODUCT_JS`: Product (JS tracking) - `CODE_INTERACTIONS`: Code interactions - `SLACK`: Slack - `LINKEDIN`: LinkedIn - `PRODUCT_API`: Product API (usage sent through the Add Telemetry Data and Add Custom Product Data APIs) Allowed: `GITHUB`, `DOCUMENT`, `WEBSITE`, `PRODUCT_JS`, `CODE_INTERACTIONS`, `SLACK`, `LINKEDIN`, `PRODUCT_API`.
`result.data.data[].label`	`string`	No	—	Human-readable label for the source or activity type.
`result.data.data[].activity_types`	`array`	No	—	Activity types valid for this source.
`result.data.data[].activity_types[].activity_type`	`string`	No	—	Type of activity. See ENUMs and Get Activity Types. - `FORK` (GITHUB): Forked repository - `STAR` (GITHUB): Starred repository - `COMMENT` (GITHUB): Commented - `ISSUE_CREATION` (GITHUB): Created an issue - `PULL_REQUEST` (GITHUB): Opened a pull request - `WATCH` (GITHUB): Watched repository
`result.data.data[].activity_types[].label`	`string`	No	—	Human-readable label for the source or activity type.
`result.data.request_id`	`string`	No	—	Request ID. Also returned in the `X-Request-Id` response header.
`result.meta`	`object`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: fixed (per call).
Estimated Deepline credits: 0 per pricing unit.
Provider-native pricing may still exist outside Deepline credit billing.

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation