Integration
Connect DOOMSCROLLR to Chaport
When something happens in DOOMSCROLLR, your agent does the next thing in Chaport. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want DOOMSCROLLR and Chaport to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with DOOMSCROLLR and Chaport
Triggers and actions 10 triggers · 28 actions
Trigger
New Audience MemberTriggers when a new audience member is added.
Trigger
New Content PostTriggers when a new content post is created.
Action
Add Audience MemberAdds a new audience member to your account.
Action
Add productCreate a new product. POST /products
Action
Create Image PostCreates a new image post.
Action
Create PostCreates a new post.
Action
Delete audience memberRemove a subscriber by id. DELETE /audience/{id}
Action
Delete postDelete a post by id. DELETE /posts/{id}
Action
Delete productDelete a product by id. DELETE /products/{id}
Action
Get audience memberRetrieve a single subscriber by id. GET /audience/{id}
Action
Get postRetrieve a single post by id. GET /posts/{id}
Action
Get productRetrieve a single product by id. GET /products/{id}
Action
List audience membersList subscribers/audience members. GET /audience
Action
List PostsLists all posts in your account.
Action
List productsList all products in the account. GET /products
Action
Update audience memberUpdate an existing subscriber. PATCH /audience/{id}
Action
Update postUpdate an existing post. PATCH /posts/{id}
Action
Update productUpdate an existing product. PATCH /products/{id}
Trigger
Chat Closed (instant)Fires when a chat is closed. Webhook event: chat.closed.
Trigger
Chat FinishedTriggers when chat is finished.
Trigger
Chat Stage Updated (instant)Fires when a chat's stage changes. Webhook event: chat.stageUpdated.
Trigger
Message Read (instant)Fires when a message is read. Webhook event: message.read.
Trigger
New Chat StartedTriggers when chat is started.
Trigger
New Message Sent (instant)Fires when a new message is sent in a chat. Webhook event: message.sent.
Trigger
New Visitor (instant)Fires when a new visitor is created. Webhook event: visitor.created.
Trigger
Visitor UpdatedTriggers when visitor data is updated.
Action
Create an OperatorAdds a new operator to your Chaport account and returns the created operator.
Action
Delete a MessageDeletes one message from a Chaport chat. Identify the visitor and the message you want removed.
Action
Delete an OperatorRemoves an operator from your Chaport account.
Action
List OperatorsReturns every operator in your Chaport account, with each operator's name, email, role and status.
Action
List VisitorsReturns the visitors in your Chaport account, one page at a time.
Action
Retrieve an OperatorReturns one Chaport operator with their name, email, role, job title and current status.
Action
Retrieve a VisitorReturns one Chaport visitor with their name, contact details, notes and any custom data held about them.
Action
Retrieve Last Visitor ChatReturns a visitor's most recent Chaport chat, including its stage, operators and — when asked for — the transcript.
Action
Send a MessagePosts a message into a Chaport visitor's chat, starting a chat if there isn't one open.
Action
Update an OperatorUpdates a Chaport operator's details. Anything you leave blank keeps its current value.
Action
Update a VisitorUpdates an existing Chaport visitor's contact details, notes and custom data. Only the fields you fill in are changed; blank fields are left untouched.
Action
Update Operator StatusSets a Chaport operator's availability status, such as online or offline, optionally for a limited time.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.