Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] [New Workflow] Lead Docket Sync #47

Open
bdkiran opened this issue Aug 26, 2024 · 4 comments
Open

[Feature] [New Workflow] Lead Docket Sync #47

bdkiran opened this issue Aug 26, 2024 · 4 comments
Assignees
Labels
enhancement New feature or request

Comments

@bdkiran
Copy link
Contributor

bdkiran commented Aug 26, 2024

In this workflow we will be keeping all the leads from one Lead Docket synced with another. The workflow from a high level will look like the following:

New Lead Creation (Workflow)

Requirements:

  • Endpoint
  • Topic
  • Database(to store mapping of IDs in Lead Docket A to Lead Docket B)

Steps:

  • Lead Created Webhook(from Lead Docket A)
  • Transform and Send Lead(to Lead Docket B)
  • Create entry in our Mapping DB(Map Lead Docket A ID to Lead Docket B ID)

Lead Status Update (Workflow)

Requirements:

  • Endpoint
  • Topic
  • Database(to store mapping of IDs in Lead Docket A to Lead Docket B)

Steps:

  • Lead Status Change Webhook(from Lead Docket A)
  • Lookup in DB for Lead ID in Lead Docket B
  • Update the status in Lead Docket B using the Rest API
@bdkiran bdkiran added the enhancement New feature or request label Aug 26, 2024
@lucidmq lucidmq deleted a comment from masooddahmedd Aug 26, 2024
@lucidmq lucidmq deleted a comment Aug 26, 2024
@keremeyuboglu
Copy link
Collaborator

  • As I've understand we want this synchronization to be one way, not both ways, right?
  • Also, this is not urgent but I'd probably need the format we will be sending to the other docket for both update and creation(maybe it should be the same format with the one we use in ld_ld_sync but still) at one point.
  • As for the incoming requests, I've already got the json format that docket sends to us from the other project and looked around the swagger docs of the lead docket as well, so I should be fine in that end.

@bdkiran
Copy link
Contributor Author

bdkiran commented Aug 27, 2024

  • Yes this is a 1 way sync
  • Yeah I'll get you that info. What I'm going to do is set up 2 topics. One that will catch the Lead Created messages and one that will catch the Lead Status Update messages. From there you can go in the UI and retrieve the messages

@keremeyuboglu
Copy link
Collaborator

Great, let me know when you set those topics

@bdkiran
Copy link
Contributor Author

bdkiran commented Aug 30, 2024

Just an update that I'm migrating our infrastructure from my local server to the cloud. This is taking some time as I have to change a lot of what we're doing for a cloud setup. I'll let you know when the migration is completed and when the new topics are set up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

4 participants
@bdkiran @keremeyuboglu and others