Marketing ยท CONNECTIONManage Quentn contacts, tags, comments, contact fields, pipelines, stages, opportunities and lost reasons, read emails and users, and trigger campaign elements.
Explore 56 workflow actions for Quentn, including account permissions and operation limits.
Choose an action in the workflow builder, connect an account, and map its inputs. These actions are available in the catalog; your account access and a successful test determine whether they work for your setup.
The body is a plain JSON array of tag ids.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Returns how many contacts match a filter, without transferring them.
Returns the number of open opportunities matching the request.
Creates a contact.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Creates a comment on the contact.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Creates a custom field.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Creates up to 100 contacts in a single request.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Create a lost reason.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Places a contact into a pipeline stage as a deal.
A repeated request may repeat the external action. Review the previous result before retrying a write.
The new pipeline is owned by the acting owner of the API key.
A repeated request may repeat the external action. Review the previous result before retrying a write.
The stage is appended: its weight is the current maximum plus one.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Creates a tag.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Permanently removes the contact.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Permanently removes the comment (and the call-log entry attached to it, if it was one).
A repeated request may repeat the external action. Review the previous result before retrying a write.
Deleting a field also deletes the values stored in it.
A repeated request may repeat the external action. Review the previous result before retrying a write.
The reason is detached from every pipeline exit that referenced it - those deals stay lost, just without a reason.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Removes the deal together with its versions, scheduled actions and exit records.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Deletes the pipeline and everything it contains - stages, opportunities, their versions and exit records.
A repeated request may repeat the external action. Review the previous result before retrying a write.
A stage that still holds open opportunities cannot be deleted without saying what should happen to them: pass opportunitiesAction, and for move also opportunitiesNewStageId.
A repeated request may repeat the external action. Review the previous result before retrying a write.
A tag that is referenced by a campaign action cannot be deleted - deletion_blocked on the tag tells you in advance.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Looks the contact up by numeric id or by e-mail address.
A comment that belongs to a different contact is reported as 404 Comment not found.
A numeric identifier addresses a container, any other value a custom field by machine name (e.g.
Returns one email.
Returns one email version.
Read an opportunity.
Read a pipeline.
Read a stage.
Read a tag by id or name.
This is used to get user by id.
This is used to get all users.
Returns a page of the comments attached to a contact, newest first by default.
Returns a page of the custom fields (machine names starting with field_) followed by the field containers.
For every pipeline the acting owner may see, where this contact stands: active (open deal), won, lost (latest exit) or inactive (never in it, or removed).
Returns a page of the tags assigned to a contact, each with the moment it was assigned (assigned_date).
Returns a page of contacts.
Returns a page of email versions.
Returns a page of the account's emails.
Lost reasons are tenant-global.
Returns open opportunities.
Ordered by weight ascending - the pipeline's own stage order - unless sort says otherwise.
Lists the pipelines the acting owner of the key may see.
Returns a page of the tags of the account.
The one endpoint for every stage transition.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Moves a won or lost deal back into the stage it left, deletes the exit record and appends a new version.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Tag ids may be sent as a JSON array body or, for clients that cannot send a body with DELETE, as the pipe-separated ids query parameter.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Sets the weight of every stage in one call.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Contact object must contain either a valid mail field or a full address including the following fields: *first_name*, *family_name*, *ba_street*, *ba_city*, *ba_postal_code*.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Partially updates a contact.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Replaces the text of a comment; comment is required.
A repeated request may repeat the external action. Review the previous result before retrying a write.
The field type cannot be changed; sending a different field_type is rejected.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Rename a lost reason.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Changes deal fields.
A repeated request may repeat the external action. Review the previous result before retrying a write.
At least one of title, currency.isoCode, ownerId or access must be present - an empty body is rejected.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Only the title and the colour can be changed here; use reorder for the position.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Only name and description can be changed.
A repeated request may repeat the external action. Review the previous result before retrying a write.
Use the account and permissions required for your process. Review the connection check before configuring a workflow action.
Select a listed operation and map its required inputs. Use test records and add a human approval before writes that need review.
Inspect step outputs and confirm the result in Quentn. A saved workflow is not a completed provider action.
