All integrationsAccounting & Finance

Decile Hub

Read fund activity, portfolio companies, and CRM records, and manage deal pipelines in Decile Hub.

actions
20
triggers
5

Triggers

Start a workflow when something happens in Decile Hub.

  • New activity entryStarts a workflow when new activity entry.
  • Pipeline is createdStarts a workflow when pipeline is created.
  • Portfolio company is addedStarts a workflow when portfolio company is added.
  • Task is createdStarts a workflow when task is created.
  • New personStarts a workflow when new person.

Actions

Steps a workflow can run in Decile Hub.

  • Identify the authenticated API keyReturns metadata about the authenticated API key, the user it belongs to, the account it is scoped to, the key-level permissions, and (for regular user keys) the user's account_user role flags and accessible pipeline IDs. Useful for agents and integrations to introspect their own capabilities before making other calls. `account` is the account this request acted in (the one named by `X-Account-Id`, or the key's default account); `token.cross_account` says whether this is a us
  • List the accounts this API key can act inReturns every account the key's user is a member of, with the roles the user holds in each, except accounts whose admins have blocked the user's keys from other accounts (the key's own default account is always listed). A user API key acts in its default account (the one it was created in) unless a request sends the `X-Account-Id` header; the `id` of any row here is a valid value for that header. The list is the same whichever account the request runs in. A key that stays in
  • List activity feed entries for the current accountReturns the activity feed for the current account, newest first. Filter by subject (entity), event type, actor, date range, or form. Pagination is keyset. pass `pagination.next_page_token` from a response back as `page_token=` to fetch the next page.
  • Get a single activity entry with its full entryable bodyReturns one activity entry plus the full per-type `entryable` body. audit change diffs, full email bodies and recipients, note bodies, AML/KYC status, chat summaries, and so on. The list endpoint omits this detail.
  • List PeopleGets a paginated list of People in your People Directory. The response will have a data array with the people and a pagination object with the total count, current page, and total pages.Pages are 0-indexed, so the first page is page 0.The People returned can be filtered and ordered. Order direction is ascending by default. The default response shape is unchanged from prior versions and embeds notes, organizations_with_titles, and referred_by. The optional include= parameter i
  • Show PersonGet a single Person by Person id. A pipeline prospect id is not a Person id: take `person_id` from a search_pipeline_prospects row. An unknown id returns 404. The default response shape is unchanged from prior versions (embeds notes, organizations_with_titles, referred_by). The optional include= and fields= parameters are purely opt-in - include= replaces the default include set with a caller-specified subset, and fields= narrows top-level columns. The response also carries a
  • Update Person by IDUpdates the existing person selected by account-scoped ID; changing the email does not create a record.
  • Add a note to a personAppend a plain-text note to a person. The note is stored on the person and surfaced wherever person notes appear (including the prospect view if the person is a pipeline prospect's prospectable).
  • List pipelines for the current accountReturns the active pipelines for the current account. Pass `kind=investor` to filter to investor pipelines. Rows are ordered with the account's primary investor pipeline first (when one is marked); prefer the `is_primary: true` row when multiple investor pipelines exist. For entity-scoped operations, match `entity_id` exactly rather than inferring from the name or `is_primary`. The `id` field is the value to pass to any pipeline-scoped endpoint (e.g. `/api/v1/pipeline_prospec
  • Retrieves info for a specific pipelineReturns basic information for a specific pipeline and its stages. Forwarding an email to `ingestion_email` adds or updates the prospect (a deal on an investment pipeline) and attaches the email's files, such as a pitch deck.
  • Creates a pipelineCreates a pipeline, the same as "Create New Pipeline" in Hub. Pass `name` and either `type` or `copy_from_pipeline_id`. Fundraising (`investor`), Dealflow (`investment`) and Connectors (`connector`) pipelines come with their standard stages and email templates; `custom` starts empty. `copy_from_pipeline_id` copies the stages, actions and columns of an existing Fundraising, Dealflow, Connectors or Custom pipeline without changing it. Returns the new pipeline in the same shape
  • Deletes a pipelinePermanently deletes a user-created pipeline with its stages, automations and prospects, as deleting it in Hub does. Cannot be undone; archive the pipeline to only hide it.
  • Get pipeline metricsReturns aggregate counts/values for a pipeline plus a 7-days-ago snapshot for week-over-week deltas. The caller is expected to compute deltas in its prose layer.
  • Lists the stages of a pipelineReturns every stage of the pipeline in board order, with the id needed to rename a stage or to filter prospects by stage. `internal_id` is the stable key automations match on and never changes when a stage is renamed; `editable: false` marks a Decile-Hub-managed stage that cannot be renamed.
  • Adds a stage to a pipelineAdds a new stage at the END of the pipeline. Account admin authorization is required (account admins, or decile admins acting on the account). The stage is always appended last; there is no position parameter. To put it somewhere else, create it and then call `reorder_pipeline_stages` with the order you want. that call reports whether the move changes how the pipeline behaves before anything is applied. `internal_id` is generated from the name and returned; it is the stable
  • List portfolio companies for the current accountReturns portfolio companies across every fund in the current account. Each row is a (fund, organization) pair. the fund's stake in a single underlying company. Filter by `fund_id` or `organization_id`. Pagination is keyset. pass `pagination.next_page_token` from a response back as `page_token=` to fetch the next page.
  • Get a single portfolio company by idReturns one portfolio company. the same allowlisted fields surfaced by `GET /api/v1/portfolio_companies`.
  • List investments for a portfolio companyLegacy portfolio system. Funds on the new portfolio system keep their marks as position valuations: use `list_position_valuations`, `list_investment_positions` or `list_schedule_of_investments`. Returns the investments (accounting-transaction-driven tranches) belonging to a single portfolio company. Each row includes its effective mark, linked funding-round security, and valuation provenance as of the selected date. FMV and mark price match the expanded portfolio UI tranche r
  • List valuation history for a portfolio companyLegacy portfolio system. Funds on the new portfolio system keep their marks as position valuations: use `list_position_valuations`, `list_investment_positions` or `list_schedule_of_investments`. Returns valuation events for one portfolio company, ordered by valuation date newest first with an id tiebreaker. Numeric valuation values are strings. Pagination is keyset. pass `pagination.next_page_token` from a response back as `page_token=` to fetch the next page.
  • List TasksReturns a paginated, account-scoped list of Tasks. Optional filters narrow by status, assignee, and origin. Pages are 0-indexed.

Automate Decile Hub with Lodol.

Connect Decile Hub, then hand Lodol the job in Slack, Claude or ChatGPT.

We’re letting people in a few at a time.