Update opportunity with the Salesflare API
Updates the given fields of an opportunity. Moving it through the pipeline is a change of stage.
- Identifier
- salesflare_update_opportunity
The request
POST https://connect.reportei.com/api/tools/salesflare_update_opportunity/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
| Parameter | Type | Required | Description |
|---|---|---|---|
| id | integer | Yes | Id of the opportunity, from List opportunities or Create opportunity. |
| name | string | No | Name of the opportunity. |
| account | integer | No | Id of the account, from List accounts. |
| stage | integer | No | Id of the new stage, from the stages of List pipelines. |
| value | number | No | Value of the deal, in the currency of the pipeline. |
| probability | number | No | Chance of winning, in percent. |
| close_date | string | No | Close date, in ISO 8601. |
| closed | boolean | No | Whether the opportunity is closed. |
| done | boolean | No | Whether the opportunity is marked as done. |
| main_contact | integer | No | Id of the main contact, from List contacts. |
| owner | integer | No | Id of the user who owns the opportunity, from List users. |
| assignee | integer | No | Id of the user assigned to the opportunity, from List users. |
| tags | array | No | Tag names. |
| custom | object | No | Custom field values, keyed by the API name of each custom field of the team. |
Supported connections
Your customer connects their Salesflare 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/salesflare_update_opportunity. It becomes your agent's tool definition with no conversion.
Other Salesflare tools
- List accountsGETLists the accounts, the companies of the team, 10 per page by default. Paginate with limit and offset; a page shorter than limit is the last one.
- Get accountGETReturns one account with its addresses, email addresses, phone numbers, tags and custom fields.
- Create accountPOSTCreates an account, the company that contacts and opportunities belong to. Returns the new account with its id.
- Update accountPUTUpdates the given fields of an account.
- List contactsGETLists the contacts of the team, 20 per page by default. Paginate with limit and offset; a page shorter than limit is the last one.
- Get contactGETReturns one contact with its account, positions, phone numbers, addresses, tags and custom fields.
- Create contactPOSTCreates a contact, linked to an account with account. Returns the new contact with its id.
- Update contactPUTUpdates the given fields of a contact. archived true archives it.
Toolkits in the same category
See all 100 toolkitsSee Connect applied to your product.
Try it for 15 days with no card, or walk our team through your use case.
