Conference Follow-Up
You met people at a conference but did not connect on LinkedIn. This recipe matches your attendee list to LinkedIn profiles. You confirm each match and approve the campaign before it starts.
When to use this recipe
- After attending a conference, meetup, or webinar
- You have an attendee list with LinkedIn URLs, or names and companies to match
- You want to follow up soon after the event
Steps
Match attendees to profiles
The import needs a LinkedIn URL for each person. It skips rows without one. For rows with only a name and company, your agent searches LinkedIn and shows you each match to confirm.
Example prompt
“Here is my attendee list from [event]. Use the LinkedIn URL when a row has one. Otherwise search by name and company. Show me each match with name, headline and company. Leave unclear matches unmatched.”
Import confirmed attendees
Your agent creates a list and imports only the people you confirmed. It writes to your Crispy contacts only after you approve.
Example prompt
“Show me the people you will import. After I approve, create a list called '[list name]' and import only the confirmed people into it. Use the list.id from the manage_lists result as list_id.”
Set up and launch the campaign
Your agent shows you the campaign settings first. It saves the campaign only after you approve the settings. Saving sends nothing. Then your agent shows you a launch preview and launches only after you approve it. After launch, Crispy asks for no further approval. It tries to invite eligible people on its schedule. It can defer or skip a person, for example an existing connection or a person on the block list. These approvals are instructions in the prompt. Crispy does not enforce them.
Example prompt
“Prepare an acquisition campaign for the list with this note. "Hi {first_name}, good to see you at [event]. I would like to stay connected." Use 15 invites a day and the list.id from the manage_lists result as list_id. Show me the campaign settings. Do not create or change the campaign until I approve the settings. After I approve, save the campaign. Use the campaign.id from the upsert_campaign result as campaign_id for the next calls. Show me the launch preview. Do not launch until I approve the preview.”
Follow up with a resource
Ask your agent for accepted invitations from the campaign. It must ask for the accepted status, because the default call returns incoming requests. It drafts a message with your resource and sends each one only after you approve.
Example prompt
“List the invitations from my [event] campaign that were accepted. Use the accepted status. Draft a short message with the link to my talk slides for each person. Show me each message. Send each message only after I approve it.”
Try it now
Copy this prompt and paste it into Claude, Cursor, or any MCP client connected to Crispy.
I just got back from [event]. Here is the attendee list. Match each person to a LinkedIn profile and show me the matches. Do not import, invite or message anyone until I approve each step.
Run LinkedIn workflows from the AI client you already use.
Create your account, connect LinkedIn, create an API key, then add Crispy to your client. Review the docs for supported workflows and safety controls.