Update deal with the Agendor API

Updates the fields sent and returns the deal in data. dealStage moves the deal to another stage, and dealStatusText wins, loses or reopens it.

Identifier
agendor_update_deal

The request

POST https://connect.reportei.com/api/tools/agendor_update_deal/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "id": 1
  }
}

Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.

Parameters

ParameterTypeRequiredDescription
idintegerYesId of the deal, from List deals or one of the create deal tools.
titlestringNoTitle of the deal.
descriptionstringNoNotes about the deal.
valuenumberNoMonetary value of the deal.
ownerUserintegerNoId of the user who owns the deal, from List users.
dealStageintegerNoPosition of the new stage in the funnel, starting at 1: the sequence of the stage in List funnels, not its id. Send funnel too when the deal is not in the default funnel.
funnelintegerNoId of the funnel of the new stage, from List funnels.
dealStatusTextstringNowon or lost finishes the deal, and ongoing reopens it.Values: ongoing, won, lost
lossReasonobjectNoWhy the deal was lost. Only with dealStatusText lost.
endTimestringNoWhen the deal was finished, in ISO 8601.
customFieldsobjectNoCustom field values keyed by the identifier of each custom field configured in Agendor.

Supported connections

Your customer connects their Agendor account once, with one of the modes below. The same connection serves every tool of the toolkit.

API key

Your customer pastes the app's key on a Connect screen, or your system sends the key with POST /api/customer-toolkits, with no screen.

The response

On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.

Ready for AI agents

This tool's input is a JSON Schema, available at GET /api/tools/agendor_update_deal. It becomes your agent's tool definition with no conversion.

Other Agendor tools

See all 15 tools

Toolkits in the same category

See all 100 toolkits

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.