The moment it happens

Post each new signature request to Slack

My team sees every signature request as it goes out, so nobody sends a duplicate.

Runs: The moment it happens
Apps: Dropbox Sign
AI: Not needed
Access: API key

Send this to your assistant

Create a ClickRuntime automation: whenever a signature request is sent from Dropbox Sign, post the title and who it went to in #sales-ops.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

In a team where several people send contracts, offers or consent forms through Dropbox Sign, nobody has a complete picture of what has gone out. A manager does not know whether the new vendor agreement was sent, finance cannot tell whether a customer has received the order form, and two people sometimes send the same document to the same person. Asking in chat takes time and interrupts whoever knows.

As soon as a signature request is sent in Dropbox Sign, an event arrives and a Slack message appears with the document title and who it was sent to. The channel becomes a live feed of outgoing paperwork, so everyone with an interest can see it without asking anyone.

Operations teams, legal departments and small businesses where more than one person sends documents will find it useful.

What you get out of it

One place to see what has gone out
The channel shows every request as it is sent. Managers and finance can check whether a document was sent without interrupting the person who sent it, who is usually in the middle of something else.
Duplicate sends are avoided
When a request appears in the channel, a colleague knows not to send it again. That prevents confusion for the recipient, who might otherwise receive two slightly different versions and wonder which one is correct.
Wrong recipients caught early
Seeing the recipient's name in the post lets a colleague spot a document sent to the wrong person. A quick correction before they sign is far better than a legal clean-up after a confidential agreement has been signed.
A timeline of outgoing paperwork
Slack keeps the posts in order, giving you a timeline of what was sent and when. That helps when someone insists they never received a contract and you need to show when it left.
Follow-up gets planned
Knowing a request has gone out lets a manager plan a check-in a few days later. Without that, nobody tracks whether the document comes back, and it can sit unsigned for weeks.

How it works

What happens, step by step

When a signature request is sent from Dropbox Sign, Dropbox Sign tells ClickRuntime straight away.
ClickRuntime picks out the document title and each signer's name and email.
It posts them to #sales-ops in Slack, so the team can see what has already gone out and avoid sending a duplicate.

Before it runs live

Connect Dropbox Sign
Paste your automation's link into the other app's webhook settings

What you get

RunsThe moment it happens

Post each new signature request to Slackjust nowSucceeded

Slack · #sales-opsSent for signature: Acme order form To: Jo Park <jo@acme.com>

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Act only on the items that match your own rules, and skip the rest
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other Dropbox Sign steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

request_sent_alert.pyexample

import json
from clickruntime import on_event, notify

@on_event
def handle(event):
    data = event.json or {}
    payload = json.loads(data["json"]) if isinstance(data.get("json"), str) else data
    if payload["event"]["event_type"] != "signature_request_sent":
        return {"posted": False}
    req = payload["signature_request"]
    to = ", ".join(f"{s['signer_name']} <{s['signer_email_address']}>" for s in req.get("signatures", []))
    notify.slack(f"Sent for signature: {req['title']}\nTo: {to}", channel="#sales-ops")
    return {"posted": True}

FAQ

Common questions

Which event does it listen for?

It uses the Dropbox Sign callback for a signature request being sent, so a post appears each time one goes out. You add the callback address in the API settings of your Dropbox Sign account.

Does the message include the signer's email address?

It can include the names or emails that Dropbox Sign supplies with the event. If you would rather keep addresses out of a shared channel, tell your AI assistant to show only names or the document title.

Do requests sent from templates trigger it too?

Yes. A request created from a template is still a signature request, so it triggers the same event. The post shows the title of the resulting document and the signers it was sent to, exactly as for a document uploaded by hand.

What permissions does it need?

API key. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run for each event the app sends.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

The moment it happens